MSE cloud-native gateways use routes, services, service sources, and domain names to manage traffic from clients to your backend systems. This topic describes each of these components.
Routes
A route defines rules that the gateway uses to match incoming client requests and forward them to the appropriate service. Each route is bound to one service, and a service can have multiple routes.
MSE cloud-native gateways support five routing modes:
|
Routing mode |
When to use |
|
Single-service routing |
Forward all matching requests to one backend service |
|
Percentage-based routing |
Split traffic across multiple versions for canary releases or gradual rollouts |
|
Tag-based routing |
Route requests to specific service versions based on request headers or user attributes, for A/B testing |
|
Mock routing |
Return a fixed response without forwarding to a backend, for testing and staging |
|
Redirection |
Redirect requests to a different URL |
For instructions on creating and configuring routes, see Routing.
Services
A service represents a backend application registered in the gateway. The gateway resolves service endpoints through the service, then routes traffic to those endpoints according to the matching route rules.
Cloud-native gateways support the following service sources, from which you can add and manage services:
Container services
MSE Nacos
MSE ZooKeeper
Enterprise Distributed Application Service (EDAS) registries
Serverless App Engine (SAE) registries
Fixed addresses
DNS domain names
Function Compute
For instructions on adding and managing services, see Services.
Service sources
A service source is the underlying registry or cluster that provides service discovery. Connecting a service source to the gateway lets the gateway automatically discover and track service endpoints without manual configuration.
The following service sources are supported:
Container Service for Kubernetes (ACK) and ACK Serverless clusters
EDAS registries
SAE registries
MSE ZooKeeper
MSE Nacos
For instructions on creating and managing service sources, see Service sources.
Domain names
Domain names determine how the gateway exposes your services to external clients. Each domain name can be configured with its own protocol settings, Secure Sockets Layer (SSL) certificate, and route configurations, letting you serve multiple domains from a single gateway instance.
You can create and manage domain names, and update protocols or certificates when an SSL certificate expires or domain ownership changes.
For instructions on creating and managing domain names, see Domain names.