This topic describes how to use the features of Microservices Governance, including connecting applications, querying services, governing applications, implementing end-to-end canary releases, and managing system settings.
Connect applications
MSE Microservices Governance offers several connection methods. The method you choose depends on your application's deployment environment and programming language.
Manage microservice namespaces
A microservice namespace is an extensible method for organizing and grouping microservices and their dependencies to simplify management and distribution. This allows teams to assign different security policies, access controls, and resource limits to the microservices. For more information, see Manage microservice namespaces.
Connect Java microservice applications in ACK and ACS clusters to the MSE governance center
You can connect microservice applications, such as Spring Cloud and Dubbo applications, that are deployed in Container Service for Kubernetes (ACK) and Container Compute Service (ACS) clusters to the MSE governance center. For more information, see Connect Java microservice applications in ACK and ACS clusters to the MSE governance center.
Connect microservice applications on ECS instances to the MSE governance center
You can connect applications deployed on Elastic Compute Service (ECS) instances and non-Alibaba Cloud virtual machines (VMs) to the MSE governance center. For more information, see Connect microservice applications on ECS instances to the MSE governance center.
Connect applications in open source Kubernetes environments to the MSE governance center
You can connect Spring Cloud and Dubbo applications in open source Kubernetes environments to the MSE governance center. This provides features such as graceful shutdown, outlier ejection, service query, service authentication, service testing, and canary release. These features significantly improve the stability and development efficiency of your online microservice applications. For more information, see Connect applications in open source Kubernetes environments to the MSE governance center.
Add custom interfaces to Microservices Governance
You can connect applications to MSE Microservices Governance by combining custom instrumentation of the Java SDK with a Java agent. For more information, see Add custom interfaces to Microservices Governance.
Network configuration for connecting to Microservices Governance from a non-Alibaba Cloud VPC
To connect to MSE Microservices Governance from a non-Alibaba Cloud virtual private cloud (VPC), see Network configuration for connecting to Microservices Governance from a non-Alibaba Cloud VPC.
Service query
You can use the service query feature of Microservices Governance to view service details and contract information for your connected applications.
Query services
After you connect your services to MSE Microservices Governance, you can use the MSE console to query service lists and details of your deployed Spring Cloud or Dubbo applications. For more information, see Query services.
Query service contracts
A service contract describes the interfaces and behavior of a microservice. In MSE, a service contract defines the communication rules between a provider and a consumer. It can also contain information about the service's input, output, and error handling. This information helps the consumer better understand and use the service. For more information, see Query service contracts.
Application governance
For applications connected to MSE Microservices Governance, you can use traffic governance features. These features include graceful startup and shutdown, system protection configuration, traffic protection, tag-based routing, and canary release for messaging.
Application overview
After connecting a service to MSE Microservices Governance, you can go to the Application overview page in the MSE console to view information such as queries per second (QPS) data and top lists. For more information, see Application overview.
Interface details
The Interface details page displays the details of all interfaces for an application, including statistical data for QPS, response time (RT), and concurrency. You can click the tabs for different interface types, such as web services and RPC services, to view the details page for each type. For more information, see Interface details.
Node details
You can use the node details feature to view basic information about all nodes of an application. This information includes statistical data, such as QPS, and basic node data, such as tags and status. For more information, see Node details.
Traffic governance
The traffic governance feature is used for traffic control to implement load balancing and fault tolerance for microservice instances. You can use features such as peak-load shifting and traffic throttling to ensure the high availability and concurrent processing capabilities of your microservice instances. For more information, see Traffic governance.
End-to-end canary release
A canary release is a deployment strategy that distributes traffic across multiple versions of an application for iteration and maintenance without affecting the production system. You can use MSE to implement an end-to-end canary release for a specific microservice instance. This method provides fine-grained traffic control and helps you more accurately evaluate the quality and stability of the microservice.
Implement an end-to-end canary release based on an MSE cloud-native gateway
After you connect an application to Microservices Governance, you can configure an MSE cloud-native gateway to implement an end-to-end canary release. The cloud-native gateway is used to expose backend services. For more information, see Implement an end-to-end canary release based on an MSE cloud-native gateway.
Implement an end-to-end canary release based on a cloud-native API gateway
You can use a cloud-native API gateway with services that are deployed in a backend Container Service for Kubernetes (ACK) cluster or registered with MSE Nacos to implement the end-to-end canary release feature. For more information, see Implement an end-to-end canary release based on a cloud-native API gateway.
End-to-end canary release based on an MSE Ingress
An MSE Ingress gateway provides an Ingress-based traffic management method that is built on the MSE cloud-native gateway. The end-to-end canary release capability of the MSE Ingress gateway lets you implement end-to-end traffic control without modifying business code. For more information, see End-to-end canary release based on an MSE Ingress.
Implement an end-to-end canary release based on a self-managed Spring Cloud Gateway or Zuul gateway
If the API gateway in your microservices model uses Spring Cloud Gateway or Zuul, you can configure routing rules to route requests to a canary environment. This lets you verify and test the canary release version. For more information, see Implement an end-to-end canary release based on a self-managed Spring Cloud Gateway or Zuul gateway.
Implement an MSE-based end-to-end canary release with Kruise Rollouts
Kruise Rollouts offers multiple phased release policies, such as canary release and blue-green deployment. By combining Kruise Rollouts with MSE Microservices Governance, you can implement seamless canary upgrades for new application versions in the service invocation chain. This ensures the stability of the new versions. For more information, see Implement an MSE-based end-to-end canary release with Kruise Rollouts.
Asynchronous task support for MSE end-to-end canary release
MSE supports custom asynchronous tasks to implement traffic tag pass-through. To do this, you can add a scan package for asynchronous pass-through. For more information, see Asynchronous task support for MSE end-to-end canary release.
System settings
You can manage MSE Microservices Governance settings as needed.
Upgrade the MSE Microservices Governance component
The MSE Microservices Governance component is updated. You can upgrade the older ack-mse-pilot component to the ack-onepilot component. For more information, see Install and upgrade the MSE Microservices Governance component.
Disable MSE Microservices Governance
If your application no longer uses the features of the MSE governance center, you should promptly disable MSE Microservices Governance. For more information, see Disable MSE Microservices Governance.