MSE products include the following modules: microservice registration center, microservice governance, and cloud native gateway.

By choosing the microservice engine MSE, you can achieve full hosting of the application registration and configuration center, service governance, and cloud-native gateway technology, and easily build resources with the following advantages:

Container service ACK

Service Mesh ASM

Application High Availability Service AHAS

Application real-time monitoring service ARMS

Application Configuration ManagementACM

Link Tracing Tracing Analysis

Message queue Kafka version

functional module Feature details Related documents Service management Supports visual service query and management of Nacos and Eureka, making it easier to manage accessed services. Management services Data management Supports ZooKeeper visual data query and update, allowing you to focus on business data. Manage data Observation analysis Supports visual engine monitoring indicators, including monitoring of connections, TPS, QPS and other indicators, helping you locate system bottlenecks. Nacos monitoring engine ZooKeeper monitoring engine Alarm management Supports receiving alarms through SMS, email, and DingTalk, so you can keep track of abnormal business dynamics in a timely manner. Manage alarm contacts Migrate to the cloud The cloud migration capability provided by MSE uses the MSE Sync white-screen migration tool to synchronize the information of the source cluster and the target cluster. The client can perceive all the information of the source cluster and the target cluster. Migrate to the cloud Configuration management Supports creating, synchronizing, viewing, editing and deleting configurations. Create configuration

functional module Feature details Related documents Service inquiry Supports querying the service list and service details of deployed applications, including basic information, service calling relationships, metadata, etc. Inquiry service Offline without loss For any online application, lossless offline can realize service consumers without being aware of it and maintain business continuity without loss. It is supported by applications connected to the platform by default and does not require any additional operations. Configuration lossless offline Lossless launch For any application to be released, lossless launch ensures the safe release of the application by providing a series of functions such as service warm-up, delayed registration, and alignment of the microservice life cycle with the K8s life cycle. Configuration lossless online label routing Classify one or more service providers into the same group through labels, thereby restricting traffic to only flow in the specified group, and achieving traffic isolation. Configure label routing Full link grayscale By creating swim lane rules, the same versions of one or more applications are divided into the same swim lane, thereby restricting traffic to only flow in the designated swim lane, and achieving full-link traffic isolation. Configure full-link grayscale based on Java microservice gateway Full-link grayscale based on MSE Ingress Traffic protection Traffic protection takes traffic as the entry point and ensures business stability from multiple dimensions such as flow control, isolation control, hotspot parameter protection, and Web protection. It provides more professional and stable traffic protection methods and second-level traffic level distribution analysis functions. Configure flow control rules Configure isolation rules Configure circuit breaker rules Configure hotspot rules Microservice testing Provides the testing function of microservices, and you can easily initiate calls to services through the console. Test service Remove outliers Detect the availability of Spring Cloud and Dubbo application instances and make dynamic adjustments to ensure successful service calls, thereby improving business stability and service quality. Remove outliers Service authentication When one of your microservice applications has security requirements, you can authenticate other applications that call the application, and only allow calls from applications that match the authentication rules. Configure service authentication

functional module Feature details Related documents safety certificate Integrated authentication login system allows businesses to quickly build security barriers, supporting HTTPS certificates, IP blacklists, authentication and authorization (including JWT, OIDC and IDaaS), and abnormal traffic cleaning. Set gateway IP blacklist and whitelist Gateway Authentication Overview Associated domain names Observability Supports functions such as global dashboard, gateway instance monitoring, log retrieval, business top list, log delivery, link tracking, and alarm management. View gateway monitoring data Enable gateway log delivery Enable gateway link tracking Manage alert rules Routing configuration Supports service governance functions such as current limiting and downgrading, service discovery, service routing, multiple registration centers, traffic marking, canary publishing, and timeout configuration. Routing Overview Configure timeout policy Configure rewrite policy Configure current limiting policy Configure Header setting policy Configure cross-domain resource sharing policy Configure retry strategy High availability Integrated current limiting and circuit breaker capabilities help businesses build a high-availability system from the entrance, prevent large promotion peaks from overwhelming the system, and provide multi-availability zone deployment, automatic detection, and fault self-healing capabilities. Create a new cloud native gateway MSE Ingress Overview Manage alarm contacts Service management Supports adding, deleting, modifying, and checking services, making it easy for you to add services in the service list and their backend node addresses to the gateway. Add service Change service Delete service View services Manage service version Manage service traffic rules Configuring active health checks for services Service source management Supports multiple service sources such as container services (including ACK and ACK Serverless clusters), EDAS registration center, SAE registration center, MSE ZooKeeper, and MSE Nacos, allowing the gateway to dynamically obtain your backend service list. Create a new service source Modify service source Delete service source Domain name management The cloud native gateway provides multi-domain name management capabilities, making it easy for you to manage protocols, certificates, and routing configurations under different domain names. Associated domain names Change domain name Delete domain name

The MSE registration and configuration center can realize service registration and discovery, configuration management, distributed data management and other functions, and supports multiple engine types (compatible with Nacos, ZooKeeper and Eureka). Can be applied to the following business scenarios.

Microservice registration and discovery

Distributed scheduling (supports non-microservice scenarios)

Recommended to use with:

In the process of microservices going online, we rely on the microservices governance capabilities provided by MSE. You can obtain the following capabilities without modifying any code or configuration.

Comprehensive elimination of risks in the change process

Comprehensive elimination of risks caused by accidental problems

Implement agile development of microservices at low cost

Recommended to use with

Traffic gateways (such as Nginx) provide global policies that have nothing to do with back-end business applications, such as HTTPS certificate offloading, web firewalls, global traffic monitoring, etc. Microservice gateway (such as Spring Cloud Gateway) refers to a policy that is tightly coupled with the business and provides a single business domain level, such as service governance, identity authentication, etc. The MSE cloud native gateway turns the two-layer gateway into one layer, which not only saves 50% of resource overhead, but also reduces operation, maintenance and usage costs.

In the traditional gateway model, the traffic gateway is responsible for north-south traffic scheduling and security protection, and the microservice gateway is responsible for east-west traffic scheduling and service governance. In the next-generation gateway model, the cloud native gateway is responsible for east-west, north-south traffic scheduling, security protection, and service governance. The deployment structure diagram is as follows:

Authentication is a fundamental requirement for gateways. The MSE cloud native gateway not only provides conventional JWT authentication, but also provides OIDC authentication based on the authorized open network standard OAuth 2.0. At the same time, the MSE cloud-native gateway also supports Alibaba Cloud's application identity service IDaaS, which helps you realize third-party authentication logins such as Alipay, Taobao, and Tmall, and supports extended authentication and authentication functions in the form of plug-ins to reduce security access costs.

The MSE cloud native gateway is responsible for east-west, north-south traffic scheduling, security protection and service management. The schematic diagram of the authentication and authentication function is as follows: