Microservice scenarios

SAE service registry

• Spring Cloud

  The SAE service registry integrates all Spring Cloud Alibaba Nacos Discovery features.

  Spring Cloud Alibaba Nacos Discovery implements Spring Cloud Registry standard interfaces and specifications, and provides capabilities equivalent to Eureka, Consul, and ZooKeeper for service registration and discovery.

  You can replace Eureka, Consul, ZooKeeper, and Redis with the SAE service registry. SAE also provides the following advantages:

  • The SAE service registry is a shared component that saves the costs of physical equipment for O&M and deployment of components such as ZooKeeper.
  • The SAE service registry encrypts and authenticates communication to secure service registration.
  • The SAE service registry integrates with other SAE components to provide a complete microservice solution.
• Dubbo

  The SAE service registry supports Dubbo's SPI-based registry extension, including service registration, routing rules, and rule configuration.

  Note

  • Dubbo SPI-based registry extension: SPI Extension Implementations
  • Dubbo service registration: Registry Server References and Multiple Registries
  • Dubbo routing rules: Routing Rule
  • Dubbo rule configuration: Configure rule

When you deploy an application on SAE, the SAE service registry automatically configures the Nacos server address, service port, and the following parameters with high priority: namespace, access-key, secret-key, and context-path. No additional configuration is required.

Native Spring Cloud applications

• To deploy a Spring Cloud application on SAE for the first time, add dependencies and configure your application locally, then deploy on SAE. For more information, see Use Spring Cloud to develop microservice applications and deploy them on SAE.
• If your Spring Cloud application uses Eureka, Consul, ZooKeeper, or Redis, replace the registry dependencies and configurations with Spring Cloud Alibaba Nacos Discovery to deploy on SAE. No code changes are required for microservice hosting on SAE. For more information, see Modify service registration and discovery of applications to Nacos.

Native Dubbo applications

• To deploy a native Dubbo application on SAE for the first time, add dependencies and configure your application locally, then deploy on SAE. For more information, see Host Dubbo applications to SAE.
• If your Dubbo application uses Eureka, Consul, ZooKeeper, or Redis, replace the registry dependencies and configurations with edas-dubbo-extension to deploy on SAE. No code changes are required for microservice hosting on SAE. For more information, see Host Dubbo applications to SAE.