Serverless App Engine (SAE) supports the native Dubbo microservice framework. You can migrate applications to SAE by only adding dependencies to and modifying configurations for the microservices that are developed by using this framework. You do not need to modify any code. SAE provides the following enterprise-level capabilities: microservice application hosting, microservice governance, monitoring and alerting, and application diagnosis.
Dubbo architecture
The following figure shows the architecture of the Dubbo framework.
The container starts, loads, and runs the services of the provider.
When the provider starts, it registers to the registry.
When the consumer starts, it subscribes to the required service from the registry.
The registry returns a list of provider addresses to the consumer. If changes occur, the registry pushes changed data to the consumer by using a persistent connection.
The consumer selects a provider to call from the list of provider addresses based on the software load balancing algorithm. If the call fails, the consumer calls another provider.
The consumer and provider store the total number of calls and the amount of time consumed by the calls in the memory, and send the data to the monitor once per minute.
References
For developing Dubbo applications, consider the following examples:
Host Dubbo applications to SAE: This topic provides an example on how to use XML configuration files to develop two Dubbo microservice applications that are used as a provider and a consumer respectively in an on-premises environment. This topic also describes how to deploy the applications on SAE.
Use Spring Boot to develop Dubbo microservice applications: This topic describes how to use Spring Boot to develop Dubbo applications and use the SAE service registry to implement service registration and discovery.