Microservice namespaces provide applications with isolated runtime environments, such as the development, testing, and production environments. You can use microservice namespaces to isolate resources and services. You cannot create two microservice namespaces that have the same name in the same region.
Scenarios
For example, you have three environments in a virtual private cloud (VPC), which are used for application development, testing, and production. You can create the Dev microservice namespace for application development, create the Test microservice namespace for testing, and create the Prod microservice namespace for production. Resources, applications, and services in different microservice namespaces are isolated from each other. You cannot call services or push configurations across microservice namespaces.
Default microservice namespace
When you create an application in Enterprise Distributed Application Service (EDAS), you can select the default microservice namespace. Then, the application does not use microservice namespaces to isolate resources and services.
If you select the default microservice namespace of a region on the Applications page, the displayed applications do not belong to microservice namespaces.
Create a microservice namespace
Modify the configurations of a microservice namespace
- In the microservice namespace list, find the microservice namespace and click Edit in the Actions column.
- In the Edit Microservice Namespace dialog box, you can modify the Microservice Namespaces and Description parameters. You can also enable or disable the remote debugging feature. Then, click OK.
Delete a microservice namespace
- No clusters belong to the microservice namespace.
- No microservice-oriented applications belong to the microservice namespace.
- No Elastic Compute Service (ECS) instances belong to the microservice namespace.
- In the microservice namespace list, find the microservice namespace and click Delete in the Actions column.
- In the OK message that appears, click Delete.