Create a Spring Cloud microservices engine

  1. On the top navigation bar, click Business Apps.

  1. From the left navigation pane, select Microservices > Microservices Engines.

  1. Click Create.

  1. Configure engine parameters as needed, and then click Create.

Basic configuration parameters

Parameter

Description

Engine Name

Specify an alias for the microservices engine. You can select a microservices engine by its alias when you create an application group. For more information, see "Create an application group." The alias is a string of 1 to 30 characters and can contain letters, digits, underscores (_), and hyphens (-).

Resource Configuration

Select a container cluster to provide an isolated working environment for the microservices engine. The system will automatically deploy the engine component container to the selected container cluster. The following cluster types are available:

  • Shared cluster—Select a container AZ.

  • Exclusive cluster—Select a container cluster created on the Cloud Services > Cloud Container Engine page.

Only services deployed in the selected container AZ or cluster can use the microservices engine.

Access IP

This parameter is optional.

Enter an IPv4 address in dotted decimal notation. If you do not specify an IP address, the VIP is used.

 

Engine configuration parameters

Parameter

Description

Engine Type

Select Spring Cloud.

Component Type

Select a component type:

  • Spring Cloud Native Components: Provides configuration management, service discovery, intelligent routing, grayscale service, circuit breaker, control bus, cluster state capabilities.

  • Nacos: Provides registration center and configuration center capabilities. The Nacos component can discover, configure, and manage most mainstream services. You do not need to configure the registration center or configuration center separately when you select this type.

Spring Cloud native component configuration

Version

Available versions include Finchley.SR4, Greeenwich.SR1, and Hoxton.SR8.

Engine Component

Configure the registration center, configuration center, and API gateway settings. The registration center is required, and the configuration center and API gateway are optional. As a best practice, configure the configuration center.

The available configuration center, registration center, and API gateway versions vary by engine version, as shown in Table-1.

Nacos

Engine Component

Configure the registration center, configuration center, and API gateway settings. The registration center and configuration center are required and are selected by default, and the API gateway is optional.

Instance Quantity

Specify the number of registration center, configuration center, or API gateway instances as needed. More instances can improve system reliability but require more resources.

Container Flavor

Specify the container startup and operation limits. The startup limit cannot be higher than the operation limit.

  • Startup Limit: Minimum CPU and memory resources required to start the container.

  • Operation Limit: Maximum CPU and memory resources that can be used by the container.

Cluster External Port

Manually specify or configure the system to automatically allocate the internal/external network port number for the engine component.

Nacos supports gRPC and requires three ports to be opened. The system can assign ports automatically. If you choose to assign ports manually, you only need to enter the main port number, and the system generates the other two port numbers automatically, main port number+1000, and main port number+1001.

Database and Middleware Settings

Configure database and middleware settings for the configuration center of the Spring Cloud native component, registration center of Nacos, configuration center, and API gateway.

  • Default: Use the default MySQL database and Redis cache. To avoid service conflicts, do not use the default settings in a production environment.

  • Manually Specify: Manually specify the database and cache settings. If the selected AZ is not in the default cluster, you can only manually specify the database and cache settings. The platform supports MySQL databases by default. If you specify an API gateway, you can enter the cached address, port, and password.

 

Table-1 Component versions supported by different Spring Cloud engine versions

SpringCloud engine version

Registration center version

Configuration center version

API gateway version

Finchley.SR4

Eureka2.0.9

Spring Cloud Config2.0.9

Spring Cloud Gateway2.0.9

Greeenwich.SR1

Eureka2.1.1

Spring Cloud Config2.1.1

Spring Cloud Gateway2.1.1

Hoxton.SR8

Eureka2.2.5

Spring Cloud Config2.2.5

Spring Cloud Gateway2.2.5

 

The microservices engine will create a registration center, a gateway, and a configuration center automatically. To view their internal access addresses and external access addresses, click the engine name and access the detailed engine information page.