Serverless App Engine (SAE) uses Layer 7 load balancing capabilities to distribute request traffic to specified application instances based on forwarding rules. This topic describes the limits of Microservices Engine (MSE) cloud-native gateways with which you must be familiar before you use the gateway routing feature of SAE.
Limits
You can configure settings for MSE cloud-native gateways in the MSE console or in the SAE console. MSE does not protect the settings that you configured for MSE cloud-native gateways in the SAE console, and allows you to modify the settings that are maintained by SAE in the MSE console. This may cause unintended consequences for your business. Therefore, 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.
Route configurations of MSE cloud-native gateways support only the HTTP protocol stack, including HTTP 1.0, HTTP 1.1, HTTP 2.0, gRPC, and WebSocket, and do not support Dubbo services.
You can configure advanced capabilities such as throttling, rewrite, cross-origin resource sharing (CORS), retry, and traffic replication policies in the MSE console.