API Gateways — Trivia & Interesting Facts¶
Surprising, historical, and little-known facts about API gateways.
The API gateway pattern predates microservices¶
API gateways existed long before the microservices movement. Enterprise Service Buses (ESBs) in the early 2000s performed similar routing and transformation functions. The modern API gateway pattern was formalized by Chris Richardson around 2015 as part of the microservices architecture movement.
Netflix Zuul handled over 50 billion requests per day¶
Netflix's Zuul gateway, open-sourced in 2013, processed more than 50 billion requests per day at peak. It was one of the first cloud-native API gateways and pioneered patterns like dynamic routing and filter chains that every modern gateway now copies.
Kong was born from a failed API marketplace¶
Kong (originally called Mashape) started in 2010 as an API marketplace where developers could discover and consume APIs. When the marketplace struggled, the team pivoted to open-source the gateway technology they'd built internally. Kong Gateway 0.1 was released in 2015 and has since been downloaded billions of times.
NGINX handles about 34% of all web traffic¶
NGINX, frequently used as an API gateway, serves roughly 34% of the world's busiest websites according to Netcraft surveys. Igor Sysoev created it in 2002 to solve the C10K problem — handling 10,000 concurrent connections. F5 Networks acquired NGINX Inc. for $670 million in 2019.
AWS API Gateway has a 30-second hard timeout¶
AWS API Gateway enforces a maximum integration timeout of 29 seconds (originally 30, reduced by 1 second for overhead). This hard limit has forced countless teams to redesign synchronous APIs into async patterns. It's one of the most complained-about AWS limits, and AWS has never raised it.
Envoy was created because NGINX config was too painful¶
Matt Klein created Envoy at Lyft in 2015 specifically because configuring NGINX for a dynamic microservices environment was unmanageable. Envoy introduced xDS APIs for dynamic configuration — meaning the proxy could be reconfigured without reloading. This innovation became the foundation of the entire service mesh movement.
Rate limiting algorithms have a fascinating history¶
The token bucket algorithm used in most API gateways was first described in 1986 for ATM network traffic shaping. The leaky bucket variant appeared in the same era. These 40-year-old algorithms are still the standard approach in modern gateways like Kong, Envoy, and AWS API Gateway.
The Gateway API (Kubernetes) took 4 years to reach GA¶
The Kubernetes Gateway API, intended to replace Ingress, was proposed in 2019 and didn't reach GA (v1.0) until October 2023. The long timeline reflected the difficulty of designing an API that could satisfy dozens of gateway implementations while remaining simple enough to be useful.
GraphQL gateways caused an unexpected DDoS vector¶
When organizations deployed GraphQL behind API gateways, they discovered that deeply nested queries could cause exponential backend load. A single GraphQL request could fan out to thousands of REST calls. This led to the creation of query depth limiting and query cost analysis — features that didn't exist in REST-era gateways.
Traefik auto-discovers services without configuration files¶
Traefik, created by Emile Vauge in 2015, introduced automatic service discovery by watching container orchestrators. Unlike NGINX or HAProxy which required config file changes and reloads, Traefik could detect new containers and route traffic to them within seconds. It was the first gateway truly built for the container era.