Enterprise Distributed Application Service (EDAS) allows you to configure NGINX Ingresses or Application Load Balancer (ALB) Ingresses for applications deployed in Kubernetes clusters. This way, external requests can be routed to these applications. This topic describes the scenarios of NGINX Ingresses and ALB Ingresses, and the differences between these two Ingress types.
Scenarios
NGINX Ingress
NGINX Ingresses are Kubernetes ingress gateways built based on open source NGINX. NGINX is widely used, and NGINX Ingresses are also easy to use. As the default ingress gateways in Kubernetes clusters, NGINX Ingresses provide basic capabilities, such as those related to security, routing, and observability. However, NGINX Ingresses require manual maintenance. NGINX Ingresses are suitable for scenarios in which your service traffic is low, you raise lower requirements for security, scalability, and stability, and you can manually manage gateways, or in which you need to customize gateways.
ALB Ingress
ALB Ingresses are based on Alibaba Cloud ALB instances. A single ALB instance supports one million queries per second (QPS). This provides ALB Ingresses with improved traffic routing capabilities, such as complex routing and automatic certificate discovery. ALB Ingresses also support auto scaling and are fully managed by Alibaba Cloud. ALB Ingresses are suitable for scenarios in which you have requirements for ultra-high elasticity and balancing of heavy traffic loads at Layer 7.
Differences
For more information about the differences between NGINX Ingresses and ALB Ingresses, see Compare NGINX Ingresses and ALB Ingresses.