What Is CSE?

Cloud Service Engine (CSE) is a cloud middleware used for microservice applications. It supports ServiceComb engines contributed to Apache and 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.

Open-source base
The open-source Apache microservice core framework ServiceComb supports Spring Cloud and commercial Service Mesh.
Reliability and stability
Using Huawei's cloud-native technology, CSE provides cloud core services to hundreds of millions of Huawei devices.
Professional services
CSE is developed in collaboration with 100+ industry partners with experience in microservice consulting services.
Multiple programming languages
Microservice solutions are compiled in multiple programing languages, such as Java, Go, .NET, and Node.js.

Nacos Engine

CSE Nacos is a microservice registry, discovery, and configuration management platform developed based on open-source Nacos 2.x. It supports multiple development languages and frameworks, and provides DNS-based service discovery.

Nacos engines are supported only in CN East 2, CN-Hong Kong, AP-Singapore, ME-Riyadh, and LA-Mexico City2.

Key features of Nacos:

**Table 1** Features supported by Nacos
Feature	Sub-feature
Instance management	Creating a gateway
	Viewing instance specifications
	Viewing instance list
	Viewing instance details
	Deleting an instance
	Changing the billing mode from pay-per-use to yearly/monthly
	Enterprise project
Specification change	Expansion/Change
Connections	Using the IP address and domain name to access intranet
Namespace management	Viewing namespace list
	Viewing namespace details
	Creating a namespace
	Modifying a namespace
	Deleting a namespace
	Maximum number of namespaces NOTE: Up to 50 namespaces can be created.
Service management	Filtering namespaces
	Searching for a service
	Filtering empty services
	Viewing service list
	Creating a service
	Viewing service providers
	Viewing service subscribers
	Distinguishing instances by cluster
	Filtering providers by metadata
	Getting online/offline of a service node
	Editing the weight of a service node
Configuration management	Creating a configuration
	Import configurations
	Editing a configuration
	Deleting configurations
	Configuring dark launch
	Maximum number of configuration items that can be configured in a namespace
	Searching for a configuration
	Viewing configuration list
	Viewing configuration details
	Viewing historical versions
	Roll back a version
	Comparing configuration contents
	Configuring interception query.

ServiceComb Engine

ServiceComb engine uses Apache ServiceComb Service Center, which is a RESTful-style, high-availability, and stateless service registry and discovery center and provides microservice discovery and management. Service providers can register their instance information with the registry and discovery center for consumers to discover and use. ServiceComb engine is seamlessly compatible with open-source ecosystems such as Spring Cloud and ServiceComb. For details about Apache ServiceComb Service Center, see the following:

ServiceComb engines are supported only in CN East 2, CN-Hong Kong, ME-Riyadh, TR-Istanbul, AP-Singapore, and AP-Jakarta.

ServiceComb engine has two versions: 1.x and 2.x.

ServiceComb 2.x engines are commercial engines that manage large-scale microservice applications. You can select different engine specifications based on service requirements, and these specifications cannot be changed once engines are created. Exclusive engines are exclusively used; therefore, the performance is not affected by other tenants.

Compared with ServiceComb engine 1.x, the underlying architecture, functions, security, and performance of ServiceComb engine 2.x are upgraded, providing an independent service registry and discovery center and configuration center, and supports custom service scenarios and governance. Table 2 lists features supported in CSE 1.0 and CSE 2.0.

**Table 2** Comparison between ServiceComb engine 2.x and ServiceComb engine 1.x
Feature	Sub-feature		2.x	1.x	Remarks
Engine management	Security	Security authentication	√	√	-
Engine management	Reliability	3-AZ high reliability	√	√	-
Microservice management	Basic capability	Registry and discovery	√	√	-
		Multi-frame access	√	√	Supports Spring Cloud and ServiceComb Java Chassis.
		Automatic clear of versions without instances	√	x	The latest three microservice versions are retained for version 2.3.7 and later, and the versions without instances are automatically cleared.
	Performance	Millisecond-level push of instance changes	√	√	-
Configuration management	Basic capability	Management and configuration	√	√	-
		Diversified configuration formats	√	Only text is supported.	2.x supports YAML, JSON, TEXT, Properties, INI and XML.
		Import and export	√	√	2.x supports configuration import of the same policy.
	Advanced features	History version management	√	x	-
		Version comparison	√	x	-
		Fast rollback	√	x	-
		Configuration labels	√	x	-
	Performance	Second-level delivery	√	x	-
Microservice governance	Scenario-based service governance	Custom service scenario	√	x	-
		Matching rule based on the request method	√	x	-
		Matching rule based on the request path	√	x	-
		Matching rule based on request headers	√	x	-
	Governance policy: rate limiting	Token bucket rate limiting on the server	√	√	-
	Governance policy: retry	The client performs retry to ensure the availability, fault tolerance, and consistency of user services.	√	√	-
	Governance policy: circuit breaker	The server breaks faulty services to prevent large-scale faults.	√	√	-
	Governance policy: repository isolation	The server controls the request concurrency capability based on the semaphore.	√	x	-
Development tool	Local lightweight engine	One-click local startup, facilitating offline microservice development	√	√	-