Microservices Engine (MSE) provides three modules: Microservices Registry, Microservices Governance, and Cloud-native Gateway. These modules provide you with a series of high-performance and highly available enterprise-class cloud service capabilities. This topic describes the features of the modules provided by MSE.
Microservices Registry
Feature | Description | References |
Service management | This feature allows you to query and manage services on a Nacos or Eureka instance in a visualized manner. This feature facilitates the management of services that are registered with instances. | |
Data management | This feature allows you to query and update data on a ZooKeeper instance in a visualized manner. This feature helps you focus on business data. | |
Observation analysis | This feature visualizes engine metrics, such as the number of connections, transactions per second (TPS), and queries per second (QPS). This feature helps you identify system bottlenecks. | |
Alert management | This feature allows you to receive alerts by using text messages, emails, or DingTalk. This way, you can keep track of business exceptions in real time. | |
Cloud migration | MSE provides the cloud migration feature. When you use this feature, you can use MSE Sync, a GUI-based migration tool, to synchronize information between the source and destination instances. This way, the client can obtain information from both the source and destination instances. | Migrate self-managed instances to MSE Microservices Registry |
Configuration management | This feature allows you to create, synchronize, view, edit, and delete configurations. |
Microservices Governance
Feature | Description | References |
Service query | This feature allows you to query the service list and service details of deployed applications, including the basic service information, service call relationships, and metadata. | |
Graceful shutdown | This feature allows you to shut down online applications without interrupting services. In this process, service consumers are unaware of application shutdown. All applications that access MSE support this feature. No additional operations are required. | |
Graceful start | For a to-be-released application, the graceful start feature provides a series of capabilities to ensure the secure release of the application. The capabilities include service prefetching, delayed registration, and alignment of the microservices lifecycle and Kubernetes lifecycle. | |
Tag-based routing | This feature allows you to allocate one or more service providers to the same group by using tags. This way, you can forward traffic to service providers in specific groups. | |
End-to-end canary release | This feature allows you to create lane rules to add one or more applications of the same version to the same lane. This way, traffic is forwarded in the specified lane and end-to-end traffic isolation is implemented. | |
Traffic protection | This feature ensures service stability in multiple aspects, such as traffic throttling, isolation control, hotspot parameter protection, and web protection. This feature provides professional and stable traffic protection methods and second-level traffic usage distribution analysis. | |
Microservice testing | This feature allows you to test microservice applications. You can initiate service calls in the MSE console. | |
Outlier ejection | This feature allows you to monitor the availability of Spring Cloud and Dubbo application instances and dynamically add or remove application instances. This ensures successful service calls and improves service stability and quality of service (QoS). |
Cloud-native Gateway
Feature | Description | References |
Security authentication | Cloud-native gateways are integrated with a logon authentication system to ensure the security of services. Cloud-native gateways support HTTPS certificates, IP address blacklists, authentication, and suspicious traffic scrubbing. The authentication types include JSON Web Token (JWT) authentication, OpenID Connect (OIDC) authentication, and Alibaba Cloud Identity as a Service (IDaaS) authentication. | |
Observability | This feature provides capabilities, such as global dashboards, gateway instance monitoring, log retrieval, top N service lists, log shipping, tracing analysis, and alert management. | |
Route configurations | This feature provides multiple service governance capabilities, such as throttling, service degradation, service discovery, service routing, multi-registry support, traffic tagging, canary release, and timeout configuration. | |
High availability | Cloud-native gateways provide the throttling and circuit breaking capabilities. These capabilities help you build a highly available system from the traffic ingress to handle traffic surges. Cloud-native gateways also provide the multi-zone deployment, automatic detection, and automatic repairing capabilities. | |
Service management | This feature allows you to add, delete, modify, and query services. This way, you can add the services in the service list and their backend node addresses to cloud-native gateways. | |
Service source management | Cloud-native gateways support the following types of service sources: Container Service for Kubernetes (ACK) or serverless Kubernetes (ASK) clusters, Enterprise Distributed Application Service (EDAS) registries, Serverless App Engine (SAE) registries, MSE ZooKeeper instances, and MSE Nacos instances. These service sources help gateways dynamically obtain your backend service list. | |
Domain name management | Cloud-native gateways provide the multi-domain name management capability. This capability allows you to manage protocols, certificates, and route configurations of different domain names. |