This topic compares Cloud-native API Gateway and the original API Gateway.
Original API Gateway
The original API Gateway service is an API hosting service that provides a full range of lifecycle management functions to help build an API-centric system architecture. The lifecycle management functions include API design, development, testing, publishing, sales, O&M and monitoring, security control, and unpublishing. However, the original API Gateway is unable to expose services and control traffic in a Kubernetes Ingress or microservices architecture. The original API Gateway service is also incapable of functioning as a traffic ingress or integrator for AI applications.
For more information, see What is API Gateway.
Cloud-native API Gateway
Cloud-native API Gateway is a performant and secure gateway service that integrates traffic gateways, microservices gateways, security gateways, and AI gateways based on a unified architecture. Cloud-native API Gateway provides capabilities such as service exposure, traffic control, AI traffic entry and integration, and API lifecycle management. It is one to five times more powerful than a self-managed gateway, highly reliable based on accumulated expertise and experience in Double 11 promotions, highly secure thanks to multiple mechanisms such as mutual Transport Layer Security (mTLS) authentication, logon authentication, integrated application firewall, and custom security plug-in, and highly scalable by providing a wide variety of hot updatable plug-ins.
For more information, see What is Cloud-native API Gateway.