Consider alternatives when:
1) Building an external developer platform
- If developer onboarding flows, portals, monetization, and API product management are required, evaluate Apigee, Azure APIM, or dedicated API management suites.
2) Need streaming / WebSockets / long-lived connections
- API Gateway does not support streaming. For streaming or WebSockets, consider AWS API Gateway WebSocket APIs, load balancers, or Kubernetes-native gateways depending on platform requirements.
3) Require advanced gateway features out of the box
- Gaps commonly cited include caching, sophisticated quota logic, custom policies, fault injection, and advanced traffic control. Consider Kong, Tyk, NGINX, Apigee, or service mesh + ingress patterns.
4) Primarily Kubernetes/GKE-first
- Community guidance often recommends Kubernetes Gateway API implementations or other ingress/gateway solutions instead of Google Cloud API Gateway for Kubernetes-native patterns.
5) Need high-scale per-consumer API key management / usage plans
- Community threads raise concerns about API key limits and identifying individual callers using API keys. For external APIs with many tenants/keys, compare with platforms that provide first-class consumer identity, usage plans, and billing constructs.
Red flags in buying:
- If internal stakeholders treat API Gateway as a lightweight Apigee substitute while expecting Apigee features, re-platforming risk is significant.