When multiple teams or environments share a Virtual Private Cloud (VPC), services and configurations can interfere with each other. Microservices namespaces in Enterprise Distributed Application Service (EDAS) solve this by isolating resources, services, and configurations at the namespace level. Each namespace acts as an independent boundary -- applications in one namespace cannot discover or call services in another, and configuration pushes stay scoped to their origin namespace.
How namespace isolation works
After you create namespaces and deploy applications into them, EDAS enforces the following isolation boundaries:
| Resource | Isolated? | Details |
|---|---|---|
| Service discovery and calls | Yes | Applications in one namespace cannot discover or invoke services in another |
| Configuration pushes | Yes | Configurations are scoped to the namespace where they originate |
| Clusters | Yes | Each cluster is associated with a specific namespace |
| ECS instances | Yes | Each Elastic Compute Service (ECS) instance is associated with a specific namespace |
| Applications | Yes | Each application is associated with a specific namespace |
The default namespace does not enforce these isolation boundaries. For production workloads, always create a dedicated namespace.
Default namespace
Every region includes a built-in default microservices namespace. Applications in this namespace are not isolated -- their resources and services remain accessible without namespace-level boundaries.
On the Applications page, if you select Default Microservices Namespace in a region, the listed applications do not belong to any microservices namespace.
Create a microservices namespace
Log on to the EDAS console.
In the left-side navigation pane, choose Resource Management > Microservices Namespaces.
In the upper-right corner of the Microservices Namespace page, click Create Microservices Namespace.
In the Create Microservices Namespace dialog box, configure the following parameters and click Create.
Parameter Description Microservices Namespace Name of the namespace. Must be unique within the region. Microservices Namespace ID Custom identifier for the namespace. Only letters and digits are allowed. Registration and Configuration Center Service registration and configuration backend. Select one of the following: - MSE Nacos -- A Microservices Engine (MSE) Nacos instance that you purchased. Integrates seamlessly with EDAS for service registration and configuration management.
- EDAS Registration and Configuration Center -- A free registration and configuration center provided by EDAS. If your application requires high performance and stability, we recommend that you use MSE Nacos.
MSE Nacos Instance Nacos instance created through MSE. For more information, see Create a Nacos engine. Region Region for the namespace. This value is pre-populated and cannot be changed. Allow Remote Debugging Turn on this toggle to connect to cloud-deployed applications from an on-premises computer for remote debugging. Description Optional description of the namespace. 
Modify a microservices namespace
On the Microservices Namespace page, find the target namespace and click Edit in the Actions column.
In the Edit Microservices Namespace dialog box, update any of the following settings:
Namespace name
Description
Allow Remote Debugging toggle (turn on or turn off)
Click OK.
The AccessKey ID and AccessKey secret that are automatically generated for a namespace cannot be modified after creation.
Delete a microservices namespace
Before you delete a namespace, make sure that all of the following conditions are met:
The namespace contains no clusters
The namespace contains no microservices applications
The namespace contains no ECS instances
If any of these resources exist in the namespace, remove or migrate them first.
Procedure
On the Microservices Namespace page, find the target namespace and click Delete in the Actions column.
In the confirmation dialog box, click Delete.
Best practices
Separate environments by namespace. Create dedicated namespaces such as
Dev,Test, andProdto prevent configuration and service conflicts across environments.Use MSE Nacos for production. If your application requires high performance and stability, use MSE Nacos as the registration and configuration center.
Avoid the default namespace for production. The default namespace does not enforce isolation. Always create a dedicated namespace for production applications.