SAE supports three types of service registries. Choose the one that matches your infrastructure and deployment requirements.
For most new deployments with no existing registry, use an MSE Nacos registry—it provides production-grade availability and supports Nacos configuration management.
Choose a registry
|
Registry |
Best for |
Limitations |
|
MSE Nacos registry |
Production workloads with no existing registry |
Requires an MSE instance |
|
Self-managed registry |
Existing Nacos or ZooKeeper deployments |
You manage address configuration and network connectivity |
|
SAE built-in Nacos registry |
Quick proof-of-concept testing |
Test environments only; no Nacos configuration management support |
Use an MSE Nacos registry: Use this option when you need a fully managed registry with high performance, extensibility, and high availability. It also supports Nacos configuration management.
Self-managed registry: Use this option if you have an existing self-managed service registry—such as Nacos or ZooKeeper—and want to continue using it after deploying to SAE. The application and registry must have network connectivity, and you configure the registry address directly in your application.
Use the SAE built-in Nacos registry: Use this option to quickly deploy and test applications without setting up a registry. Do not use it in production environments. The SAE built-in Nacos registry does not support Nacos configuration management—use Application Configuration Management (ACM) instead.