Review these limits for Microservices Engine (MSE) cloud-native gateways before you use the gateway routing feature in Serverless App Engine (SAE).
Limits
Console conflict risk
Both the MSE console and the SAE console let you configure MSE cloud-native gateways. MSE does not protect settings that SAE writes to the gateway, and allows you to modify settings that are maintained by SAE from the MSE console. This may cause unintended consequences for your business. We recommend that you do not use the MSE console to modify the routing rules of MSE cloud-native gateways that are created by SAE.
Protocol support
Route configurations support only the HTTP protocol stack. Dubbo services are not supported.
| Protocol | Supported |
|---|---|
| HTTP 1.0 | Yes |
| HTTP 1.1 | Yes |
| HTTP 2.0 | Yes |
| gRPC | Yes |
| WebSocket | Yes |
| Dubbo | No |
What's next
To configure advanced capabilities — throttling, rewrite, cross-origin resource sharing (CORS), retry, and traffic replication policies — use the MSE console.