Cloud-native gateways of Microservices Engine (MSE) integrate the functionalities of traffic gateways (such as Kubernetes Ingress and NGINX Ingress) with those of microservice gateways (including Spring Cloud Gateway and Zuul). A cloud-native gateway reduces resource overhead by up to 50% and decreases request latency. You can migrate from a traffic or microservice gateway to an MSE cloud-native gateway.
Migrate traffic from an NGINX Ingress gateway to an MSE Ingress gateway
MSE Ingress is an open source, Kubernetes-based Ingress controller that simplifies the handling of Kubernetes API calls. It supports HTTP, HTTPS, Web Server Gateway Interface (WSGI), and gRPC. By migrating from an NGINX Ingress gateway to an MSE Ingress gateway, you can improve resource utilization and operational efficiency. For more information, see Migrate traffic from an NGINX Ingress gateway to an MSE Ingress gateway.
Migrate services from Spring Cloud Gateway to a cloud-native gateway
A cloud-native gateway provides optimized routing and authentication management between services, with greater extensibility and fault tolerance than Spring Cloud Gateway. Migrating to a cloud-native gateway improves performance for microservices and containerized deployments. For more information, see Migrate services from Spring Cloud Gateway to a cloud-native gateway.
Migrate services from a Zuul gateway to a cloud-native gateway
Zuul lacks containerized service discovery, which is essential for modern microservices. Cloud-native gateways automatically detect and route requests to the appropriate service instance, which streamlines discovery and reduces the risk of faults. We recommend that you migrate services from a Zuul gateway to a cloud-native gateway. For more information, see Migrate from Zuul to a cloud-native gateway.