Help Center/ Cloud Service Engine/ Service Overview/ Functions
Updated on 2025-10-31 GMT+08:00
View PDF
Share

Functions

Cloud Service Engine (CSE) is a cloud middleware service for microservice applications. It supports Huawei Cloud ServiceComb engines contributed to Apache, open-source enhanced Nacos engines. You can also use other cloud services to quickly build a cloud-native microservice system, implementing quick development and high-availability O&M of microservice applications.

This section describes main functions of CSE. You can check if a certain function is available in a region on the console.

Nacos Engine

  • Managing Nacos engines

    On the CSE console, you can view the Nacos engine information, increase Nacos engine instances, upgrade the Nacos engine, manage Nacos engine tags, and delete Nacos engines. For details, see Managing Nacos Engines.

  • Using 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. For details, see Managing Namespaces.
    • You can use the CSE console to manage services registered with Nacos. For details, see Managing Nacos Engine Services.
    • The CSE console manages configurations of services registered with Nacos. For details, see Managing Nacos Engine Configurations.

ServiceComb Engine

  • Managing ServiceComb engines

    On the CSE console, you can view the ServiceComb engine information, set ServiceComb engine backup and restoration, manage public network access of ServiceComb engines, upgrade ServiceComb engine versions, change ServiceComb engine specifications, manage ServiceComb engine security authentication, manage ServiceComb engine tags, and delete ServiceComb engines. For details, see Managing ServiceComb Engines.

  • Using ServiceComb engines
    • The service center of the ServiceComb engine provides the service registry 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 the information and changes of configurations. 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.