API Gateway, A Success Story
summary
A custom API gateway is built in Go, using fastHTTP for HTTP and vanilla WebSocket handling, enforces API key auth, and stores config in etcd/YAML. It resolves a TCP keepalive bug that caused random errors, sustains metric endpoints up to 330k requests/s, deploys in Docker on AWS, proxies and rate-limits with almost zero added latency, compares favorably to nginx for the focused proxy workload, and reaches production within two months.
AI-written summary · about
chapters (8)
- 0:00Introduction to System 73
- 1:23Defining system requirements
- 3:39Identifying core needs
- 7:26The role of an API gateway
- 8:56Evaluating build vs buy
- 13:05Developing the custom solution
- 17:39Overcoming technical hurdles
- 20:55Performance and final thoughts
related talks
28mWhy is API Gateway essential to business
20mAPI Gateway in a Nutshell
23mLessons from Building an API Management Platform
28mAPI Gateway: critical component of your digital architecture
36m10 Things You Hate About Your API Gateway
51mThe API Gateway is dead! Long live the API Gateway!
31mIn and Out: A 20-Minute Adventure or How to Rewrite a Bank's API Gateway
42mAPI Gateway Pattern & Kong in a Microservices World