Serverless App Engine (SAE) allows you to select different Nacos registries from the console, including self-managed registries, the SAE built-in registry, and commercial registries from Microservices Engine (MSE). This topic describes how to use the SAE console to configure Nacos service registration and discovery for an application.
Related documentation
Follow the procedure for your Nacos type.
-
For a commercial Nacos registry from MSE, see Use an MSE Nacos registry.
-
For a self-managed Nacos registry, see Use a self-managed Nacos registry.
-
For the SAE built-in Nacos registry, follow the steps in this topic. SAE automatically updates the registry and configuration center addresses for your application by injecting environment variables and modifying the bytecode with a Java Agent. This means you can deploy your application directly to SAE without changing your code.
Recommendations
If you have a large number of microservices applications, you can use one of the following types of service registries that are listed in descending order by recommendation level:
-
MSE Nacos registry
-
Self-managed service registry
-
SAE built-in service registry
For more information, see MSE Nacos and open-source Nacos.
How it works
SAE automatically updates the registry and configuration center addresses for your application by injecting environment variables and modifying the bytecode with a Java Agent. This means you can deploy your application directly to SAE without changing your code.
The SAE built-in Nacos enables authentication by default, requiring no additional configuration.
Limitations
-
The SAE built-in Nacos does not support Seata Server.
-
The SAE built-in Nacos supports only the Java language.
-
Note
Upgrading from Nacos SDK 1.x to 2.x is recommended for the following reasons:
-
The 1.x client uses a long polling mechanism to listen for configuration changes, with a default timeout of 30 seconds. ARMS (Application Real-Time Monitoring Service) may misinterpret these timeouts as slow calls and trigger unnecessary alerts. The 2.x client uses persistent gRPC connections, which avoids this issue.
-
The 2.x series offers significant improvements in architecture, performance, stability, and features. For more information, see the release notes.
-
Procedure
The entry point differs depending on the scenario:
Create an application
-
Log on to the SAE console. In the navigation pane on the left, choose . Then, select a region and a namespace, and click Create Application.
-
On the Basic Information page, configure the settings and click Next: Advanced Settings.
Modify a running application
After 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 navigation pane on the left, choose . Then, select a region and a namespace, and click the name of the target application.
-
On the Basic Information page of the application, click Deploy Application.
Modify a stopped application
-
Log on to the SAE console. In the navigation pane on the left, choose . Then, select a region and a namespace, and click the name of the target application.
-
On the Basic Information page of the application, click Modify Application Configurations.
Configure service registration and discovery
Find and expand the Service Registration and Discovery section. Set Nacos-based Service Discovery to SAE Built-in Nacos.
After you select this option, SAE overwrites the registry address configured in your application and automatically connects the application to the SAE built-in Nacos registry.