Function Overview

Cloud Service Engine (CSE) is a cloud middleware used for microservice applications. It supports the ServiceComb engine provided by Huawei Cloud to the Apache community, and nacos engine enhanced in open source. You can use CSE with other cloud services to quickly build a cloud-native microservice system, implementing quick development and high-availability O&M of microservice applications.

On the CSE console, you can view the ServiceComb engine information, obtain the ServiceComb registry and discovery address and configuration center address, set ServiceComb engine backup and restoration, manage public network access for a ServiceComb engine, upgrade ServiceComb engines, change ServiceComb engine specifications, manage security authentication for a ServiceComb engine, manage tags for ServiceComb engines, and delete ServiceComb engines.

• The service center of the ServiceComb engine provides the service registration function, that registers basic information, such as the application to which a microservice belongs, microservice name, microservice version, and listening address, with the service center when the microservice is started.
• The configuration center is used to manage microservice application configurations. Microservices connect to the configuration center to obtain configurations and changes. The configuration center is also the core component for managing microservices. For example, service governance rules are delivered through the configuration center.
• Unified request marker-based governance is provided based on dynamic configurations for different microservice development frameworks, such as Spring Cloud, Java Chassis, and Dubbo. Microservice governance of ServiceComb engines can be used by introducing related governance components to the development frameworks.
• In dark launch, a small number of users test the trial version, ensuring smooth rollout of new features. Once new features become mature, a formal version is released for all users. Dark launch ensures stability of the entire system. During initial dark launch, problems can be detected and fixed.
• Dashboard provides basic capabilities for monitoring microservice running. Microservices report running status using SDKs. The reported data includes request statistics, such as the quantity, latency, and error rate, as well as governance-related status, such as the circuit breaker status.
• A ServiceComb engine may be used by multiple users. Different users must have different engine access and operation permissions based on their responsibilities and permissions.

Spring Cloud or Java Chassis applications can be connected to the ServiceComb engine to use ServiceComb functions.

On the microservice engine console, you can view the Nacos engine information, expand the Nacos engine capacity, upgrade Nacos engines, manage tags for Nacos engines and delete Nacos engines.

• Namespaces isolate configurations in different environments. For example, resources (such as configurations and services) in the development and test environments are isolated from those in the production environment. Different namespaces can have the same group or data ID.
• The CSE console manages services registered with Nacos.
• The CSE console manages configurations of services registered with Nacos.

Spring Cloud applications can be connected to the Nacos engine to use Nacos functions.

Cloud Trace Service (CTS) enables you to query, audit, and review operations performed on cloud resources. Traces include the operation requests sent using the management console or APIs as well as the results of these requests.

Microservice engines provide Representational State Transfer (REST) APIs, allowing you to call APIs using HTTPS.