CN112272228A

CN112272228A - Distributed registry architecture

Info

Publication number: CN112272228A
Application number: CN202011141885.9A
Authority: CN
Inventors: 陈宏鸿; 范兴泽; 彭彰苗; 朱海东
Original assignee: Beijing Shenzhou Digital Technology Co ltd
Current assignee: Beijing Shenzhou Digital Technology Co ltd
Priority date: 2020-10-22
Filing date: 2020-10-22
Publication date: 2021-01-26

Abstract

The invention provides a distributed registration center architecture. The architecture includes: the client SDK is used for accessing the client system to the distributed registration center; the Proxy agent layer is used for virtually enabling the data nodes to be N virtual slices, calculating a hash value according to the service identifier after receiving a request of the client SDK, and routing to the specific data nodes according to the hash value; the data persistence layer comprises a plurality of data nodes and is used for performing distributed storage on the microservices and providing registration services according to the received requests; and the management console is used for managing each component of the distributed registration center. The distributed registration center framework provided by the invention can solve the problem of bottleneck existing in the registration of the service instance in the registration center.

Description

Distributed registry architecture

Technical Field

The invention relates to the technical field of micro-service architecture, in particular to a distributed registration center architecture.

Background

With the development of industrial technology, more and more enterprises and organizations are transforming the technical architecture and constructing the micro-service of the system.

For large enterprises and organizations, a certain bottleneck exists in the registration examples and service continuity of popular registration centers (such as Eureka, Zookeeper and Nacos) in the market at present, and when the number of service examples reaches a certain amount, the service examples can cause very large performance influence on the whole business system, even normal operation of the system.

Disclosure of Invention

The technical problem to be solved by the invention is to provide a distributed registration center architecture, which can solve the problem of bottleneck existing in registering a service instance in a registration center.

To solve the above technical problem, the present invention provides a distributed registry architecture, where the architecture includes: the client SDK is used for accessing the client system to the distributed registration center; the Proxy agent layer is used for virtually enabling the data nodes to be N virtual slices, calculating a hash value according to the service identifier after receiving a request of the client SDK, and routing to the specific data nodes according to the hash value; the data persistence layer comprises a plurality of data nodes and is used for performing distributed storage on the microservices and providing registration services according to the received requests; and the management console is used for managing each component of the distributed registration center.

In some embodiments, the client SDK supports registration and discovery of services, self-discovery and loading at the Proxy layer.

In some embodiments, the client SDK is compatible with access to multiple registry frameworks simultaneously, wherein the registry frameworks include: and the major registration centers of industries such as zookeeper, eureka and nacos.

In some embodiments, the data persistence layer is comprised of a plurality of small clusters, each of which has data nodes disposed within it.

In some embodiments, the virtual slices are arranged in correspondence with the small clusters.

In some embodiments, the data node is configured to store a service registration instance.

In some embodiments, the management console primarily manages the administration of rights by the registry.

In some embodiments, the management and control functions include black and white lists accessed to a registration center, Proxy online management, data node management, virtual shard maintenance, service routing, weight and the like.

In some embodiments, further comprising: the data synchronizer is used for being compatible with stock application, and can synchronize the service registration instance information of the original stock application into the distributed registry or synchronize the service registration instance of the distributed registry into the original stock registry.

After adopting such design, the invention has at least the following advantages:

through the distributed registry, the access of the service is routed through the Proxy, the Proxy can be expanded infinitely as required, the service is routed to different data nodes through the hash calculation of the service identifier consistency, the distributed storage of the information of the service is realized, and the requirements of large-scale enterprises and mechanisms in millions of instances are met.

Drawings

The foregoing is only an overview of the technical solutions of the present invention, and in order to make the technical solutions of the present invention more clearly understood, the present invention is further described in detail below with reference to the accompanying drawings and the detailed description.

Fig. 1 is an architecture diagram of a distributed registry architecture provided by an embodiment of the present invention.

Detailed Description

The preferred embodiments of the present invention will be described in conjunction with the accompanying drawings, and it will be understood that they are described herein for the purpose of illustration and explanation and not limitation.

Because the service registration examples supported by the registration center in the current market are limited, the method has certain limitation on the micro-service construction of large enterprises and institutions, and the registration and discovery of millions of examples are realized by researching and developing a distributed registration center.

Referring to fig. 1, the distributed registry design is generally divided into five modules: client side SDK, Proxy layer, data persistence layer, management console, and data synchronizer.

The client SDK is mainly responsible for accessing a client system to a distributed registry, supporting registration and discovery of services, self-discovery and load of a Proxy layer, and simultaneously being compatible with the access of a mainstream registry framework in the current market, such as registries of zookeeper, eureka and the like, so that the inventory system can be easily accessed to the distributed registry.

The Proxy layer is mainly responsible for the access of a client, the Proxy layer is designed in a stateless manner and can be expanded infinitely to support the access of tens of millions of services, the Proxy bottom layer logically virtualizes data nodes into N virtual fragments, the virtual fragments are distributed on a Hash ring through a consistent Hash algorithm, the Proxy receives a client request, calculates Hash according to service identification to route to specific data nodes, the registration and discovery of the services are realized, and the service registration information quantity of each data node is reduced.

The data persistence layer is composed of a plurality of small clusters and is routed to different data clusters by Proxy to realize distributed storage.

The management console mainly manages authority control of the registration center, and includes management and control functions of black and white lists accessed to the registration center, Proxy online management, data node management, virtual fragment maintenance, service routing, weight and the like.

The data synchronization application is mainly used for compatible stock application, and can synchronize the service registration instance information of the original stock application into the distributed registry or synchronize the service registration instance of the distributed registry into the original stock registry.

The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the present invention in any way, and it will be apparent to those skilled in the art that the above description of the present invention can be applied to various modifications, equivalent variations or modifications without departing from the spirit and scope of the present invention.

Claims

1. A distributed registry architecture, comprising:

the client SDK is used for accessing the client system to the distributed registration center;

the Proxy agent layer is used for virtually enabling the data nodes to be N virtual slices, calculating a hash value according to the service identifier after receiving a request of the client SDK, and routing to the specific data nodes according to the hash value;

the data persistence layer comprises a plurality of data nodes and is used for performing distributed storage on the microservices and providing registration services according to the received requests;

and the management console is used for managing each component of the distributed registration center.

2. The distributed registry architecture of claim 1 wherein client SDKs support registration and discovery of services, self-discovery and loading at the Proxy agent level.

3. The distributed registry architecture of claim 2 wherein the client SDK is simultaneously compatible with access to multiple registry frameworks, wherein the registry frameworks comprise: and the major registration centers of industries such as zookeeper er, eureka, nacos and the like.

4. The distributed registry architecture of claim 1 wherein the data persistence layer is comprised of a plurality of small clusters, each of which has data nodes disposed therein.

5. The distributed registry architecture of claim 4 wherein the virtual slices are arranged in correspondence with small clusters.

6. The distributed registry architecture of claim 4 wherein the data nodes are configured to store service registry instances.

7. The distributed registry architecture of claim 1 wherein the management console primarily manages registry entitlement management.

8. The distributed registry architecture of claim 7 wherein the management and control functions include black and white lists for access to the registry, Proxy online management, data node management, virtual shard maintenance, service routing, weighting, etc.

9. The distributed registry architecture of claim 1 further comprising:

the data synchronizer is used for being compatible with stock application, and can synchronize the service registration instance information of the original stock application into the distributed registry or synchronize the service registration instance of the distributed registry into the original stock registry.