Microservices Governance provided by Microservices Engine (MSE) isolates resources and configurations across different environments by 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 differ from Kubernetes namespaces. To enable Microservices Governance for your application, you can add the label mseNamespace: ${Namespace name} for your pod or Kubernetes namespace to specify the microservices namespace of the application.
What is a microservice application?
A microservice application is a Java process that provides a group of microservices. A microservice application can separately implement cohesive business logic of microservices and requires support from dedicated maintenance and development engineers.
In MSE Microservices Governance, one microservice application corresponds to a group of deployments in terms of deployment modes.
To enable Microservices Governance for applications in the prod microservices namespace, you can add the labels mseNamespace: prod and msePilotCreateAppName: ${Application name} for your pod. The length of application names cannot exceed 63 characters.
Use cases
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:
You can connect all applications in the test environment to a microservices namespace named
test. For example, you can connect an application named example-app to the test microservices namespace. You can also connect all applications in the production environment to a microservices namespace namedprod. For example, you can connect an application named example-app to the prod microservices namespace.If you want to use the features of Microservices Governance provided by MSE, you can configure and verify the features on theexample-appapplication in the test microservices namespace. If the verification is successful, perform the same operations on theexample-appapplication in the prod microservices namespace.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 left-side navigation pane, 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.