SAE integrates with the microservices governance features of MSE to help you manage applications more efficiently. Learn how to enable microservices governance and configure graceful start and shutdown.
Overview
Microservices governance
Serverless App Engine (SAE) integrates with Microservices Engine (MSE) to provide microservices governance capabilities including graceful start and shutdown, traffic governance, canary releases for messages, end-to-end tracing, intelligent circuit breaking, degradation policies, and same-zone routing preference. These features improve service responsiveness and stability while simplifying architectural management.
Graceful start and shutdown
This section covers graceful start and shutdown. For other microservices governance features, see Microservices governance.
Graceful start
Operations such as deployments, scale-outs, scale-ins, and restarts are common for online applications. In a microservices architecture, a provider service can receive traffic as soon as it registers with a registry, even if it is still performing initialization tasks such as warming up a database connection pool. For high-traffic microservice applications, enable graceful start to prevent an instance from receiving traffic before it is fully ready.
Graceful shutdown
When you update a running application, the process should be seamless to clients with no impact on business requests. In a high-concurrency microservices environment, if a provider instance shuts down abruptly, consumer applications may continue routing requests to it before detecting the offline status, causing errors and traffic loss. Configure graceful shutdown to ensure proper shutdown during deployments, stops, rollbacks, scale-ins, or resets.
Prerequisites
This feature is available only for Java applications.
For Standard Edition applications, you must activate the Professional or Enterprise Edition of MSE microservices governance.
ImportantWhen you use the microservices governance features of MSE with a Standard Edition SAE application, separate charges are incurred for MSE.
For Professional Edition applications, you must activate the Enterprise Edition of MSE microservices governance.
ImportantUsing the microservices governance features of MSE with a Professional Edition SAE application incurs no extra fees.
If you have activated the Professional Edition of microservices governance, you must upgrade to the Enterprise Edition.
Access the configuration page
The method for accessing the configuration page varies by scenario:
Create an application
Log on to the SAE console. In the left-side navigation pane, click Application Management > Application List. Select a region and namespace, and then click Create Application.
On the Basic Information page, configure the parameters and click Next: Advanced Settings.
Change a running application
WarningAfter you redeploy an application, the application is restarted. To prevent unpredictable errors such as business interruptions, we recommend that you deploy applications during off-peak hours.
Log on to the SAE console. In the left-side navigation pane, click Application Management > Application List. Select a region and namespace, and then click the name of your target application.
On the Basic Information page of the application, click Deploy Application.
Change a stopped application
Log on to the SAE console. In the left-side navigation pane, click Application Management > Application List. Select a region and namespace, and then click the name of your target application.
On the Basic Information page of the application, click Modify Application Configurations.
Find and expand the Microservices Governance section and follow the steps below.
Configure microservices governance
Enable microservices governance
In the Microservices Governance section, turn on microservices governance.
Configure graceful start and shutdown
Configure graceful start
After you enable microservices governance, configure graceful start in the Microservices Governance section.
Enable the graceful start feature.
Configure the Low-traffic Prefetching Duration and Delayed Service Registration.
Parameter
Description
Low-traffic Prefetching Duration (Seconds)
The traffic warm-up mechanism gradually increases traffic to a new node, mitigating cold-start performance impacts in Java applications and preventing a spike in overall response time (RT). The warm-up process ends automatically after the specified duration, after which the node handles its full traffic load.
Delayed Service Registration
Delays service registration for a specified duration. If your application performs long-running asynchronous tasks at startup, use this parameter to delay when a new node starts receiving traffic.
ImportantIf you set a delayed registration duration greater than 0, you must configure a readiness probe for the application deployment. Set the path to
/healthand the port to 54199. This ensures that Kubernetes considers the service ready only after it has fully registered with the registry. This prevents traffic drops that can occur when service consumers cannot find an available provider. Important: Do not set theliveness probeto the same path/health, as this can cause the application to get stuck in a restart loop.For example, set small flow warm-up time to
120seconds and delayed registration to0seconds.
Configure graceful shutdown
The graceful shutdown feature is enabled by default when you enable microservices governance.
Graceful shutdown ensures that in-flight requests complete before a node goes offline during deployments, scale-ins, or restarts, preventing request errors from abrupt shutdowns.