Create a Dubbo 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 the 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. 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

Specify the access IP address of the microservices engine. If you do not configure this parameter, the VIP will be used.

Description

Specify a description for the engine.

 

Engine configuration parameters

Parameter

Description

Engine Type

Select Dubbo.

Component Type

Select a component type:

  • Zookeeper: Integrated with the registration center to dynamically govern service releases and calls. Only the 2.7.3 version is supported.

  • Nacos: Provides registration center and configuration center capabilities. The Nacos component can discover, configure, and manage most mainstream services.

Zookeeper engine component configuration

Version

Only the 2.7.3 version is supported.

Engine Component

The registration center is required, and the configuration center is optional.

Register Center Type

Only dubbo-zookeeper3.5.6 is supported.

Configuration Center Type

Only Nacos2.0.1 is supported.

Nacos engine component configuration

Nacos provides registration center and configuration center capabilities, and you do not need to configure them.

Instance Quantity

Specify the number of instances as needed.

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.

MySQL Configuration

Configure MySQL settings for the configuration center.

  • 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.

 

The microservices engine will create a registration center and a configuration center automatically. You can click the engine name and access the detailed engine information page to view the registration center and configuration center addresses, domain names, and ports.