This topic describes how to use the Cloud-native Gateway module of Microservices Engine (MSE).
Practice guideline
MSE Cloud-native Gateway provides comprehensive network and security features to help developers quickly build distributed applications across clouds and devices. Cloud-native Gateway supports multiple protocols and frameworks, and can implement features such as service registration and discovery, load balancing, proxy, circuit breaking, traffic throttling, degradation, and intelligent retry. You can use the cloud-native gateway features that are described in the following sections.
Manage services in multiple ACK clusters by using a cloud-native gateway
A cloud-native gateway supports access from multiple Alibaba Cloud Container Service for Kubernetes (ACK) clusters. A gateway is associated with multiple clusters, combines services with identical names, and implements load balancing among multiple services. You can use the feature together with the health check feature of the gateway to automatically detect service availability and implement automatic traffic switching upon failures in an efficient manner. For more information, see Manage services in multiple ACK clusters by using a cloud-native gateway.
Use an MSE cloud-native gateway as an egress gateway in ACK clusters
MSE cloud-native gateways can expose services deployed in ACK clusters to meet business requirements for egress traffic management and security control. For more information, see Use an MSE cloud-native gateway as an egress gateway in ACK clusters.
Perform auto scaling for backend applications in ACK clusters based on gateway QPS values
As traffic ingresses, cloud-native gateways are highly sensitive to the amount of business traffic. On the basis of Kubernetes capabilities and queries per second (QPS) metric data collected by MSE cloud-native gateways, business applications can perform auto scaling based on the QPS values of business pods. This way, you can scale out or scale in backend services on demand. For more information, see Perform auto scaling for backend applications in ACK clusters based on gateway QPS values.
Implement the blue-green deployment, A/B testing, and canary release by using MSE cloud-native gateways
You can implement the blue-green deployment, A/B testing, and canary release by using MSE cloud-native gateways. For more information, see Implement the blue-green deployment, A/B testing, and canary release by using MSE Cloud-native Gateway.
Implement static website hosting by using MSE cloud-native gateways and Alibaba Cloud OSS
You can store files that are required by static websites in Object Storage Service (OSS) buckets and then use MSE cloud-native gateways as proxies to manage the static website content that is stored in OSS buckets. For more information, see Implement static website hosting by using MSE cloud-native gateways and Alibaba Cloud OSS.
Implement active zone-redundancy based on MSE cloud-native gateways
By default, cloud-native gateways are deployed in multiple zones. This allows you to globally manage traffic across zones in a region. In active zone-redundancy scenarios, requests from multiple business clusters across zones can be efficiently allocated by using load balancing. If a node in a zone fails, the system implements a failover and the faulty node can be automatically removed within 1 second. This helps effectively ensure service continuity and high availability.
Route requests of WebSocket applications based on cloud-native gateways
Cloud-native gateways can forward traffic from WebSocket applications that are deployed in an ACK cluster. For more information, see Route requests of WebSocket applications based on cloud-native gateways.
Route requests of gRPC applications based on cloud-native gateways
Cloud-native gateways can route requests of gRPC applications. For more information, see Route requests of gRPC applications based on cloud-native gateways.
Manage MSE Nacos services by using a cloud-native gateway
You can configure routing policies and alerts by associating a cloud-native gateway with a service source in MSE Nacos registries. For more information, see Manage MSE Nacos services by using a cloud-native gateway.
Enable HTTP/3 for a cloud-native gateway
HTTP/3 has three major features: head-of-line blocking, connection migration, and zero round-trip time (0-RTT). HTTP/3 is especially suitable for scenarios in which a network switchover is performed for multiple devices or a network connection is weak. You can enable HTTP/3 for a cloud-native gateway. For more information, see Enable HTTP/3 for a cloud-native gateway.