CN115102854B - Remote procedure call route management control method, system and equipment for micro-service - Google Patents

Remote procedure call route management control method, system and equipment for micro-service Download PDF

Info

Publication number
CN115102854B
CN115102854B CN202210860309.2A CN202210860309A CN115102854B CN 115102854 B CN115102854 B CN 115102854B CN 202210860309 A CN202210860309 A CN 202210860309A CN 115102854 B CN115102854 B CN 115102854B
Authority
CN
China
Prior art keywords
information
management
routing
route
pushing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202210860309.2A
Other languages
Chinese (zh)
Other versions
CN115102854A (en
Inventor
李斌
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kangjian Information Technology Shenzhen Co Ltd
Original Assignee
Kangjian Information Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Kangjian Information Technology Shenzhen Co Ltd filed Critical Kangjian Information Technology Shenzhen Co Ltd
Priority to CN202210860309.2A priority Critical patent/CN115102854B/en
Publication of CN115102854A publication Critical patent/CN115102854A/en
Application granted granted Critical
Publication of CN115102854B publication Critical patent/CN115102854B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The application provides a remote procedure call route management control method, a remote procedure call route management control system, computer equipment and a computer readable storage medium for micro services, and relates to the technical field of computers. The architecture of the micro service in the method can comprise a routing decision management and control center, a routing information pushing center and a management background, wherein the routing decision management and control center manages routing rules and matching strategies, the routing information pushing center is responsible for real-time pushing of routing information, and the management background provides unified interface management operation capability. The embodiment of the application can provide the management capability of dynamic intervention during micro service operation through the linkage among the management background, the routing decision management and control center and the routing information pushing center, realize the real-time management and control of routing rules and matching strategies, and can accurately adjust the remote procedure call flow direction of the micro service.

Description

Remote procedure call route management control method, system and equipment for micro-service
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, a system, a computer device, and a computer readable storage medium for controlling remote procedure call routing of a micro service.
Background
Micro-services are a cloud native architecture approach in which a single application consists of many loosely coupled and independently deployable smaller components or services, with remote invocation between services being accomplished through remote procedure call (RPC, remote Produce Call) protocols, which can make invocation between services as convenient as local invocation, making the caller unaware of the logic of the remote invocation. Each service has a plurality of service instances to form a service cluster, so that a service consumer needs to select one service instance from a target service cluster before initiating a remote procedure call request, which is a process of service routing and load balancing. However, there is a unified and complete scheme for dynamically controlling the remote procedure call route of the micro service, and the remote procedure call flow direction of the micro service cannot be controlled and regulated in real time, so that the technical problem needs to be solved.
Disclosure of Invention
The application provides a remote procedure call route management control method, a remote procedure call route management control system, a remote procedure call route management control computer device and a remote procedure call route management control computer device for micro services, which are used for solving the technical problem that the flow direction of the remote procedure call of the micro services cannot be controlled and adjusted in real time at present.
In a first aspect, a method for controlling route management of remote procedure call of a micro service is provided, where the architecture of the micro service includes a route decision management and control center, a route information pushing center and a management background, the route decision management and control center manages route rules and matching policies, the route information pushing center is responsible for real-time pushing of route information, and the management background provides unified interface management operation capability, and the method includes:
when the management background receives a management operation, if the management operation is a route management operation, the management background sends route management information corresponding to the route management operation to the route decision management and control center;
The routing decision control center analyzes the routing management information, determines that the routing rules and the matching strategies change, generates push information containing the change contents of the routing rules and the matching strategies, and provides the push information for the routing information push center to push;
And the routing information pushing center pushes the pushing information to a corresponding target service consumer node, and the target service consumer node updates a local routing rule and a matching strategy according to the pushing information.
In a second aspect, a remote procedure call routing management control system for a micro service is provided, including:
the route decision management and control center is used for managing route rules and matching strategies;
The route information pushing center is used for pushing route information in real time;
The management background is used for providing unified interface management operation capability;
when the management background receives a management operation, if the management operation is a route management operation, the management background sends route management information corresponding to the route management operation to the route decision management and control center;
The routing decision control center analyzes the routing management information, determines that the routing rules and the matching strategies change, generates push information containing the change contents of the routing rules and the matching strategies, and provides the push information for the routing information push center to push;
And the routing information pushing center pushes the pushing information to a corresponding target service consumer node, and the target service consumer node updates a local routing rule and a matching strategy according to the pushing information.
In a third aspect, a computer device is provided, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the remote procedure call routing management control method of the micro-service described above when the computer program is executed.
In a fourth aspect, there is provided a computer readable storage medium storing a computer program which, when executed by a processor, implements the steps of the remote procedure call routing management control method of a micro service described above.
In the solution implemented by the method, the system, the computer equipment and the computer readable storage medium for remote procedure call route management control of the micro service, the architecture of the micro service can comprise a route decision management and control center, a route information pushing center and a management background, wherein the route decision management and control center manages route rules and matching strategies, the route information pushing center is responsible for real-time pushing of route information, and the management background provides unified interface management operation capability; when the management background receives the management operation, if the management operation is a route management operation, the management background sends route management information corresponding to the route management operation to a route decision management and control center; the route decision management and control center analyzes the route management information, determines that the route rules and the matching strategies change, generates push information containing the change contents of the route rules and the matching strategies, and provides the push information for the route information push center to push; the route information pushing center pushes the pushing information to the corresponding target service consumer node, and the target service consumer node updates the local route rules and the matching strategies according to the pushing information. It can be seen that the embodiment of the application can provide the management capability of dynamic intervention in micro service operation through the linkage among the management background, the routing decision management and control center and the routing information pushing center, realize the real-time management and control of the routing rules and the matching strategies, and accurately adjust the remote procedure call flow direction of the micro service.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments of the present application will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of an application environment of a remote procedure call routing management control method for a micro-service according to an embodiment of the present application;
FIG. 2 is a schematic diagram of an application environment of a remote procedure call routing management control method for a micro-service in accordance with another embodiment of the present application;
FIG. 3 is a flow chart of a method for remote procedure call routing management control for a micro service according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a push feedback process according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a logical processing node recorded during a routing process according to an embodiment of the present application;
FIG. 6 is a schematic diagram of a remote procedure call routing management control system for a micro service according to an embodiment of the present application;
FIG. 7 is a schematic diagram of a remote procedure call routing management control system for a micro service according to another embodiment of the present application;
fig. 8 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
Exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the application to those skilled in the art.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that such use is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "include" and variations thereof are to be interpreted as open-ended terms that mean "include, but are not limited to.
The architecture of a micro service typically includes a registry, service provider nodes, and service consumer nodes, the service provider nodes being registered with the registry, the service consumer nodes obtaining micro service information for the service provider nodes from the registry. Each service of the service provider node has a plurality of service instances to form a service cluster, so when the service consumer node initiates a remote procedure call request, one service instance needs to be selected from the target service cluster, which is the process of service routing and load balancing.
The remote procedure call route management control method of the micro service provided by the embodiment of the application can comprise a route decision management and control center, a route information pushing center and a management background besides a registration center, a service provider node and a service consumer node of a micro service architecture, wherein the route decision management and control center manages route rules and matching strategies, the route information pushing center is responsible for real-time pushing of route information, and the management background provides unified interface management operation capability as shown in fig. 1.
In micro-services, all that initiates remote procedure calls are service consumer nodes, and remote procedure call routing load balancing is also performed at the service consumer nodes, so in the embodiment of the present application, contact is mainly established with the service consumer nodes as well. When a service consumer node in the micro service is started, information of an application instance of the service consumer node is reported to a routing decision management and control center, and the routing decision management and control center manages the information of the application instance. The information of the application instance herein may include information such as IP (Internet Protocol, protocol of interconnection between networks), port, micro-service framework, instance tag, etc., which is not limited by the embodiment of the present application.
In order to solve the problems of risk of upgrading of the micro-service system and lack of effective intervention means for on-line fault site retention and investigation, the embodiment of the application can also comprise a remote procedure call request link observation center in addition to each role shown in fig. 1 under the micro-service architecture, as shown in fig. 2, wherein the remote procedure call request link observation center is responsible for observation of remote procedure call request link systems and reports.
The architecture of the micro-service may include, from a network level, an access layer, a gateway layer, a service layer, and a storage layer, where service consumer nodes are located, and where a registry, a service provider node, a routing decision management and control center, a routing information push center, a management background, and a remote procedure call request link observation center may be located, specifically:
The access layer may be a browser of a personal computer, a mobile device or other terminal, and invoking the microservice by the access layer requires carrying token information for the gateway layer to verify whether the request is legal.
All requests of the access layer pass through the gateway layer, the gateway layer is responsible for receiving the requests of the access layer, the gateway layer firstly performs authentication authorization verification on the requests of the access layer, judges whether the requests are legal requests according to token information of the requests, and directly returns error codes if the requests are not legal requests; if the request is legal, the gateway layer routes the request to a specific service instance, that is, each service of the service provider node has a plurality of service instances to form a service cluster, and the service consumer node needs to select one service instance from the target service cluster when initiating the remote procedure call request.
The gateway layer can maintain a timing task, send a request to a registration center of the service layer at regular intervals (for example, 30 seconds) to acquire micro service information, cache the IP and port numbers of all micro services to the local of the gateway layer, send the request to one of the service instances according to a load balancing algorithm, and can use a polling load balancing algorithm to call the target service instance in sequence to distribute the request of the access layer to different servers of the service layer for execution. When a certain micro-service fails to call and times out frequently, the gateway layer actively fuses the failed micro-service so as to prevent a large number of threads from being occupied for a long time due to the calling of the failed micro-service, and after the failed micro-service is restored and stabilized, the gateway layer restores the calling.
The storage layer may be used for data storage of a registration center of the service layer, a service provider node, a routing decision management center, a routing information push center, a management background, a remote procedure call request link observation center, and the like.
The service layer may be implemented by a stand-alone server or a server cluster composed of a plurality of servers. The present application will be described in detail with reference to specific examples.
Referring to fig. 3, fig. 3 is a flow chart of a remote procedure call route management control method of a micro service according to an embodiment of the present application, in fig. 3, a micro service architecture may include a route decision management and control center, a route information push center and a management background, where the route decision management and control center manages a route rule and a matching policy, the route information push center is responsible for real-time push of route information, and the management background provides a unified interface management operation capability, and may specifically include steps S301 to S303 as follows:
Step S301, when the management background receives the management operation, if the management operation is a route management operation, the management background sends route management information corresponding to the route management operation to the route decision management and control center.
In the step, an operator can input management operation through a unified interface of a management background, and after the management background receives the management operation, if the management operation is route management operation, the management background sends route management information corresponding to the route management operation to a route decision management and control center. The route management operations herein may be operations on rules and matching policies of the route.
For example, in a micro-service architecture, service consumer node A, B, C, service provider node D, D including version 1, version 2, and version 3, each version including multiple service instances, assuming that the initial routing rules and matching policies are that service consumer node A invokes version 1 of service provider node D, service consumer node B invokes version 2 of service provider node D, and service consumer node C invokes version 3 of service provider node D. The operator modifies the routing rules and the matching policies through the management background, i.e. the service consumer node a invokes version 2 of the service provider node D and the service consumer node B invokes version 3 of the service provider node D. It should be noted that the examples are illustrative only and are not intended to limit the embodiments of the present application.
Step S302, the routing decision control center analyzes the routing management information, determines that the routing rules and the matching strategies change, generates push information containing the changing contents of the routing rules and the matching strategies, and provides the push information for the routing information push center to push.
In this step, the step of providing the push information to the routing information push center for push may be that the push information is sent to the routing information push center for push, and still taking the above example as an example, the routing decision management and control center analyzes the routing management information, determines that the routing rule and the matching policy change, generates push information containing the content of the routing rule and the matching policy change, that is, generates push information of version 2 of the service consumer node a for calling the service provider node D, sends the push information to the routing information push center, and the routing information push center pushes the push information to the service consumer node a; push information is also generated that the service consumer node B invokes version 3 of the service provider node D and sends the push information to the routing information push center, which pushes the push information to the service consumer node B.
In step S303, the routing information pushing center pushes the pushing information to the corresponding target service consumer node, and the target service consumer node updates the local routing rule and the matching policy according to the pushing information.
In the step, a routing information pushing center pushes push information of version 2 of a service provider node D to a service consumer node A, and the service consumer node A updates a local routing rule and a matching strategy according to the push information; the routing information pushing center pushes the pushing information of the version 3 of the service provider node D to the service consumer node B, and the service consumer node B updates the local routing rules and the matching strategy according to the pushing information.
The embodiment of the application can provide the management capability of dynamic intervention during micro service operation through the linkage among the management background, the routing decision management and control center and the routing information pushing center, realize the real-time management and control of routing rules and matching strategies, and can accurately adjust the remote procedure call flow direction of the micro service.
The embodiment of the application provides a possible implementation mode, when the service consumer node in the micro service is started, the information of the application instance of the service consumer node is reported to the routing decision control center, and the routing decision control center manages the information of the application instance. The information of the application instance may include information of an IP address, a port, a micro service framework, an instance tag, and the like, which is not limited by the embodiment of the present application. Therefore, through the management of the application instance of the service consumer node, the real-time management and control of the routing rule and the matching strategy can be realized, and the remote procedure call flow direction of the micro service can be accurately regulated.
In the embodiment of the application, a possible implementation manner is provided, if the push information contains an application set and a notification set, the application set represents a first service list bound by a routing rule and a matching policy, and the first service list contains service provider nodes in micro services; the notification set indicates a second service list to use the routing rules and the matching policies, where the second service list includes service consumer nodes in the micro service, and then the routing information pushing center pushes the push information to the corresponding target service consumer node in step S303, and the target service consumer node updates the local routing rules and the matching policies according to the push information, which specifically may include the following steps A1 to A3:
Step A1, a routing information pushing center acquires information of all application examples corresponding to service consumer nodes of a notification set according to pushing information, records a pushing log, pushes the pushing information to one or more corresponding target service consumer nodes, and updates a pushing state after pushing is completed;
step A2, one or more target service consumer nodes receive the push information, update local routing rules and matching strategies according to the push information, and feed back an update result to a routing information push center;
And step A3, the route information pushing center receives feedback information containing an updating result, records the feedback information and updates the statistical data of the feedback information of the pushing record.
Thus, the whole pushing feedback process is finally completed through the steps A1, A2 and A3, and the log and information recorded in the whole process intuitively reflect the states of all links and are used for abnormal investigation.
Fig. 4 is a schematic diagram of a push feedback flow provided in an embodiment of the present application, where a routing decision control center analyzes routing management information, determines that a routing rule and a matching policy change, analyzes a change behavior, generates push information containing a change content of the routing rule and the matching policy, and provides the push information to a routing information push center for push.
The routing information pushing center acquires information of all application instances corresponding to the service consumer nodes of the notification set according to the pushing information, records a pushing log, pushes the pushing information to one or more corresponding target service consumer nodes, and updates the pushing state after pushing is completed.
One or more target service consumer nodes receive the push information, update local routing rules and matching strategies according to the push information, and feed back an update result to the routing information push center.
And the routing information pushing center receives feedback information containing an updating result, records the feedback information and updates the statistical data of the feedback information of the pushing record.
According to the steps A1, A2 and A3 and the flow of fig. 4, the embodiment of the application constructs an information synchronization feedback model, wherein the information synchronization feedback model comprises a management and control party, a pushing party and a consumer, and the consumer comprises a receiver, a broadcaster, a monitor and a feedback party; the management and control party is used for realizing the function of a route decision management and control center, and the pushing party is used for realizing the function of a route information pushing center;
When receiving route management information corresponding to route management operation sent by a management background, a management control part analyzes the route management information, determines that a route rule and a matching strategy change, generates push information containing the change contents of the route rule and the matching strategy, and provides the push information for a push party to push;
The pushing party pushes the pushing information to the corresponding target consumer, and the target consumer updates the local routing rule and the matching strategy according to the pushing information;
the receiver in the target consumer receives the push information, submits the push information to the broadcaster, the broadcaster broadcasts the push information, the corresponding monitor processes the push information, and the feedback person feeds back the result to the push party after the processing is finished.
In the embodiment of the application, the received message is broadcasted in the information synchronization feedback model, and the interested listener performs corresponding processing, such as updating local routing strategy information, and the result is fed back to the push after the processing is finished. The model has the advantages that the processes of receiving, synchronizing and feeding back are subjected to carding and abstraction, different roles are designed, respective logic is processed, and more functions are expanded by realizing different listeners.
In order to solve the problems of risk of upgrade of a micro-service system and lack of effective intervention means for on-line fault site retention and investigation, the embodiment of the application can also comprise a remote procedure call request link observation center under the micro-service architecture, wherein the remote procedure call request link observation center is responsible for observation of remote procedure call request link graphs and reports. Therefore, the abnormal problems can be timely checked through observing the recorded logs.
In the routing process, if the remote procedure call request includes a routing tag, the remote procedure call request is a dyeing request, and a request link record of the dyeing request can be performed, which specifically includes the following steps B1 and B2:
Step B1, receiving a route label, judging whether the route label exists, if so, screening service instances, acquiring a target service instance through load balancing, and calling the target service instance through a remote process; if the route label does not exist, matching the route strategy, judging whether the route label exists, if the route label does not exist, ending, if the route label does exist, screening the service instance, acquiring a target service instance through load balancing, and calling the target service instance through a remote process;
And step B2, the remote procedure call request link observation center records and receives the route label, matches the route strategy, performs service instance screening, obtains a target service instance through load balancing and invokes a logic processing node of the target service instance through the remote procedure, and is used for observing the route flow direction of the dyeing request and the service condition of the route strategy.
Fig. 5 is a schematic diagram of a logic processing node recorded in a routing process according to an embodiment of the present application, where the logic processing node is used to receive a routing label, match a routing policy, perform service instance screening, obtain a target service instance through load balancing, and call the target service instance through a remote process, and is a logic processing node to be recorded, and the routing flow direction of a dyeing request and the service condition of the routing policy can be observed.
The embodiment of the application provides a possible implementation mode, wherein a remote procedure call request link observation center is combined with a distributed tracking system to construct a tracking model, and the tracking model defines a registrar role and a reporter role of a dyeing request route record track and an adapter role of a distributed tracking middleware;
And tracking each logic processing node through the adapter role of the distributed tracking middleware, recording each logic processing node through the registrar role, and reporting each logic processing node to a remote procedure call request link observation center through the reporter role.
The embodiment model of the application defines the role of a registrar and a reporter of the dyeing request route record track and the role of an adapter of the distributed tracking middleware, thereby reducing the cost of repeated development and realizing the observation function of the dyeing request link by the capability of the distributed tracking system. The model focuses on the recording and reporting logic of the track, and can be compatible with different distributed tracking systems, so that the model is flexible and universal.
The embodiment of the application provides a unified cloud primary micro-service remote procedure call routing strategy management and control scheme, which can dynamically adjust remote procedure call request routing rules in real time when a system is running, and can be used for gray level release and other scenes in system upgrading release so as to reduce release cost and release risk; when faults occur on the line, the flow on the line can be controlled in real time, the fault site is reserved, and the fault checking efficiency is improved.
Meanwhile, the embodiment of the application also provides an instance information management, a pushing flow of a routing strategy and an information synchronization feedback model, which can observe whether the strategy is pushed successfully in real time and inform the nodes of detailed states such as whether the strategy is received successfully.
The dyeing route track recording model in the embodiment of the application can be integrated with an open-source cloth tracking system at low cost on the dyeing flow rate to provide a real-time observable dyeing request route track.
It should be noted that, the sequence number of each step in the above embodiment does not mean the sequence of execution sequence, and the execution sequence of each process should be determined by its function and internal logic, and should not limit the implementation process of the embodiment of the present application in any way. In practical applications, all the possible embodiments may be combined in any combination manner to form possible embodiments of the present application, which are not described in detail herein.
Based on the remote procedure call route management control method of the micro service provided by each embodiment, the embodiment of the application also provides a remote procedure call route management control system of the micro service based on the same inventive concept.
Fig. 6 is a schematic structural diagram of a remote procedure call routing control system for a micro service according to an embodiment of the present application. As shown in fig. 6, the remote procedure call route management control system of the micro service may include a route decision management center 610, a route information push center 620, and a management background 630.
A routing decision management and control center 610 for managing routing rules and matching policies;
the routing information pushing center 620 is configured to be responsible for real-time pushing of routing information;
management background 630, configured to provide unified interfacing management operation capability;
When the management background 630 receives the management operation, if the management operation is a route management operation, the management background 630 sends route management information corresponding to the route management operation to the route decision management and control center 610;
the routing decision management and control center 610 analyzes the routing management information, determines that the routing rules and the matching strategies change, generates push information containing the changing contents of the routing rules and the matching strategies, and provides the push information to the routing information push center 620 for pushing;
The routing information pushing center 620 pushes the pushed information to the corresponding target service consumer node, and the target service consumer node updates the local routing rule and the matching policy according to the pushed information.
In one possible implementation manner provided in the embodiment of the present application, the micro-service architecture further includes a service consumer node, where when the service consumer node in the micro-service is started, information of an application instance of the service consumer node itself is reported to the routing decision management and control center 610, and the routing decision management and control center 610 manages the information of the application instance.
The embodiment of the application provides a possible implementation mode, wherein the push information comprises an application set and a notification set, the application set represents a first service list bound by a routing rule and a matching strategy, and the first service list comprises service provider nodes in micro services; the notification set represents a second list of services to use routing rules and matching policies, the second list of services comprising service consumer nodes in the micro-service;
The routing information pushing center 620 acquires information of all application instances corresponding to the service consumer nodes of the notification set according to the pushing information, records a pushing log, pushes the pushing information to the corresponding one or more target service consumer nodes, and updates a pushing state after pushing is completed;
One or more target service consumer nodes receive the push information, update local routing rules and matching strategies according to the push information, and feed back the update result to the routing information push center 620;
The routing information push center 620 receives feedback information including the updated result, records the feedback information, and updates statistics of the feedback information push records.
The embodiment of the application provides a possible implementation mode, and an information synchronous feedback model is constructed, wherein the information synchronous feedback model comprises a management and control party, a pushing party and a consumer, and the consumer comprises a receiver, a broadcaster, a monitor and a feedback party; the management and control party is used for realizing the function of a route decision management and control center, and the pushing party is used for realizing the function of a route information pushing center;
When receiving route management information corresponding to route management operation sent by a management background, a management control part analyzes the route management information, determines that a route rule and a matching strategy change, generates push information containing the change contents of the route rule and the matching strategy, and provides the push information for a push party to push;
The pushing party pushes the pushing information to the corresponding target consumer, and the target consumer updates the local routing rule and the matching strategy according to the pushing information;
the receiver in the target consumer receives the push information, submits the push information to the broadcaster, the broadcaster broadcasts the push information, the corresponding monitor processes the push information, and the feedback person feeds back the result to the push party after the processing is finished.
In one possible implementation manner provided in the embodiment of the present application, as shown in fig. 7, the system illustrated in fig. 6 above may further include a remote procedure call request link observation center 710, where the remote procedure call request link observation center 710 is responsible for the observation of remote procedure call request link graphs and reports.
In the routing process, if the remote procedure call request contains a routing label, the remote procedure call request link observation center 710 receives the routing label, judges whether the routing label exists, performs service instance screening if the routing label exists, acquires a target service instance through load balancing, and invokes the target service instance through the remote procedure; if the route label does not exist, matching the route strategy, judging whether the route label exists, if the route label does not exist, ending, if the route label does exist, screening the service instance, acquiring a target service instance through load balancing, and calling the target service instance through a remote process;
the remote procedure call request link observation center 710 records the receiving route label, matches the route policy, performs service instance screening, obtains the target service instance through load balancing, and invokes the logic processing node of the target service instance through the remote procedure, and is used for observing the route flow direction of the dyeing request and the service condition of the route policy.
In the embodiment of the application, a possible implementation manner is provided, and the remote procedure call request link observation center 710 is combined with a distributed tracking system to construct a tracking model, wherein the tracking model defines a registrar role and a reporter role of a dyeing request route record track and an adapter role of a distributed tracking middleware;
And tracking each logic processing node through the adapter role of the distributed tracking middleware, recording each logic processing node through the registrar role, and reporting each logic processing node to a remote procedure call request link observation center through the reporter role.
Based on the same inventive concept, the embodiment of the application also provides a computer device, which comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor realizes the steps of the remote procedure call route management control method of the micro-service when executing the computer program.
In an exemplary embodiment, a computer device is provided, which may be a server, and an internal structure thereof may be as shown in fig. 8. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes non-volatile and/or volatile storage media and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the computer device is for communicating with an external client via a network connection. The computer program, when executed by a processor, performs the functions or steps of a micro-service remote procedure call routing management control method.
Based on the same inventive concept, the embodiments of the present application further provide a computer readable storage medium having a computer program stored therein, wherein the computer program is configured to execute the remote procedure call routing control method of the micro service of any one of the embodiments described above when running.
It should be noted that, the functions or steps implemented by the computer device or the computer readable storage medium may correspond to the relevant descriptions of the server side and the client side in the foregoing method embodiments, and are not described herein for avoiding repetition.
It will be clear to those skilled in the art that the specific working processes of the above-described systems, devices and modules may refer to the corresponding processes in the foregoing method embodiments, and are not described herein for brevity.
Those of ordinary skill in the art will appreciate that: the aspects of the present application may be embodied in essence or in whole or in part in a software product stored on a storage medium, comprising program instructions for causing an electronic device (e.g., personal computer, server, network device, etc.) to perform all or part of the steps of the methods of the embodiments of the present application when the program instructions are executed. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM), a magnetic disk, or an optical disk, etc.
Or all or part of the steps of implementing the foregoing method embodiments may be implemented by hardware (such as a personal computer, a server, or an electronic device such as a network device) associated with program instructions, where the program instructions may be stored on a computer-readable storage medium, and where the program instructions, when executed by a processor of the electronic device, perform all or part of the steps of the method embodiments of the present application.
The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all technical features thereof can be replaced by others within the spirit and principle of the present application; such modifications and substitutions do not depart from the scope of the application.

Claims (8)

1. The remote procedure call route management control method of the micro service is characterized in that the architecture of the micro service comprises a route decision management and control center, a route information pushing center and a management background, wherein the route decision management and control center manages route rules and matching strategies, the route information pushing center is responsible for real-time pushing of route information, and the management background provides unified interface management operation capability, and the method comprises the following steps:
when the management background receives a management operation, if the management operation is a route management operation, the management background sends route management information corresponding to the route management operation to the route decision management and control center;
The routing decision control center analyzes the routing management information, determines that the routing rules and the matching strategies change, generates push information containing the changing contents of the routing rules and the matching strategies, and provides the push information for the routing information push center;
The routing information pushing center pushes the pushing information to a corresponding target service consumer node, and the target service consumer node updates a local routing rule and a matching strategy according to the pushing information;
The architecture of the micro-service further comprises a service consumer node, the method further comprising:
When the service consumer node is started, reporting information of an application instance of the service consumer node to the routing decision management and control center, and managing the information of the application instance by the routing decision management and control center;
the push information comprises an application set and a notification set, wherein the application set represents a first service list bound by a routing rule and a matching strategy, and the first service list comprises service provider nodes in micro services; the notification set representing a second service list to use routing rules and matching policies, the second service list containing service consumer nodes in the micro-service;
The routing information pushing center pushes the pushing information to a corresponding target service consumer node, and the target service consumer node updates a local routing rule and a matching policy according to the pushing information, including:
The routing information pushing center acquires information of all application instances corresponding to the service consumer nodes of the notification set according to the pushing information, records a pushing log, pushes the pushing information to one or more corresponding target service consumer nodes, and updates a pushing state after pushing is completed;
the one or more target service consumer nodes receive the push information, update local routing rules and matching strategies according to the push information, and feed back update results to the routing information push center;
and the routing information pushing center receives feedback information containing the updating result, records the feedback information and updates the statistical data of the feedback information of the pushing record.
2. The method as recited in claim 1, further comprising:
constructing an information synchronous feedback model, wherein the information synchronous feedback model comprises a management and control party, a pushing party and a consumer, and the consumer comprises a receiver, a broadcaster, a monitor and a feedback party; the management and control party is used for realizing the function of the route decision management and control center, and the pushing party is used for realizing the function of the route information pushing center;
When receiving the route management information corresponding to the route management operation sent by the management background, the management control analyzes the route management information, determines that the route rule and the matching strategy change, generates push information containing the change content of the route rule and the matching strategy, and provides the push information for the push party to push;
The pushing party pushes the pushing information to a corresponding target consumer, and the target consumer updates a local routing rule and a matching strategy according to the pushing information;
The receiver in the target consumer receives the push information, submits the push information to the broadcaster, the broadcaster broadcasts the push information, the corresponding monitor processes the push information, and the feedback person feeds back the result to the push party after the processing is finished.
3. The method of any of claims 1 to 2, wherein the architecture of the micro-service further comprises a remote procedure call request link observation center responsible for the observation of remote procedure call request link schematics and reports.
4. The method of claim 3, wherein the remote procedure call request is a dye request if the remote procedure call request includes a routing tag during the routing by a service consumer node in the micro service, the method further comprising:
Receiving a route label, judging whether the route label exists or not, if so, screening service instances, acquiring a target service instance through load balancing, and calling the target service instance through a remote process; if the route label does not exist, matching the route strategy, judging whether the route label exists, if the route label does not exist, ending, if the route label does exist, screening the service instance, acquiring a target service instance through load balancing, and calling the target service instance through a remote process;
The remote procedure call request link observation center records and receives a route label, matches a route strategy, performs service instance screening, obtains a target service instance through load balancing, and invokes a logic processing node of the target service instance through a remote procedure, and is used for observing the route flow direction of a dyeing request and the service condition of the route strategy.
5. The method as recited in claim 4, further comprising:
The remote procedure call request link observation center is combined with a distributed tracking system to construct a tracking model, wherein the tracking model defines a registrar role and a reporter role of a dyeing request route record track and an adapter role of a distributed tracking middleware;
and tracking each logic processing node through the adapter role of the distributed tracking middleware, recording each logic processing node through the registrar role, and reporting each logic processing node to the remote procedure call request link observation center through the reporter role.
6. A remote procedure call routing management control system for a micro service, comprising:
the route decision management and control center is used for managing route rules and matching strategies;
The route information pushing center is used for pushing route information in real time;
The management background is used for providing unified interface management operation capability;
the service consumer node reports the information of the application instance of the service consumer node to the routing decision management and control center when the service consumer node is started, and the routing decision management and control center manages the information of the application instance;
when the management background receives a management operation, if the management operation is a route management operation, the management background sends route management information corresponding to the route management operation to the route decision management and control center;
The routing decision control center analyzes the routing management information, determines that the routing rules and the matching strategies change, generates push information containing the change contents of the routing rules and the matching strategies, and provides the push information for the routing information push center to push;
The routing information pushing center pushes the pushing information to a corresponding target service consumer node, and the target service consumer node updates a local routing rule and a matching strategy according to the pushing information;
the push information comprises an application set and a notification set, wherein the application set represents a first service list bound by a routing rule and a matching strategy, and the first service list comprises service provider nodes in micro services; the notification set representing a second service list to use routing rules and matching policies, the second service list containing service consumer nodes in the micro-service;
The routing information pushing center pushes the pushing information to a corresponding target service consumer node, and the target service consumer node updates a local routing rule and a matching policy according to the pushing information, including:
The routing information pushing center acquires information of all application instances corresponding to the service consumer nodes of the notification set according to the pushing information, records a pushing log, pushes the pushing information to one or more corresponding target service consumer nodes, and updates a pushing state after pushing is completed;
the one or more target service consumer nodes receive the push information, update local routing rules and matching strategies according to the push information, and feed back update results to the routing information push center;
and the routing information pushing center receives feedback information containing the updating result, records the feedback information and updates the statistical data of the feedback information of the pushing record.
7. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the remote procedure call routing control method of the micro service according to any one of claims 1 to 5 when the computer program is executed.
8. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the steps of a remote procedure call routing management control method of a micro service according to any one of claims 1 to 5.
CN202210860309.2A 2022-07-21 2022-07-21 Remote procedure call route management control method, system and equipment for micro-service Active CN115102854B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210860309.2A CN115102854B (en) 2022-07-21 2022-07-21 Remote procedure call route management control method, system and equipment for micro-service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210860309.2A CN115102854B (en) 2022-07-21 2022-07-21 Remote procedure call route management control method, system and equipment for micro-service

Publications (2)

Publication Number Publication Date
CN115102854A CN115102854A (en) 2022-09-23
CN115102854B true CN115102854B (en) 2024-05-14

Family

ID=83299382

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210860309.2A Active CN115102854B (en) 2022-07-21 2022-07-21 Remote procedure call route management control method, system and equipment for micro-service

Country Status (1)

Country Link
CN (1) CN115102854B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109639572A (en) * 2018-12-06 2019-04-16 网易（杭州）网络有限公司 Route management method, device and micro services system
CN111970198A (en) * 2020-08-13 2020-11-20 北京金山云网络技术有限公司 Service routing method, device, electronic equipment and medium
CN112804722A (en) * 2020-12-31 2021-05-14 浪潮云信息技术股份公司 Method for realizing micro-service gateway dynamic routing
CN113794636A (en) * 2021-08-11 2021-12-14 科大国创云网科技有限公司 Dynamic routing arrangement method and system based on Spring Cloud Gateway

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109639572A (en) * 2018-12-06 2019-04-16 网易（杭州）网络有限公司 Route management method, device and micro services system
CN111970198A (en) * 2020-08-13 2020-11-20 北京金山云网络技术有限公司 Service routing method, device, electronic equipment and medium
CN112804722A (en) * 2020-12-31 2021-05-14 浪潮云信息技术股份公司 Method for realizing micro-service gateway dynamic routing
CN113794636A (en) * 2021-08-11 2021-12-14 科大国创云网科技有限公司 Dynamic routing arrangement method and system based on Spring Cloud Gateway

Also Published As

Publication number Publication date
CN115102854A (en) 2022-09-23

Similar Documents

Publication Publication Date Title
US20220094761A1 (en) Server Invocation Method and Proxy Server
US8156219B2 (en) System and method of health monitoring and fault monitoring in a network system
US7739391B2 (en) Gateway for wireless mobile clients
US7518983B2 (en) Proxy response apparatus
CN109104368B (en) Connection request method, device, server and computer readable storage medium
US20100325252A1 (en) Broker system for a plurality of brokers, clients and servers in a heterogeneous network
US7260596B1 (en) Distributed service provider
CN112671554A (en) Node fault processing method and related device
CN113347037A (en) Data center access method and device
CN116319732A (en) Message queue centralized configuration management system and method based on RabbitMQ
CN113810474B (en) Request distribution method and terminal
CN110933188A (en) Remote service calling method, system, server and storage medium
CN110995829A (en) Instance calling method and device and computer storage medium
US20240089352A1 (en) Udp message distribution method, udp message distribution apparatus, electronic device and computer readable storage medium
CN108111630B (en) Zookeeper cluster system and connection method and system thereof
CN116633993B (en) Cross-network micro-service calling method, device, equipment and storage medium
CN115102854B (en) Remote procedure call route management control method, system and equipment for micro-service
US20190387054A1 (en) Method, electronic device and computer program product for searching for node
US11582345B2 (en) Context data management interface for contact center
CN113949631A (en) Client disaster tolerance processing method and system and electronic equipment
CN114363403A (en) Service access method, system, computer device and storage medium
US10419368B1 (en) Dynamic scaling of computing message architecture
CN110995890A (en) Domain name request scheduling method and device
US10313254B1 (en) Network management interface for a network element with network-wide information
CN110740151A (en) micro-service adjusting method, device, server and computer storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant