Enterprise Distributed Application Service:Manage a microservice namespace

Scenario

For example, you have three environments in a virtual private cloud (VPC) that are separately used for application development, testing, and production. You can create the Dev, Test, or Prod microservice namespace for the relevant environment. If you create clusters and deploy applications in the namespaces, the resources, applications, and services in one namespace are isolated from those in another. You cannot call services or push configurations across namespaces.

Default microservice namespace

When you create an application in the Enterprise Distributed Application Service (EDAS) console, you can create the application in the default microservice namespace. This indicates the resources and services of the application are not isolated by microservice namespaces.

If you select the default microservice namespace in a region on the Applications page, the displayed applications do not belong to microservice namespaces.

Create a microservice namespace

1. Log on to the EDAS console.

2. In the left-side navigation pane, choose Resource Management > Microservice Namespaces.

3. In the upper-right corner of the Microservice Namespace page, click Create Microservice Namespace.

4. In the Create Microservice Namespace dialog box, configure parameters and click Create. The following table describes the parameters.

   

   Parameter	Description
   Microservice Namespace	Enter a name for the microservice namespace that you want to create.
   Microservice Namespace ID	Enter a custom string to specify an ID for the microservice namespace. The ID can contain only letters and digits.
   Registration and Configuration Center	MSE Nacos: the Microservice Engine (MSE) Nacos engine that you purchased. MSE Nacos can be seamlessly integrated with EDAS to implement service registration and configuration management. EDAS Registration Configuration Center: a free service registration and configuration center that is provided by EDAS. If your application requires high performance and stability, we recommend that you use MSE Nacos as the service registration and configuration center.
   MSE Nacos Instance	The Nacos instance that is created by using MSE. For more information, see Create a Nacos engine.
   Region	The region in which the microservice namespace resides. This parameter is autopopulated and cannot be modified.
   Allow Remote Debugging	If you want to connect on-premises applications and cloud applications, turn on Allow Remote Debugging.
   Description	Enter a description for the microservice namespace.

Modify a microservice namespace

1. On the Microservice Namespace page, find the microservice namespace that you want to modify and click Edit in the Actions column.

2. In the Edit Microservice Namespace dialog box, modify the microservice namespace based on your business requirements. You can change the name and description or enable or disable remote debugging for the microservice namespace. After you modify the microservice namespace, click OK.

Delete a microservice namespace

1. On the Microservice Namespace page, find the microservice namespace that you want to delete and click Delete in the Actions column.

2. In the message that appears, click Delete.