Microservices Governance provided by Microservices Engine (MSE) isolates resources and configurations across different environments using microservices namespaces. This topic describes how to organize your microservices in MSE based on microservices namespaces and how to manage microservices namespaces.
What is a microservices namespace?
In most cases, resources in production, test, and development environments are isolated from each other. MSE Microservices Governance strictly isolates microservices governance configurations of applications in different microservice namespaces. Therefore, when the same microservice application is deployed in different environments, the application has its own independent microservices governance configuration in each environment. In such cases, you can use microservices namespaces to isolate applications in different environments.
Microservices namespaces and Kubernetes namespaces are separate concepts. When you connect an application to MSE, you can add the label mseNamespace: ${Namespace name} to the pod or its corresponding Kubernetes namespace to specify the application's namespace in MSE.
What is an application in MSE Microservices Governance?
A microservice application typically refers to a Java process that provides a set of microservices. A microservice application independently handles cohesive business logic and has dedicated developer and operations and maintenance (O&M) personnel.
In terms of deployment mode, one MSE Microservices Governance application corresponds to a group of deployments.
When you connect an application by adding the labels mseNamespace: prod and msePilotCreateAppName: ${Application name} to the pod, the application is connected to the corresponding application within the prod microservices namespace. The application name can be up to 63 characters long.
Scenarios
Environment management: You can use the Prod, Test, and Dev microservices namespaces to isolate different environments and their resources.
Resource isolation: In different environments, application governance configurations in different microservices namespaces are strictly isolated and do not take effect across namespaces.
Example 1:
In a real-world scenario, you can connect all applications in your test environment to the
testmicroservices namespace (for example,test/example-app) and all applications in your production environment to theprodmicroservices namespace (for example,prod/example-app). To use an MSE Microservices Governance feature, you can configure and verify it on thetest/example-appapplication. After successful verification, you can apply the same configuration to theprod/example-appapplication.NoteWe recommend that you use separate databases, Message Queue clusters, Kubernetes clusters, and Nacos instances for different microservices namespaces. This prevents changes in the test environment from affecting the production environment and ensures stability.
Example 2:
Three environments are built in a virtual private cloud (VPC) and are separately used for application development, testing, and production. You can create the Dev, Test, and Prod microservices namespaces for the environments. If you create clusters and deploy applications in the microservices namespaces, the applications in one namespace are isolated from those in the other namespaces.
Versions of microservices namespaces
Microservices Governance provides the Professional Edition and Enterprise Edition. Different editions have different features and different prices. For users who use the Enterprise Edition, some applications such as those in the development environment may not require the protection feature in the Operation State (Ops). In this case, you can downgrade the microservices namespaces for these applications from the Enterprise Edition, which is the default edition, to the Professional Edition. This helps meet the requirements of accessing MSE from different environments.
For more information about the billing of Microservices Governance, see Billing overview of Microservices Governance.
Use microservices namespaces
Create a microservices namespace
Log on to the MSE console.
In the navigation pane on the left, choose Microservices Governance > O&M Center.
On the O&M Center page, click the name of the desired Kubernetes cluster.
On the Cluster details page, click Microservice Namespace in the Actions column.
Enter a name in the Microservice Namespace dialog box, and click OK.