WO2023125755A1

WO2023125755A1 - Service request processing method and apparatus based on large-scale cluster, and device and medium

Info

Publication number: WO2023125755A1
Application number: PCT/CN2022/143185
Authority: WO
Inventors: 陈鑫远; 左绘; 陈洲; 王广玥
Original assignee: 天翼物联科技有限公司
Priority date: 2021-12-30
Filing date: 2022-12-29
Publication date: 2023-07-06
Also published as: CN114296880A

Abstract

The present application relates to the technical field of cloud computing, and discloses a service request processing method and apparatus based on a large-scale cluster, and a device and a medium. The method comprises: receiving and analyzing a service request of a client to obtain a service request identifier, request end information, and target end information; determining a request path corresponding to the service request; if the service request is determined to be an in-cluster service request, injecting the request end information and the target end information into header information so as to obtain a target application domain and a target service corresponding to the service request in a service registration center, calling the target service in the target application domain, and processing the service request by means of the target service; and if the service request is determined to be a cross-cluster service request, injecting the request end information and the target end information into the header information, injecting the header information into cluster relationship information by means of a service gateway to obtain the target service to process the service request. The present invention reduces the management difficulty of the service under the cluster, and improves the service request processing efficiency.

Description

Service request processing method, device, device and medium based on large-scale cluster

technical field

The present application relates to the technical field of cloud computing, and in particular to a large-scale cluster-based service request processing method, device, equipment and medium.

Background technique

The microservice architecture divides the complex system into several small services, and each service can be independently developed, deployed, and scaled; the microservice architecture and containers (Docker/Kubernetes) are a match made in heaven, which can further simplify the delivery of microservices and enhance the elasticity of the overall system and robustness. However, a distributed application architecture composed of a large number of microservices will also increase the complexity of operation and maintenance, debugging, and security management.

When implementing large-scale system applications, there are a large number of micro-services, and the calling relationship between micro-services is complex. However, as the number of services increases, there are also interactive relationships that grow exponentially through service grid management, bringing service The fine-grained management and complex service governance issues lead to low efficiency in service request processing.

Contents of the invention

The purpose of the embodiments of the present application is to propose a large-scale cluster-based service request processing method, device, device, and medium, so as to improve service request processing efficiency.

In order to solve the above technical problems, the embodiment of the present application provides a large-scale cluster-based service request processing method, including:

Receive a service request from the client, and parse the service request to obtain the service request identifier, requester information, and target information;

Based on the service request identifier, judge a request path corresponding to the service request, and obtain a judgment result, wherein the request path includes an intra-cluster service request and a cross-cluster service request;

If the judgment result is a service request in the cluster, inject the requester information and the target information into the header information, so as to obtain the target application domain and target service corresponding to the service request in the service registration center , and invoking the target service in the target application domain, and processing the service request through the target service;

If the judgment result is the cross-cluster service request, inject the requester information and the target information into the header information, and inject the header information into the cluster relationship information through the service gateway , to obtain the target service, and process the service request through the target service.

In order to solve the above technical problems, an embodiment of the present application provides a large-scale cluster-based service request processing device, including:

The service request receiving module is used to receive the service request of the client, and analyze the service request to obtain the service request identifier, requester information and target information;

A request path judging module, configured to judge a request path corresponding to the service request based on the service request identifier, and obtain a judgment result, wherein the request path includes an intra-cluster service request and a cross-cluster service request;

An intra-cluster request processing module, configured to inject the requester information and the target information into the header information if the judgment result is the intra-cluster service request, so as to obtain the service request in the service registration center Corresponding target application domain and target service, and invoking the target service in the target application domain, and processing the service request through the target service;

A cross-cluster request processing module, configured to inject the requester information and the target information into the header information if the judgment result is the cross-cluster service request, and send the The header information is injected into the cluster relationship information to obtain the target service, and process the service request through the target service.

In order to solve the above-mentioned technical problems, a technical solution adopted by the present invention is to provide a computer device, including one or more processors; and a memory for storing one or more programs, so that the one or more processors realize the above-mentioned Any one of the large-scale cluster-based service request processing methods.

In order to solve the above-mentioned technical problems, a technical solution adopted by the present invention is: a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, any of the above-mentioned items can be realized. The described large-scale cluster-based service request processing method.

Embodiments of the present invention provide a large-scale cluster-based service request processing method, device, equipment, and medium. Wherein, the method includes: receiving a service request from the client, and parsing the service request to obtain the service request identifier, requester information, and target information; based on the service request identifier, judging the request path corresponding to the service request, and obtaining the judgment result, wherein , the request path includes an intra-cluster service request and a cross-cluster service request; if the judgment result is an intra-cluster service request, inject the requester information and target information into the header information to obtain the target application corresponding to the service request in the service registry Domain and target service, and call the target service in the target application domain, and process the service request through the target service; if the judgment result is a cross-cluster service request, inject the requester information and target information into the header information, and pass the The gateway injects the header information into the cluster relationship information to obtain the target service, and processes the service request through the target service. In the embodiment of the present invention, by judging the request path corresponding to the service request, if the request path is an intra-cluster service request, the target service is invoked by injecting header information, and if the request path is a cross-cluster service request, the service gateway is used , to call the target service, which reduces the management difficulty brought about by the fine-grained service in the cluster and the large number of services, and avoids the intrusion of the original service instance, which is conducive to improving the efficiency of service request processing.

Description of drawings

In order to illustrate the solution in this application more clearly, a brief introduction will be given below to the accompanying drawings that need to be used in the description of the embodiments of the application. Obviously, the accompanying drawings in the following description are some embodiments of the application. Ordinary technicians can also obtain other drawings based on these drawings on the premise of not paying creative work.

FIG. 1 is a flow chart of an implementation of a sub-process in a large-scale cluster-based service request processing method provided by an embodiment of the present application.

Fig. 2 is another implementation flowchart of the sub-process in the large-scale cluster-based service request processing method provided by the embodiment of the present application.

Fig. 3 is another implementation flowchart of a sub-process in the large-scale cluster-based service request processing method provided by the embodiment of the present application.

Fig. 4 is another implementation flowchart of a sub-process in the large-scale cluster-based service request processing method provided by the embodiment of the present application.

Fig. 5 is another implementation flowchart of a sub-process in the large-scale cluster-based service request processing method provided by the embodiment of the present application.

Fig. 6 is another implementation flowchart of a sub-process in the large-scale cluster-based service request processing method provided by the embodiment of the present application.

Fig. 7 is another implementation flowchart of the sub-process in the large-scale cluster-based service request processing method provided by the embodiment of the present application.

FIG. 8 is a schematic diagram of a large-scale cluster-based service request processing device provided by an embodiment of the present application.

Fig. 9 is a schematic diagram of a computer device provided by an embodiment of the present application.

Detailed ways

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the technical field of the application; the terms used herein in the description of the application are only to describe specific embodiments The purpose is not to limit the present application; the terms "comprising" and "having" and any variations thereof in the specification and claims of the present application and the description of the above drawings are intended to cover non-exclusive inclusion. The terms "first", "second" and the like in the description and claims of the present application or the above drawings are used to distinguish different objects, rather than to describe a specific order.

Reference herein to an "embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present application. The occurrences of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is understood explicitly and implicitly by those skilled in the art that the embodiments described herein can be combined with other embodiments.

In order to enable those skilled in the art to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

The present invention will be described in detail below in conjunction with the accompanying drawings and embodiments.

It should be noted that the large-scale cluster-based service request processing method provided in the embodiment of the present application is generally executed by a server, and correspondingly, the large-scale cluster-based service request processing device is generally configured in the server.

Please refer to FIG. 1 . FIG. 1 shows a specific implementation manner of a large-scale cluster-based service request processing method.

It should be noted that if there are substantially the same results, the method of the present invention is not limited to the flow sequence shown in Figure 1, and the method includes the following steps:

S1: Receive the service request from the client, and parse the service request to obtain the service request identifier, requester information, and target information.

Specifically, when the client needs to call related services, the client generates a service request and sends the service request to the server. After receiving the service request, the server parses the service request to obtain the service request identifier, the request end information and target information. Wherein, the service request identifier is an identifier corresponding to the target service that needs to be invoked, and is used to determine the service cluster where the service is located. The requester information is information generated based on the client, where the requester information includes the client's IP address information and account information. The target information is information generated based on the requested target service, where the target information includes the target service name and the like.

Referring to Fig. 2, Fig. 2 shows a specific implementation after step S1, which is described in detail as follows:

S1A: Record the initiation time and response time of the client to the service request, and record the receiving time and response return time of the server to the service request.

S1B: Generate log information based on the initiation time, response time, reception time, response return time, and header information.

Specifically, after the above step S1, this embodiment records the client's initiation time and response time to the service request, and the server's reception time and response return time to the service request during the service interaction process, and collects the information from the header Header, such as collecting the following header information: x-request-id, x-b3-traceid, x-b3-spanid, x-b3-parentspanid, x-b3-sampled, x-b3-flags and x -ot-span-context, etc., and then generate log information based on the initiation time, response time, reception time, response return time and header information. Furthermore, the log information is injected and forwarded to the service provider to facilitate service traceability. Wherein, the service provider is a client that generates and provides related services. Wherein, the header information is also the header (header), and the header information is a character string sent by the server before transmitting the HTML data to the browser with the HTTP protocol, and an empty line is required between the header information and the HTML file to separate.

In this embodiment, by recording the client's initiation time and response time to the service request, and recording the server's reception time and response return time to the service request, based on the initiation time, response time, reception time, response return time and header Information, generate log information, which is convenient for analysis and traceability of the service invocation process based on the generated log information.

S2: Based on the service request identifier, determine the request path corresponding to the service request, and obtain a judgment result, wherein the request path includes an intra-cluster service request and a cross-cluster service request.

Specifically, since the interaction process of the service may occur in the same cluster as the client and in a different cluster, it can be judged that the target service to be invoked is in the same cluster as the client through the service request identifier , or in a different cluster from the client. If the judgment result is that the target service to be invoked is in the same cluster as the client, it is an intra-cluster service request; if not, it is a cross-cluster service request.

S3: If the judgment result is a service request in the cluster, inject the requester information and target information into the header information to obtain the target application domain and target service corresponding to the service request in the service registry, and call it in the target application domain target service, and handle service requests through the target service.

Please refer to Fig. 3, Fig. 3 has shown a kind of specific implementation of step S3, described in detail as follows:

S31: If the judgment result is an intra-cluster service request, inject the requester information and target information into the header information to generate a link tracking log identifier.

S32: Based on the link tracking log identifier, traverse the service registration center to obtain the target application domain and target service corresponding to the service request.

S33: Resolving the domain name corresponding to the target application domain to call the target service, and process the service request through the target service.

Specifically, if the judgment result is a service request within the cluster, inject the requester information and target information into the header information to generate a link tracking log identifier. The requester information and target information at this time can be used as a Span message, or Inject the Span message into the header information, generate a link tracking log ID, and then go to the service registration center to track the corresponding target application domain and target service through the link tracking log ID, and then analyze the domain name corresponding to the target application domain to call the target service, and handle service requests through the target service.

Furthermore, using the service grid technology, whenever the service initiates an external call, the client will create a new Span message. The injection of a Span message can realize a complete set of service interaction processes, that is, from the client sending a request to receiving the server's response. Under the multi-level service grid, when cross-cluster service calls are made, the information of the service cluster is injected into the service gateway to display the call information and traceability of the overall cluster. The service grid technology is used to realize the division and independent autonomy of the service cluster under the large granularity, and reduce the management difficulty brought about by the fine granularity of the service and the large number of services under a single cluster.

In this embodiment, if the judgment result is a service request in the cluster, inject the requester information and target information into the header information to generate a link tracking log identifier, and then traverse the service registration center based on the link tracking log identifier to obtain The target application domain and target service corresponding to the service request, and then resolve the domain name corresponding to the target application domain to call the target service, and process the service request through the target service, so that the service request in the cluster can realize the request call of the service, and avoid the native service The intrusion of instances effectively improves the efficiency of service request processing.

Please refer to Fig. 4, Fig. 4 has shown a kind of specific implementation manner of step S33, describe in detail as follows:

S331: Resolve the domain name corresponding to the target application domain through CoreDNS resolution, and obtain the IP address of the target service deployment unit Pod.

S332: Call the target service based on the IP address of the target service deployment unit Pod, and process the service request through the target service.

Specifically, CoreDNS is a domain name discovery project hosted by CNCF, natively integrated with Kubernetes, and its goal is to become a reference solution for cloud-native DNS servers and service discovery; and the CoreDNS resolution method is to configure domain name resolution through CoreDNS, It can analyze the application domain and obtain the IP address of the real service deployment unit Pod. Among them, the service deployment unit Pod refers to the concept proposed by Kubernetes for deploying, managing, and orchestrating containerized applications, and it is also the smallest deployment unit in Kubernetes. In this embodiment of the application, the domain name corresponding to the target application domain is resolved through the CoreDNS resolution method, and the IP address of the target service deployment unit Pod is obtained, and then based on the IP address of the target service deployment unit Pod, the target service is invoked, and processed by the target service Service requests, realize service calls between clusters, and help improve the efficiency of service request processing.

Please refer to FIG. 5, which shows a specific implementation before step S3, which is described in detail as follows:

S3A: Obtain multiple services, compile and package multiple services, generate service mirrors, and place the service mirrors into the service mirror warehouse.

S3B: Obtain the application domain corresponding to the service, and allocate the service to the corresponding cluster based on the application domain.

S3C: In the service registration center, the application domain in the cluster is used as the root node and initialized to obtain the root node corresponding to the application domain.

Specifically, the cluster includes a variety of services, and each service has its corresponding business function. Each business function is regarded as an application domain cluster, and it is registered as each application domain cluster as the root node, so that Get the root node corresponding to the application domain cluster. Therefore, multiple services are obtained first, and then multiple services are compiled and packaged into service mirrors. Among them, mirroring (Mirroring) is a form of file storage and a type of redundancy. The data on one disk is stored on another disk. An identical copy exists on the mirror. Then put it into the service mirror warehouse, obtain the business function of each service, that is, obtain the application domain of the service, plan and configure it into the corresponding cluster; The application domain is used as the root node and is initialized to obtain the root node corresponding to the application domain. In this embodiment, when the service is deployed and released, according to the division of the application domain, the relevant service container is registered with the application domain cluster name as the root node, and the services under this node can automatically discover the service corresponding to the root node, realizing this Cross-service calls under the application domain.

Please refer to FIG. 6. FIG. 6 shows a specific implementation after step S3C, which is described in detail as follows:

S3D: If a service change is detected, a service change notification will be generated in the service registration center.

S3E: Send the service change notification to the client, so that the client obtains the service change content and stores the service change content locally in the client.

Specifically, the service is monitored through the service registration center, and when a service change is detected, the service change content is obtained, and a corresponding service change notification is generated, and the service change notification is sent to the client, and the client receives the service change notification After that, the corresponding service change content is obtained, and then the service change content is stored locally on the client. In this embodiment, if the service transmission change is monitored, a service change notification is generated in the service registration center, and the service change notification is sent to the client, so that the client obtains the service change content and stores the service change content locally in the client , to monitor the service, and update the local service content of the client in real time when the service changes.

S4: If the judgment result is a cross-cluster service request, inject the requester information and target information into the header information, and inject the header information into the cluster relationship information through the service gateway to obtain the target service, and pass the target The service handles service requests.

Referring to Fig. 7, Fig. 7 shows a specific implementation of step S4, which is described in detail as follows:

S41: If the judging result is a cross-cluster service request, inject the requester information and the target information into the header information to obtain the target header information.

S42: Using the service gateway, injecting the target header information into the cluster relationship information to generate cluster information.

S43: In the cluster relationship information, the cluster information is collected and forwarded to obtain the target service, and the service request is processed through the target service.

Specifically, if the judgment result is a cross-cluster service request, the requester information and target information are injected into the header information to obtain the target header information, and then the embodiment of this application reserves a registration interface externally through the service gateway, and the target header The internal information is injected into the cluster relationship information to generate cluster information, for example, the generated cluster messages are x-src-cluster-id and x-dst-cluster-id, and then in the cluster relationship information, the cluster information is collected and forwarded Process to obtain the target service and process the service request through the target service.

Furthermore, when requesting cross-cluster services, it is necessary to fully consider whether the call relationship between services is important and whether it is exposed to the outside world. The embodiment of this application distinguishes and isolates the clusters according to the application domain, and the embodiment of the application also registers through the service gateway and Expose to the outside to achieve service calls outside the cluster, reduce the possibility of excessive expansion of services under the cluster domain, and also reduce the coupling between services. After completing the cross-cluster call service, register such service on the application service gateway through the interface to realize cross-domain interaction between systems. At the same time, distinguishing and isolating clusters according to application domains can effectively reduce the number of services in a single cluster, reduce the complexity of cluster management, and reduce the impact of a certain service on the overall system service due to abnormal shutdown or degradation.

In this embodiment, the service request from the client is received, and the service request is parsed to obtain the service request identifier, requester information, and target information; based on the service request identifier, the request path corresponding to the service request is judged, and the judgment result is obtained, wherein , the request path includes an intra-cluster service request and a cross-cluster service request; if the judgment result is an intra-cluster service request, inject the requester information and target information into the header information to obtain the target application corresponding to the service request in the service registry Domain and target service, and call the target service in the target application domain, and process the service request through the target service; if the judgment result is a cross-cluster service request, inject the requester information and target information into the header information, and pass the The gateway injects the header information into the cluster relationship information to obtain the target service, and processes the service request through the target service. In the embodiment of the present invention, by judging the request path corresponding to the service request, if the request path is an intra-cluster service request, the target service is invoked by injecting header information, and if the request path is a cross-cluster service request, the service gateway is used , to call the target service, which reduces the management difficulty brought about by the fine-grained service in the cluster and the large number of services, and avoids the intrusion of the original service instance, which is conducive to improving the efficiency of service request processing.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be realized by instructing related hardware through a computer program. The computer program can be stored in a computer-readable storage medium. During execution, it may include the processes of the embodiments of the above-mentioned methods. Wherein, the aforementioned storage medium may be a nonvolatile storage medium such as a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM).

Please refer to FIG. 8. As an implementation of the method shown in FIG. 1 above, this application provides an embodiment of a large-scale cluster-based service request processing device, which is similar to the method embodiment shown in FIG. 1 Correspondingly, the device can be specifically applied to various electronic devices.

As shown in FIG. 8 , the large-scale cluster-based service request processing device of this embodiment includes: a service request receiving module 51, a request path judgment module 52, an intra-cluster request processing module 53, and a cross-cluster request processing module 54, wherein:

The service request receiving module 51 is configured to receive the service request from the client, and analyze the service request to obtain the service request identifier, requester information and target information;

The request path judging module 52 is configured to judge the request path corresponding to the service request based on the service request identifier, and obtain a judgment result, wherein the request path includes an intra-cluster service request and a cross-cluster service request;

The intra-cluster request processing module 53 is configured to inject the requester information and target information into the header information if the judgment result is an intra-cluster service request, so as to obtain the target application domain and target service corresponding to the service request in the service registration center, And call the target service in the target application domain, and process the service request through the target service;

The cross-cluster request processing module 54 is used to inject the requester information and the target information into the header information if the judgment result is a cross-cluster service request, and inject the header information into the cluster relationship information through the service gateway, so as to Get the target service, and process the service request through the target service.

Further, the intra-cluster request processing module 53 includes:

A link tracking log identification generation unit, configured to inject requester information and target information into the header information if the judgment result is a service request within the cluster, to generate a link tracking log identification;

The service registration center traversal unit is configured to traverse the service registration center based on the link tracking log identifier, and obtain the target application domain and target service corresponding to the service request;

The domain name resolution unit is configured to resolve the domain name corresponding to the target application domain, so as to call the target service, and process the service request through the target service.

Further, the domain name resolution unit includes:

The IP address generation subunit is used to resolve the domain name corresponding to the target application domain through the CoreDNS resolution method, and obtain the IP address of the target service deployment unit Pod;

The service request processing unit is configured to call the target service based on the IP address of the target service deployment unit Pod, and process the service request through the target service.

Further, before the intra-cluster request processing module 53 also includes:

The service image storage module is used to obtain various services, compile and package the various services, generate a service image, and put the service image into the service image warehouse;

The application domain configuration module is used to obtain the application domain corresponding to the service, and allocate the service to the corresponding cluster based on the application domain;

The root node generating module is configured to use the application domain in the cluster as the root node in the service registration center and perform initialization processing to obtain the root node corresponding to the application domain.

Further, after the root node generation module, it also includes:

The service change notification generation module is used to generate a service change notification in the service registration center if the service is monitored to send a change;

The service change content storage module is configured to send the service change notification to the client, so that the client obtains the service change content and stores the service change content locally in the client.

Further, after the service request receiving module 51, it also includes:

The time recording module is used to record the client's initiation time and response time to the service request, and record the server's reception time and response return time to the service request;

The log information generation module is configured to generate log information based on initiation time, response time, reception time, response return time and header information.

Further, the cross-cluster request processing module 54 includes:

A target header information generation unit, configured to inject requester information and target information into the header information to obtain the target header information if the judgment result is a cross-cluster service request;

The cluster information generation unit is used to inject the target header information into the cluster relationship information by using the service gateway to generate cluster information;

The target service acquisition unit is configured to acquire the target service by collecting and forwarding the cluster information in the cluster relationship information, and process the service request through the target service.

In order to solve the above technical problems, the embodiment of the present application further provides computer equipment. Please refer to FIG. 9 for details. FIG. 9 is a block diagram of the basic structure of the computer device in this embodiment.

The computer device 6 includes a memory 61 , a processor 62 , and a network interface 63 connected to each other through a system bus. It should be noted that the figure only shows a computer device 6 with three components memory 61, processor 62, and network interface 63, but it should be understood that it is not required to implement all the components shown, and alternative implementation more or fewer components. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculation and/or information processing according to preset or stored instructions, and its hardware includes but is not limited to microprocessors, dedicated Integrated circuit (Application Specific Integrated Circuit, ASIC), programmable gate array (Field-Programmable Gate Array, FPGA), digital processor (Digital Signal Processor, DSP), embedded devices, etc.

The computer equipment may be computing equipment such as desktop computers, notebooks, palmtop computers, and cloud servers. Computer equipment can interact with users through keyboards, mice, remote controls, touch pads, or voice-activated devices.

The memory 61 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory ( SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 61 may be an internal storage unit of the computer device 6 , such as a hard disk or internal memory of the computer device 6 . In other embodiments, the memory 61 can also be an external storage device of the computer device 6, such as a plug-in hard disk equipped on the computer device 6, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, flash memory card (Flash Card), etc. Of course, the memory 61 may also include both the internal storage unit of the computer device 6 and its external storage device. In this embodiment, the memory 61 is generally used to store the operating system and various application software installed in the computer device 6, such as program codes of a large-scale cluster-based service request processing method, and the like. In addition, the memory 61 can also be used to temporarily store various types of data that have been output or will be output.

The processor 62 may be a central processing unit (Central Processing Unit, CPU), a controller, a microcontroller, a microprocessor, or other data processing chips in some embodiments. The processor 62 is generally used to control the overall operation of the computer device 6 . In this embodiment, the processor 62 is used to run the program code or process data stored in the memory 61, for example, run the program code of the above-mentioned large-scale cluster-based service request processing method, so as to implement the large-scale cluster-based service request processing method various embodiments.

The network interface 63 may include a wireless network interface or a wired network interface, and the network interface 63 is generally used to establish a communication connection between the computer device 6 and other electronic devices.

The present application also provides another implementation manner, which is to provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and the computer program can be executed by at least one processor, so that at least one processor performs the above-mentioned The steps of a large-scale cluster-based service request processing method.

Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or the part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to make a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the method of each embodiment of the present application.

The block chain referred to in the present invention is a new application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. Blockchain (Blockchain), essentially a decentralized database, is a series of data blocks associated with each other using cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify its Validity of information (anti-counterfeiting) and generation of the next block. The blockchain can include the underlying platform of the blockchain, the platform product service layer, and the application service layer.

Apparently, the embodiments described above are only some of the embodiments of the present application, but not all of them. The drawings show preferred embodiments of the present application, but do not limit the patent scope of the present application. The present application can be implemented in many different forms, on the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure content of the present application more thorough and comprehensive. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing specific embodiments, or perform equivalent replacements for some of the technical features . All equivalent structures made using the contents of the description and drawings of this application, directly or indirectly used in other related technical fields, are also within the scope of protection of this application.

Claims

A large-scale cluster-based service request processing method, characterized in that it includes:

Receive a service request from the client, and parse the service request to obtain the service request identifier, requester information, and target information;

Based on the service request identifier, judge a request path corresponding to the service request, and obtain a judgment result, wherein the request path includes an intra-cluster service request and a cross-cluster service request;

If the judgment result is a service request in the cluster, inject the requester information and the target information into the header information, so as to obtain the target application domain and target service corresponding to the service request in the service registration center , and invoking the target service in the target application domain, and processing the service request through the target service;

If the judgment result is the cross-cluster service request, inject the requester information and the target information into the header information, and inject the header information into the cluster relationship information through the service gateway , to obtain the target service, and process the service request through the target service.
The large-scale cluster-based service request processing method according to claim 1, wherein if the judgment result is a service request within the cluster, injecting the requester information and the target information into In the header information, the target application domain and target service corresponding to the service request are obtained from the service registry, and the target service is invoked in the target application domain, and the service request is processed through the target service, include:

If the judgment result is a service request in the cluster, inject the requester information and the target information into the header information to generate a link tracking log identifier;

Based on the link tracking log identifier, traverse the service registration center to obtain the target application domain and target service corresponding to the service request;

Resolving the domain name corresponding to the target application domain to call the target service, and process the service request through the target service.
The large-scale cluster-based service request processing method according to claim 2, wherein the domain name corresponding to the target application domain is resolved to call the target service, and the service is processed through the target service requests, including:

Analyzing the domain name corresponding to the target application domain through the CoreDNS resolution method to obtain the IP address of the target service deployment unit Pod;

Based on the IP address of the target service deployment unit Pod, the target service is invoked, and the service request is processed through the target service.
The large-scale cluster-based service request processing method according to claim 1, wherein the judgment result is a service request within the cluster, and injecting the requester information and the target information into the header information In order to acquire the target application domain and target service corresponding to the service request in the service registry, and invoke the target service in the target application domain, and process the service request through the target service, the Methods also include:

Obtaining various services, compiling and packaging the various services, generating a service image, and placing the service image into a service image warehouse;

Obtain the application domain corresponding to the service, and allocate the service to the corresponding cluster based on the application domain;

In the service registration center, the application domain in the cluster is used as the root node and initialized to obtain the root node corresponding to the application domain.
The large-scale cluster-based service request processing method according to claim 4, wherein, in the service registration center, the application domain in the cluster is used as the root node and initialized to obtain the application domain After the corresponding root node, the method also includes:

If it is monitored that the service sends a change, a service change notification is generated in the service registration center;

The service change notification is sent to the client, so that the client obtains the service change content and stores the service change content locally in the client.
The large-scale cluster-based service request processing method according to claim 1, wherein the service request from the client is received, and the service request is parsed to obtain the service request identifier, requester information, and target After the information, the method also includes:

Recording the initiation time and response time of the client to the service request, and recording the receiving time and response return time of the server to the service request;

Log information is generated based on the initiation time, the response time, the reception time, the response return time and the header information.
The large-scale cluster-based service request processing method according to any one of claims 1 to 6, wherein if the judgment result is the cross-cluster service request, the requester information and the Inject the target information into the header information, and inject the header information into the cluster relationship information through the service gateway to obtain the target service, and process the service request through the target service, including :

If the judgment result is the cross-cluster service request, injecting the requester information and the target information into the header information to obtain target header information;

Using the service gateway, injecting the target header information into the cluster relationship information to generate cluster information;

In the cluster relationship information, the cluster information is collected and forwarded to obtain the target service, and the service request is processed through the target service.
A large-scale cluster-based service request processing device, characterized in that it includes:

A service request receiving module, configured to receive a service request from a client, and analyze the service request to obtain a service request identifier, requester information, and target information;

A request path judging module, configured to judge a request path corresponding to the service request based on the service request identifier, and obtain a judgment result, wherein the request path includes an intra-cluster service request and a cross-cluster service request;

An intra-cluster request processing module, configured to inject the requester information and the target information into the header information if the judgment result is the intra-cluster service request, so as to obtain the service request in the service registration center Corresponding target application domain and target service, and invoking the target service in the target application domain, and processing the service request through the target service;

A cross-cluster request processing module, configured to inject the requester information and the target information into the header information if the judgment result is the cross-cluster service request, and send the The header information is injected into the cluster relationship information to obtain the target service, and process the service request through the target service.
A computer device, characterized by comprising a memory and a processor, the memory stores a computer program, and when the processor executes the computer program, the large-scale Service request processing method for scale clusters.
A computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the large-scale Service request processing method for scale clusters.