Serverless App Engine:Introduction to microservice scenarios

SAE service registry

• Spring Cloud

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

  Spring Cloud Alibaba Nacos Discovery uses Spring Cloud Registry standard interfaces and is based on Spring Cloud Registry standard specifications. Spring Cloud Alibaba Nacos Discovery provides the same capabilities as Eureka, Consul, and ZooKeeper to support service registration and discovery.

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

  • The SAE service registry is a shared component that can help you save the costs of physical equipment for O&M and the deployment of components such as ZooKeeper.
  • The SAE service registry performs authentication and encryption during communication to improve the security of your service registration process.
  • The SAE service registry is integrated into other components of SAE to provide a complete set of microservice solutions.
• Dubbo

  The SAE service registry supports the SPI-based registry extension provided by Dubbo. The service registry supports features such as service registration, routing rules, and rule configuration on Dubbo.

  Note

  • For more information about the SPI-based registry extension provided by Dubbo, see SPI Extension Implementations.
  • For information about Dubbo service registration, see Registry Server References and Multiple Registries.
  • For information about Dubbo routing rules, see Routing Rule.
  • For information about Dubbo rule configuration, see Configure rule.

When you deploy an application on SAE, the SAE service registry automatically specifies the Nacos Server server address, the service port, and the following information at a high priority: namespace, access-key, secret-key, and context-path. No additional configurations are required.

Native Spring Cloud applications

• The first time you deploy a Spring Cloud application on SAE, you must locally add dependencies and manage configurations, and then deploy the application on SAE. For more information, see Use Spring Cloud to develop microservice applications and deploy them on SAE.
• If you have locally developed a Spring Cloud application that uses components such as Eureka, Consul, ZooKeeper, and Redis as dependencies, and you want to deploy the application on SAE, you only need to replace the registered and discovered dependencies and configurations with Spring Cloud Alibaba Nacos Discovery. You can deploy the application on SAE for microservice hosting without the need to modify any code. For more information, see Host Spring Cloud applications to SAE.

Native Dubbo applications

• The first time you deploy a native Dubbo application on SAE, you must locally add dependencies and manage configurations, and then deploy the application on SAE. For more information, see Host Dubbo applications to SAE.
• If you have locally developed a Dubbo application that uses components such as Eureka, Consul, ZooKeeper, and Redis as dependencies, and you want to deploy the application on SAE, you only need to replace the registered and discovered dependencies and configurations with edas-dubbo-extension. You can deploy the application on SAE for microservice hosting without the need to modify any code. For more information, see Host Dubbo applications to SAE.