Micro Service Engine MSE Heavy Upgrade

Publishing the Enterprise Edition of Micro Service Governance

On top of the original Basic and Professional editions, MSE has launched the Enterprise Edition of Microservice Governance, providing traffic control and fault tolerance capabilities for microservice applications and commonly used gateways. It ensures business stability from multiple dimensions such as traffic control, concurrency control, fuse degradation, adaptive protection, and hotspot prevention and control, helping users cope well with traffic surges or unstable service dependencies.

At the microservice gateway layer, such as Zuul and Spring CloudGateway, users can set rules for entry traffic protection. At the application layer, interface level granularity protection can be implemented, supporting multiple current limiting methods such as single machine current limiting, cluster current limiting, and minute hour current limiting. In addition to the impact of high traffic, problems with third-party services can sometimes lead to longer interface response times and inability to release thread resources. Users can configure fuse rules for weakly dependent interfaces, which automatically fuse when unstable conditions are reached. For non critical interfaces, they can be proactively downgraded in advance to avoid overall unavailability caused by single point service exceptions. In addition, traffic protection supports adaptive system protection, which can set system protection rules based on system resource indicators such as CPU and load to prevent avalanches. At the same time, you can also configure isolation rules for automatically identified slow SQL statements to limit the number of concurrent executions and prevent the database Connection pool from being full and affecting normal calls.

The enterprise version also supports second level monitoring capabilities for indicators such as QPS, response time, exceptions, CPU/load, and provides analysis functions for second level flow and water level distribution in machine dimensions, interface dimensions, and cluster dimensions for these indicators, facilitating users to monitor protection effects and guide rule configuration.

In addition, the Service Governance Center has added application configuration capabilities to help users dynamically manage configuration items in their code, which can be used in various business scenarios. One is to embed functional switches in the business logic, such as dynamically opening a promotional activity, demoting certain time-consuming operations, etc; Second, the application operation level can be adjusted without application restart, such as online modification log level, specifying A/B Test path, thread pool configuration, etc; The third is the push of complex types of structured content such as List and Map, such as regularly pushing the list of promotional products, and uniformly sending the customer list of discount coupons.

The prices for the Basic, Professional, and Enterprise editions are as follows:

For more information on the differences between the three versions, please visit: https://help.aliyun.com/document_detail/333528.html

Open Source Service Governance Specification and Implementation of OpenSergo

Micro service governance is an inevitable challenge to be solved in the process of managing micro services, but there are generally the following pain points in the industry:

High cost of understanding and communication: The industry lacks a clear understanding of the capabilities and boundaries of microservice governance, and the service governance concepts defined by each enterprise are inconsistent, resulting in high understanding and communication costs.

Lack of standardized conventions: There are many open source microservice frameworks, such as the microservice interfaces defined in Spring Cloud and Dubbo, which cannot be interconnected. Go and Java have different architectures and cognitions.

Lack of business oriented abstractions and standards: For business development, it is not only necessary to understand the deployment architecture of different microservice frameworks, but also to understand the concepts and differences of different service governance methods.

OpenSergo, co sponsored by bilibili, ByteDance, and the Spring Cloud Alibaba, Nacos, and Apache Dubbo/dubo go communities, is a set of specifications and implementation of microservice governance. It aims to solve the problem of fragmentation and interoperability of microservice governance concepts in different frameworks and languages. For example, how to standardize service registration and discovery, how to unify the meta information format of services, and so on.

OpenSergo @GithHub：github.com/opensergo/opensergo-specification

The capabilities provided by OpenSergo can be viewed from three dimensions: control, data, and spec

Control surface: Users can view and modify service governance configurations through CRD or Dashboard, and distribute these control information to the data surface.

• Data side: JavaAgent, Servcie Mesh, and various microservice frameworks connected to OpenSergo can receive service governance configurations and apply them to current business traffic.

OpenSergo Spec: Spec specifies communication protocols for control and data surfaces, ensuring that users can describe microservice architectures of different frameworks, protocols, and languages using a single Spec, eliminating the need for developers to focus on underlying differences.

Next generation gateway - Cloud native gateway upgrade

Gateways are divided into traffic gateways and business gateways. Traffic gateways mainly provide global and backend business independent policy configurations, such as the unified access gateway Tengine within Alibaba, which is a typical traffic gateway; As the name suggests, Business Gateways mainly provide independent business domain level, tightly coupled with backend business policy configuration. With the evolution of application architecture mode from single entity to distributed microservices, Business Gateways have also gained a new name - Microservice Gateways.

But in the cloud native era dominated by containers and Kubernetes, Ingress has become the gateway standard for the Kubernetes ecosystem, combining traffic gateways and microservices gateways. Transforming two layers of gateways into one layer not only saves 50% of resource costs, but also reduces operational and usage costs.

The cloud native gateway provided by MSE has once again upgraded its core capabilities, including seamless support for Nginx Ingress annotation conversion, support for Waf local protection, support for plugin marketing, and support for HTTP to Dubbo conversion. Taking seamless support for Nginx Ingress annotation conversion as an example, the MSE Ingress Controller obtains changes in Ingress resources in the associated ACK cluster through the List Watch mechanism, and then dynamically updates the routing rules of the MSE cloud native gateway through hot updates. When the MSE cloud native gateway receives a request, it matches the Ingress forwarding rule to forward the request to the corresponding Pod of the backend service.

Compared to Nginx Ingress Controller, MSE Ingress Controller is a hot update method that takes effect on the Ingress resources that are monitored in seconds. This method of configuring without restarting the data plane greatly improves the stability of the cluster gateway and effectively ensures the lossless business traffic. More importantly, the MSE Ingress Controller can manage multiple clusters, serving as the gateway to multiple clusters at the same time. This means that it can simultaneously listen to Ingress resources in multiple clusters, solving traffic scheduling and governance issues for users across Kubernetes clusters.

In addition to micro service semi hosted products such as MSE, during this upgrade conference, the advantages and characteristics of MSE+SAE's fully hosted solution were also shared, and combined with serverless technology, the utilization rate of computing resources was further improved, with low threshold containerization transformation and Kubernetes transformation.

MSE provides commercialization enhancement for ZooKeeper, Nacos, Consul, Envoy and other open source projects, serving enterprises such as Skechers, Caller Technology, Play More, Helian Health, Master Wan, Cloud Goods Selection, Shanghai Mitsubishi, Salesforce China, and has become one of the preferred microservice platforms for domestic cloud customers.