CSE Best Practices

This document summarizes operation practices of ServiceComb engines, application gateways, and registry/configuration centers in Cloud Service Engine (CSE) in common application scenarios. It provides detailed solutions each practice, helping users easily use CSE in different application scenarios.

**Table 1** Best practices of ServiceComb engines
Best Practice	Description
Hosting Spring Cloud Applications Using Spring Cloud Huawei SDK	Spring Boot and Spring Cloud are widely used to build microservice applications. The main purpose of using ServiceComb engines to host Spring Cloud applications is to replace open-source components with highly reliable commercial middleware to better manage and maintain the application system. The reconstruction process should minimize the impact on service logic. This operation is applicable to the following scenarios: Application systems developed based on Spring Boot do not have basic microservice capabilities. The application system integrates Spring Cloud Huawei to provide capabilities such as service registration and discovery and dynamic configuration management. Application systems developed based on the Spring Cloud open-source technology system, for example, Eureka for registration and discovery and Nacos for dynamic configuration, integrate Spring Cloud Huawei and use highly reliable commercial middleware to replace open-source middleware, reducing maintenance costs. Cloud native applications built based on other Spring Cloud development systems, such as Spring Cloud Alibaba and Spring Cloud Azure, are migrated to Huawei Cloud using Spring Cloud Huawei.
Hosting a Java Chassis Application	Java chassis is an open-source microservice development framework managed by the Apache Software Foundation. It was first donated by CSE. Till now, hundreds of developers have contributed to the project. Compared with Spring Cloud, Java chassis provides the following functions: Flexible and high-performance RPC implementation. Based on open APIs, Java chassis provides unified description of different RPC development modes, standardizing microservice API management and retaining flexible usage habits of developers. Based on reactive, Java chassis implements efficient communication protocols such as REST and Highway, and is compatible with traditional communication protocols such as Servlet. Rich service governance capabilities and unified governance responsibility chain. Common microservice governance capabilities, such as load balancing, rate limiting, and fault isolation, can be used out of the box. In addition, a unified governance responsibility chain is provided to simplify the development of new governance functions.

**Table 2** Best practices of the registry/configuration center
Best Practice	Description
Connecting Spring Cloud Eureka Applications to Nacos Engines	This section uses a demo to demonstrate how to connect Spring Cloud Eureka applications to Nacos engines.
Migrating Data from Self-Built Nacos to CSE Nacos	This section describes a registry center migration solution based on Nacos Sync. This solution is applicable to users who build Nacos on Huawei Cloud. Nacos Sync is an open-source component that supports bidirectional synchronization and smooth migration of the registry center. You can migrate services through synchronization tasks. Nacos Sync can synchronize the service information of the source cluster with that of CSE Nacos, in this way, the self-built registry center and CSE Nacos can be smoothly migrated, which is applicable to users who need service continuity.