Shulou(Shulou.com)06/01 Report--

This article mainly explains "why Dubbo needs service governance". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn why Dubbo needs service governance.

Service governance is mainly aimed at multi-services, micro-services and so on under the current distributed architecture.

Service is a medium-sized part of a distributed system, with the composition of services, the whole system can be alive.

With the growth of business, services can not blindly grow, the need for management, governance. A distributed system without service governance will not necessarily fail, but as the business grows, the system will be painful.

Objectives of service governance

Strictly speaking, service governance should be divided into three stages, including the entire life cycle of the service.

Among them, the service design period is mainly aimed at the design period and development period of the service, while the service operation period is mainly aimed at the operation of the service after the service is online. Finally, the continuous governance of the service adheres to the concept of "division and integration" and carries out the elimination system to the end.

Let's talk about three periods that require complete work:

Service design period:

Program review, development test review, certification issued, service discoverable

Policy management

Contract definition, negotiation

Standardized quality of service agreement

Service run time:

System records: recording information exchanged

Service management system: control, configure services and run-time components, reconfigure the environment according to abnormal conditions

Service monitoring system: collecting data, visualization, providing matching evidence

Quality of service assurance system: enhance message and run-time strategy, security, reliability, transactionality, audit, etc.

Service continuous governance:

Service asset management: evaluate and analyze service repositories, identify opportunities for service reuse, assist in asset integration, and reduce redundancy

Based on the above objectives, we can determine:

Service governance runs through the entire lifecycle of the service, including pre-development design, development and testing, operation, and subsequent management.

The service design period is mainly aimed at the design review of services and the formulation of standards.

The running period of service governance focuses on management and monitoring. In order to achieve the goal of running well, the operation status is analyzed through data, and anomalies and transformations are eliminated through automation.

The focus in the later stages of service governance is on eliminating redundancy.

Design of service governance platform

Combined with the registries and monitoring centers of most architectures, an approximate architecture diagram can be constructed:

Combined with Dubbo analysis

In the development process of the service governance platform, the development difficulties and design service complexity should be placed on service registration and service monitoring.

Dubbo is a high-performance service framework, which aims to provide high-performance and transparent RPC remote service invocation solutions, as well as SOA service governance solutions, so that applications can realize the output and input functions of services through high-performance RPC, and can be seamlessly integrated with the Spring framework.

Analysis of problems

With the continuous growth of business, in order to pursue higher performance to support the business, the introduction of clusters greatly increases the complexity of the service architecture. Large clusters are prone to all kinds of problems:

Too many service URL configuration difficulties

In the case of excessive pressure on load balancing distribution nodes, it is also necessary to deploy clusters.

Service dependency is chaotic and the startup sequence is not clear

Too many services make it difficult to analyze performance indicators and need to be monitored.

Architecture analysis

The introduction of Dubbo registry and monitoring center is the key to service governance.

Key points of the registry:

The service provider registers the services it provides with the registry

The service consumer obtains the address list of the service provider from the registry and selects the service provider with the load balancing algorithm.

Key points of the monitoring center:

Service consumers and providers accumulate the number and time of calls, and regularly send statistics to the monitoring center.

After the business is introduced into the architecture, it must be ensured that the impact on the stability of the current business can only be positive or no impact, not negative impact.

Consider the impact of the architecture on stability:

When the registry is down, consumers cache the list of providers locally, so the business is not affected for the time being, but they can no longer register new services.

When the monitoring center is down, the service will not be affected, only part of the sampled data will be affected.

After the downtime of the service provider, the request can be sent to other providers of the same service through the load balancing algorithm, which has a positive effect on robustness.

The introduction of registry and monitoring center improves the stability of operation to a great extent and corresponds to the work of service governance.

Consider the impact of the architecture on other aspects:

Services can be added dynamically, and unified and dynamic allocation by the registry

Consumers can be dynamically increased, and unified and dynamic allocation by the registry

Thus it can be seen that the introduction of the registry improves scalability and corresponds to the work required during the run-time of service governance.

With the introduction of the monitoring center, the benefits of data collection and analysis are also obvious, corresponding to the service monitoring in the running period of service governance and the service asset management under the continuous governance of service governance.

Thank you for your reading, the above is the content of "Why Dubbo needs service governance". After the study of this article, I believe you have a deeper understanding of why Dubbo needs service governance, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.