Should I do my own API Gateway?
summary
Allegro built an in‑house API gateway in under a quarter with an ~8‑person effort, using Undertow proxy, Zookeeper for config, Couchbase for rate limits and OpenAPI for docs. Routing lives in a JSON repo pushed to Zookeeper, requests flow through a chain of handlers with response listeners, tokens validate at the edge, and canary routing uses headers. Runs on VMs with 0.5 CPU and 2GB RAM and shows 250ms average overhead. Docs require manual curation; commercial alternatives reduce maintenance risk.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 2:40How we started with it
- 15:00Canary deployments
- 16:17Was it worth it
- 17:10Conclusion
related talks
46mAPI Gateway Recipes: Solutions for Operation, Integration & Security
36m10 Things You Hate About Your API Gateway
28mAPI Gateway: critical component of your digital architecture
20mAPI Gateway in a Nutshell
32mTaking Back Control of Your APIs with Gateway API
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
26mBuilding, Managing & Governing APIs on AWS
25mHow API-as-a-Service can Improve CX, Scalability, and Security