Application Scenarios

When a microservice starts, the instance information is registered with CSE, including the basic instance information, such as the application name, microservice name, version number, service contract, and instance address. When a microservice needs to call the APIs of other microservices, it queries instance information from CSE and caches the information locally. The cache is updated through mechanisms such as event notification and scheduled query. The locally cached address information is used to implement point-to-point calling between microservices. When a microservice has multiple instances, different load balancing policies can be configured, including polling, weight, and dark launch.

For O&M, you can view the instance list, microservice calling relationship, and service contract through CSE to help customers understand the application system composition and running status.

Service governance can be enabled using either of the following ways:

1. Configured in microservice development. In this way, the policy is configured for all service scenarios, for example, the load balancing policy.
2. Configured in microservice running. In this way, the policy is configured for scenarios where services are dynamically changed, for example, the rate limiting policy.

These two ways have the same internal implementation mechanism. The configuration management system delivers governance policies and the runtime SDK executes the governance policies. The runtime governance SDK is included in the microservice development framework and extension package selected by the user and is compiled and integrated with microservices. The CSE console provides common governance policy management to help users adjust governance policies based on services.

Configuration management centrally manages microservice configurations. Configurations are delivered to specific microservices based on configuration item attributes, such as scopes and labels.

Configuration management provides a series of user-friendly functions, such as historical versions view, configurations rollback, configurations import and export, and flexible scope management, meeting users' requirements for managing complex environments and a massive number of microservices.