Serverless App Engine:Use an MSE Nacos registry

Prerequisites

• A virtual private cloud (VPC) is created and available. For more information, see Create and manage a VPC.

• The access port of your Nacos registry, such as port 8848, is added to your security group before you run your application. For more information, see Add a security group rule.

Background information

A startup company needs to deploy a microservices application on SAE for management but expects to use an MSE Nacos registry instead of the built-in service registry of SAE.

For information about how to deploy an application in cluster mode, see Cluster deployment instructions.

If you have a large number of microservices applications, you can use one of the following types of service registries that are listed in descending order by recommendation level:

• MSE Nacos registry

• Self-managed service registry

• Built-in service registry of SAE

If you want to implement features such as application service discovery and configuration management by using a self-managed Nacos engine, you must purchase the required resources to create and maintain the Nacos engine. This process is time-consuming and labor-intensive. If you use MSE to create a Nacos engine, you need to only focus on the location, version, network type, and specifications of the Nacos engine. You do not need to focus on the creation and maintenance of the Nacos engine. MSE allows you to focus more on your business.

Step 1: Purchase and build a Nacos engine

For more information about how to create a Nacos engine for applications in MSE, see Create a Nacos engine.

Step 2: Register and discover services

After the Nacos engine is started, you must specify a service registry on your application to use the service registration and discovery feature. After you run your application, the system automatically registers and discovers services based on the specified service registry.

Specify a registry on each application and run your service application and consumer application.

Open the application.properties file in src\main\resources, and specify the IP address of the Nacos server.

• Provider

  Original code:

  spring.application.name=service-provider
  server.port=18081
  eureka.client.serviceUrl.defaultZone=http://127.0.0.1:8761/eureka/

  Modified code:

  spring.application.name=service-provider
  server.port=18081
  spring.cloud.nacos.discovery.server-addr=192.168.XX.XX:8848 # Replace the value with the endpoint of the Nacos registry that you purchased. Example: mse:**********:8848. 

• Consumer

  Original code:

  spring.application.name=service-consumer
  server.port=18082
  eureka.client.serviceUrl.defaultZone=http://127.0.0.1:8761/eureka/

  Modified code:

  spring.application.name=service-consumer
  server.port=18082
  spring.cloud.nacos.discovery.server-addr=192.168.XX.XX:8848 # Replace the value with the endpoint of the Nacos registry that you purchased. Example: mse:**********:8848. 

Step 3: Deploy applications to SAE

Method 1: Configure service registration and discovery

Method 2: Configure startup parameters

Verify the result

In this example, the consumer application is used to verify the result. On the Instance deployment Information tab of the Basic Information page, click Webshell in the Actions column in the instance list. In the Webshell window, run the following commands to check whether the application is deployed. For more information, see Use the webshell feature to check the health status of applications.

1. Verify whether the service is registered.

   curl -X GET 'http://192.168.XX.XX:8848/nacos/v1/ns/instance/list?serviceName=service-provider'

   • service-provider: the name of the service.

   • 192.168.XX.XX:8848: the IP address and port number of the server on which Nacos is installed. Replace 192.168.XX.XX with the internal endpoint of the MSE Nacos registry. For information about how to obtain the internal endpoint, see Step 2: Register and discover services.

   If the following output is returned, the service is registered.

   

2. Verify whether the access URL of the microservices application is normal.

   Run one of the following commands based on your business requirements. 127.0.0.1:18082 indicates the IP address and access port of the server on which the provider application and the consumer application run.

   • curl http://127.0.0.1:18082/echo-rest/{Custom variable}

   • curl http://127.0.0.1:18082/echo-feign/{Custom variable}

   The following output indicates that the consumer application called the provider application and the access URL to the microservices application is normal.

References