CN112615786A - Route determining method and device, electronic equipment and computer readable storage medium - Google Patents
Route determining method and device, electronic equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN112615786A CN112615786A CN202011419943.XA CN202011419943A CN112615786A CN 112615786 A CN112615786 A CN 112615786A CN 202011419943 A CN202011419943 A CN 202011419943A CN 112615786 A CN112615786 A CN 112615786A
- Authority
- CN
- China
- Prior art keywords
- node
- service
- nodes
- consumption
- path
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 58
- 230000008859 change Effects 0.000 claims abstract description 78
- 238000004364 calculation method Methods 0.000 claims abstract description 20
- 230000001960 triggered effect Effects 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 8
- 238000012545 processing Methods 0.000 claims description 2
- 238000007726 management method Methods 0.000 description 67
- 230000006870 function Effects 0.000 description 17
- 230000008569 process Effects 0.000 description 11
- 238000012217 deletion Methods 0.000 description 10
- 230000037430 deletion Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 6
- 230000000694 effects Effects 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000013499 data model Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000007480 spreading Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Abstract
The invention relates to a route determining method, a route determining device, electronic equipment and a computer readable storage medium, wherein the method comprises the following steps: when receiving consumption service application information between service nodes sent by an API gateway node, acquiring the attribute of each node and the connection relation between the nodes; updating node topological data stored in a graph database according to the attribute of each node and the connection relation between the nodes; calling a graph calculation engine to calculate a path between a service consumption node and a service providing node according to the node topology data and the service consumption node and the service providing node which are included in the consumption service application information; and generating routing information according to the path, and sending the routing information to the API gateway node included in the path, so that the service consumption node completes access to the service providing node according to the routing information stored in the API gateway node included in the path, and access unreachability caused by node change is avoided.
Description
Technical Field
The present application belongs to the field of communications, and in particular, to a method and an apparatus for determining a route, an electronic device, and a computer-readable storage medium.
Background
A fully functional system typically includes multiple functions. Each function may be represented by a micro-service, and accordingly, a system may include multiple micro-services. In general, a microservice may include a service instance (process); the same microservice may also include multiple service instances for some common functions. If each service instance is considered a node, then for a system, multiple service instance nodes (also referred to as service nodes) may be included.
In addition, a plurality of API (Application Programming Interface) gateways may be included for one system. At least one API gateway in the plurality of API gateways is used for carrying out information interaction with each service instance node and is called as a first type API gateway; at least one API gateway in the plurality of API gateways is used for information interaction with other external systems and is called a public gateway or a second type of API gateway.
In a practical application scenario, a system is generally regarded as a cluster, and a plurality of clusters are communicatively connected, thereby forming a complex network environment including a large number of service instance nodes and gateway nodes.
In the complex network environment, when a service instance node a belonging to a cluster a needs to access a service instance node B of a cluster B, the service instance node a and the service instance node B need to interact with each other through a series of API gateway nodes.
In the prior art, generally, background staff configures routing information according to the connection relationship between nodes and issues the routing information to each API gateway node, and once the routing is configured and issued, the routing cannot be changed.
However, each node has flexibility, for example, an API gateway node or a service instance node is added, and then, for example, an original API gateway node or a service instance node is deleted, once a connection relationship between nodes changes, if information is still forwarded according to original routing information, access between nodes may be unreachable.
Disclosure of Invention
In view of the above, an object of the present application is to provide a method, an apparatus, an electronic device, and a computer-readable storage medium for determining a route, which can calculate a path according to current real-time network topology data and issue routing information to a relevant API gateway node when an access request exists between service nodes, so as to avoid access unreachability caused by node change.
The embodiment of the application is realized as follows:
in a first aspect, an embodiment of the present application provides a method for determining a route, where the method is applied to a service management console, and the method includes: when receiving consumption service application information between service nodes sent by API gateway nodes, acquiring the attribute of each node and the connection relation between the nodes, wherein the nodes comprise the API gateway nodes and the service nodes registered in each API gateway node; updating node topological data stored in a graph database according to the attribute of each node and the connection relation between the nodes; calling a graph calculation engine to calculate a path between the service consumption node and the service providing node according to the node topology data, the service consumption node and the service providing node which are included in the consumption service application information; and generating routing information according to the path, and sending the routing information to the API gateway node included in the path, so that the service consumption node completes access to the service providing node according to the routing information stored in the API gateway node included in the path.
In this embodiment, when there is an access requirement between service nodes and routing information needs to be determined, the service management console may determine, according to the obtained node attributes and the connection relationship between the nodes, an reachable path between the service consumption node and the service providing node, so that the service management console may calculate, according to the determined path, currently reachable routing information and issue the route information to the API gateway node through which the path needs to pass, so that the service consumption node may successfully access the service providing node. In the process, even if the original node is changed to possibly cause that the path corresponding to the original routing information is unreachable, the reachable path can be calculated as far as possible according to the currently acquired node attributes and the connection relationship between the nodes, so that the unreachable access caused by the node change is avoided.
With reference to the embodiment of the first aspect, in a possible implementation manner, the obtaining attributes of each node and a connection relationship between nodes includes: when the node change information is determined to be acquired, updating the previously stored node attributes and the connection relations among the nodes according to the node attributes and the connection relations included in the node change information to obtain the connection relations among the node attributes and the nodes; and when determining that the node change information is not acquired, determining the previously stored node attributes and the connection relationship between the nodes as the connection relationship between the node attributes and the nodes. That is, when there is node change information, the current node attributes and the connection relationship between nodes can be updated according to the node change information, so as to ensure that the latest node attributes and the latest connection relationship between nodes can be obtained, and prevent the unreachable access caused by node change.
With reference to the first aspect, in a possible implementation manner, the generation of the node change information is triggered by at least one of an online state of an original offline node, an offline state of an original online node, registration of a newly added node, and deletion of an original node.
With reference to the embodiment of the first aspect, in a possible implementation manner, when the generation of the node change information is triggered by an offline of an original online node or by deletion of the original online node, the method further includes: and deleting the routing information which is associated with the original node of the offline and the deleted original node in the routing information issued last time. That is, when there is an offline node or a deleted node, the routing information related to the offline node or the deleted node may cause access unreachability, and at this time, the routing information related to the offline node or the deleted node needs to be deleted, so as to avoid subsequent access unreachability.
With reference to the embodiment of the first aspect, in a possible implementation manner, the calculating a path between the service consumption node and the service providing node includes: calculating at least one of a reachable path, a shortest path, or an optimal path between the service consuming node and the service providing node.
In a second aspect, an embodiment of the present application provides a route determining method, which is applied to an API gateway node, and the method includes: when any registered service node initiates consumption service application information between service nodes, the consumption service application information is sent to a service management console, so that the service management console calls a graph calculation engine to calculate a path between the service consumption node and the service providing node according to node topology data stored in a graph database, the service consumption node and the service providing node included in the consumption service application information; receiving routing information generated by the service management console according to the path; and executing consumption service access between service nodes according to the routing information.
With reference to the second aspect, in one possible implementation manner, the method further includes: acquiring node changes of service nodes having registration relations with the service nodes, wherein the node changes comprise at least one of the offline of the original online service nodes and the online of the original offline service nodes; generating node change information according to the node change; and sending the node change information to the service management console so that the service management console updates the node topology data stored in the graph database according to the node change information.
In a third aspect, an embodiment of the present application provides a route determining apparatus, which is applied to a service management console, and the apparatus includes: the device comprises an acquisition module, an updating module, a calculation module and a sending module. The system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring the attribute of each node and the connection relation between the nodes when receiving consumption service application information between service nodes sent by an API gateway node, and the nodes comprise the API gateway node and the service nodes registered in each API gateway node; the updating module is used for updating the node topological data stored in the graph database according to the node attributes and the connection relation among the nodes; a computation module, configured to invoke a graph computation engine to compute a path between the service consumption node and the service providing node according to the node topology data, the service consumption node and the service providing node included in the consumption service application information; and the issuing module is used for generating routing information according to the path and issuing the routing information to the API gateway node included in the path so that the service consumption node completes the access to the service providing node according to the routing information stored in the API gateway node included in the path.
With reference to the third aspect, in a possible implementation manner, the obtaining module is configured to, when determining to obtain the node change information, update, according to the node attribute and the connection relationship included in the node change information, the previously stored node attribute and connection relationship between nodes, so as to obtain the connection relationship between the node attribute and the node; and when determining that the node change information is not acquired, determining the previously stored node attributes and the connection relationship between the nodes as the connection relationship between the node attributes and the nodes.
With reference to the third aspect, in a possible implementation manner, the generation of the node change information is triggered by at least one of an online state of an original offline node, an offline state of an original online node, registration of a newly added node, and deletion of an original node.
With reference to the third aspect, in a possible implementation manner, the apparatus further includes a deleting module, configured to delete, when generation of the node change information is triggered by an offline of an original online node or by deletion of an original node, routing information that is associated with the offline original node and the deleted original node in routing information that has been delivered last time.
With reference to the third aspect, in a possible implementation manner, the calculating module is configured to calculate at least one of a reachable path, a shortest path, or an optimal path between the service consuming node and the service providing node.
In a fourth aspect, an embodiment of the present application further provides a routing determination apparatus, which is applied to an API gateway node, and the apparatus includes: the device comprises a sending module, a receiving module and an access module. A sending module, configured to send consumption service application information to a service management console when any registered service node initiates the consumption service application information between service nodes, so that the service management console invokes a graph calculation engine to calculate a path between a service consumption node and a service providing node according to node topology data stored in a graph database, the service consumption node and the service providing node included in the consumption service application information; a receiving module, configured to receive routing information generated by the service management console according to the path; and the access module is used for executing consumption service access between the service nodes according to the routing information.
With reference to the fourth aspect, in a possible implementation manner, the apparatus further includes an obtaining module, configured to obtain a node change of a service node having a registration relationship with the device, where the node change includes at least one of an offline service node of an original online service node and an online service node of an original offline service node; a generation module for generating node change information according to the node change; the sending module is further configured to send the node change information to the service management console, so that the service management console updates the node topology data stored in the graph database according to the node change information.
In a fifth aspect, an embodiment of the present application further provides an electronic device, including: a memory and a processor, the memory and the processor connected; the memory is used for storing programs; the processor calls a program stored in the memory to perform the method of the first aspect embodiment and/or any possible implementation manner of the first aspect embodiment.
In a sixth aspect, the present application further provides a non-transitory computer-readable storage medium (hereinafter, referred to as a computer-readable storage medium), on which a computer program is stored, where the computer program is executed by a computer to perform the method in the foregoing first aspect and/or any possible implementation manner of the first aspect.
Additional features and advantages of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the embodiments of the application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description and drawings.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts. The foregoing and other objects, features and advantages of the application will be apparent from the accompanying drawings. Like reference numerals refer to like parts throughout the drawings. The drawings are not intended to be to scale as practical, emphasis instead being placed upon illustrating the subject matter of the present application.
Fig. 1 shows one of flowcharts of a route determination method provided in an embodiment of the present application.
Fig. 2 shows a schematic structural diagram of a management platform provided in an embodiment of the present application.
Fig. 3 illustrates a topology diagram between nodes according to an embodiment of the present disclosure.
Fig. 4 shows a second flowchart of a route determination method according to an embodiment of the present application.
Fig. 5 shows one of the block diagrams of the structure of a route determination device according to an embodiment of the present application.
Fig. 6 shows a second block diagram of a route determination device according to an embodiment of the present application.
Fig. 7 shows a schematic structural diagram of an electronic device provided in an embodiment of the present application.
Icon: 10-a management platform; 11-service management console; 12-a registry; 13-an API gateway; 100-an electronic device; 110-a processor; 120-a memory; 400-route determination means; 410-an obtaining module; 420-an update module; 430-a calculation module; 440-a distribution module; 500-a route determination device; 510-a sending module; 520-a receiving module; 530-Access Module.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, relational terms such as "first," "second," and the like may be used solely in the description herein to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Further, the term "and/or" in the present application is only one kind of association relationship describing the associated object, and means that three kinds of relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone.
In addition, the drawback of the route determination scheme in the prior art (the original route may cause some inaccessible access once the connection relationship between the original nodes is changed on the premise that the route is statically configured) is the result obtained after the applicant has been practiced and studied, and therefore, the discovery process of the aforesaid drawback and the solution proposed by the embodiment of the present application to the aforesaid drawback in the following should be considered as the contribution of the applicant to the present application.
In order to solve the above problem, embodiments of the present application provide a technique for determining a route, which can calculate a path according to a current real-time network topology and issue routing information to a relevant API gateway node, so as to avoid unreachable access due to node change.
The technology can be realized by adopting corresponding software, hardware and a combination of software and hardware. The following describes embodiments of the present application in detail.
First, a description will be given of a route determination method provided in the present application.
Referring to fig. 1, an embodiment of the present application provides a method for determining a route of a service management console applied to a management platform, including the following steps.
Step S110: and when receiving consumption service application information between service nodes sent by the API gateway node, acquiring the attribute of each node and the connection relation between the nodes, wherein the nodes comprise the API gateway node and the service nodes registered in each API gateway node.
Step S120: and updating the node topology data stored in the graph database according to the node attributes and the connection relationship among the nodes.
Step S130: and calling a graph calculation engine to calculate a path between the service consumption node and the service providing node according to the node topology data, the service consumption node and the service providing node which are included in the consumption service application information.
Step S140: and generating routing information according to the path, and sending the routing information to the API gateway node included in the path, so that the service consumption node completes access to the service providing node according to the routing information stored in the API gateway node included in the path.
The management platform may be a master cluster of the plurality of clusters included in the complex network environment mentioned in the above background, and the master cluster may manage other clusters.
Optionally, referring to fig. 2, the management platform 10 may include a service management console 11, a registry 12, and an API gateway 13 (i.e., an API gateway node mentioned later).
When the master cluster and each node (which may be a service node or an API gateway node) included in each cluster are changed from online to offline, the API gateway node connected to the node needs to be notified. In the embodiment of the present application, after the API gateway node in each cluster senses the change of other nodes, the relevant node change information is notified to the registry 12. In other words, registry 12 may sense changes to various nodes.
Further, a graph calculation engine and a graph database are arranged in advance in the memory of the service management console 11.
The graph computation engine is a technology which focuses on global query, and can optimize large-scale data in a batch mode.
The graph database is an online graph database management system and supports operations of adding, deleting, modifying, searching and the like of a graph data model.
In the embodiment of the application, after each cluster forms a complex network environment, background staff can configure node attributes and connection relations among the nodes according to actual conditions and logic relations among the nodes, and store the node attributes and the connection relations among the nodes in a graph database.
The node attribute of a node is used to represent the state of the node, for example, the node attribute of a certain node is online or offline.
It is worth pointing out that when there is a connection between two nodes, it means that the information between the two nodes is reachable from each other.
Subsequently, a topology map (as shown in fig. 3) and node topology data between nodes in the topology map may be generated according to the node attributes of the nodes and the connection relationships between the nodes, which are configured in advance. The node topology data comprises node attributes and connection relations among the nodes. And the two nodes with the connection relation are connected by using a line segment, so that the node visualization effect is realized.
Of course, the topology map and topology data are stored in a map database.
In addition, the graph calculation engine may calculate a path available for communication between the respective nodes according to the node attributes of the respective nodes configured in advance and the connection relationship between the respective nodes.
As an alternative embodiment, the path may include at least one of a reachable path, a shortest path, or an optimal path.
Of course, how to calculate the reachable path, the shortest path, or the optimal path according to the connection relationship is a relatively mature prior art, and is not described herein again.
After obtaining each path, the service management console 11 may generate routing information according to the path, and send the routing information to the API gateway node associated with the path.
The routing information may include an IP port corresponding to the path, service information, node information, and the like.
The steps involved will be described below with reference to fig. 1.
Step S110: and when receiving consumption service application information between service nodes sent by the API gateway node, acquiring the attribute of each node and the connection relation between the nodes, wherein the nodes comprise the API gateway node and the service nodes registered in each API gateway node.
It should be noted that, in the embodiment of the present application, after a plurality of clusters are connected to each other to form a complex network environment including a plurality of micro services, the complex network environment may provide a plurality of functions to the outside, and generate a corresponding service directory in a service level thereof, where the functions corresponding to all service nodes that have completed registration are recorded in the service directory.
In one embodiment, the complex network environment may provide an interface to expose the functionality that is currently available to the user for selection. Of course, information such as the use of each function may be displayed in the interface, and a user may be provided with an option to perform a query.
At this time, as for the interface of the current function selection of the user, the interface is a running process, and the service node corresponding to the process has the role of a service consumption node for the whole complex network environment; regarding the service node corresponding to the process corresponding to the function selected by the user, the role of the service node is a service providing node.
In the embodiment of the present application, before a service consuming node needs to access a service providing node, the service consuming node needs to generate consuming service application information between service nodes, and send the consuming service application information to the service management console 11 through a first type API gateway corresponding to the service consuming node.
The consumption service application information carries information, such as name information, related to the service consumption node and the service providing node.
After the service management console 11 obtains the consumption service application information in the current period, the service consumption node and the service providing node in the current period can be determined, and then the service management console 11 can obtain the node attributes of the nodes and the connection relationship between the nodes, so as to prepare for calculating the path between the service consumption node and the service providing node.
The following description will be made with respect to the service management console 11 acquiring the attribute of each node and the connection relationship between the nodes.
In some embodiments, if the service management console 11 does not acquire the node change information in the current cycle, it means that the node attribute and the connection relationship between the nodes at the current time are the same as those in the previous cycle. In this case, the service management console 11 may determine the node attributes and the connection relationships between the nodes stored in the previous time as the connection relationships between the node attributes and the nodes at the current time.
In some embodiments, if the service management console 11 acquires the node change information in the current period, it means that the node attribute and the connection relationship between the nodes at the current time are different from those in the previous period. At this time, the service management console 11 may update the node attributes and the connection relationships between the nodes stored in the previous time, and obtain the node attributes and the connection relationships between the nodes at the current time.
As for the node attributes and the connection relationships between nodes stored in the previous period (assuming that the current period is N, the previous period is N-1), the node attributes and the connection relationships between nodes stored in the previous period (N-2) may be obtained according to the two embodiments (two embodiments of whether node change information is obtained) until the first period is traced back, and the node attributes of the original nodes and the original connection relationships between the original nodes are configured by the background staff.
It should be noted that a cycle mentioned above may refer to a time period, and may also refer to an instant. The specific duration of a period can be configured by the staff according to the actual situation.
The generation of the node change information is triggered by at least one of the conditions of the original offline node online, the original online node offline, the newly added node registration and the original node deletion.
In each cluster, when an original online node goes offline and an original offline node goes online, the API gateway node in the cluster where the node is located and in communication connection with the node needs to be notified. The API gateway node generates node change information according to the original online node being offline and the original offline node being online, and synchronizes the node change information to the registry 12. The node change information includes the node attribute of the node with the state change and the connection relationship between the node with the state change and other nodes.
The registry 12 may send the obtained node change information to the service management console 11 within a preset time interval period, so that the service management console 11 may determine the current state of each node.
Further, when the change of the node is caused by the registration of the newly added node (i.e., the newly added node) or the deletion of the original node, since the newly added node temporarily does not establish a communication connection with the API gateway node and the communication connection between the deleted node and the API gateway node is deleted, the API gateway node cannot acquire the node change caused by the deletion of the newly added node or the original online node.
Under the condition, a background worker needs to add a corresponding newly added node in the topological graph in a topological graph management interface in a manual configuration mode, and configure corresponding newly added node attributes and connection relations between the newly added node and other nodes for the newly added node; for deleting the nodes, the connection relationship between the deleted nodes and other nodes needs to be deleted in the topological graph by a background worker in a topological graph management interface in a manual configuration mode, and the corresponding connection relationship is adjusted.
In addition, the background staff configures corresponding node change information for the deletion of the added node and the node, and stores the node change information in the service management console 11, so that the service management console 11 can determine the current state of each node. Of course, the node change information configured by the background staff also includes the node attribute of the node with the state change and the connection relationship between the node with the state change and other nodes.
After the service management console 11 obtains the node change information sent by the API gateway node through the registry 12 or the node change information configured by the background staff, the node attributes and the connection relationships between the nodes stored in the previous time (for convenience of distinction, referred to as previous node attributes and previous connection relationships) may be updated according to the node attributes and the connection relationships included in the node change information, so as to obtain the node attributes and the connection relationships between the nodes at the current time.
For example, for a newly added node, on the basis of the previous connection relationship, a new node is newly added, the connection relationship of the new node is added, and the node attribute of the new node is added; and for the deleted node, deleting the node and the connection relation connected with the node on the basis of the previous connection relation.
It is worth pointing out that, for an original online node to go offline suddenly, or for an original offline node to go online suddenly, only the node attribute of the node may be changed without changing the connection relationship between the original online node and other nodes and without changing the connection relationship between the original offline node and other nodes, for example, for an offline node, the node attribute of the offline node is changed to "offline" (at this time, the connection relationship between the offline node and other nodes may be maintained); for an online node, the node attribute of the online node is changed to be 'online'.
Step S120: and updating the node topology data stored in the graph database according to the node attributes and the connection relationship among the nodes.
As mentioned previously, node topology data is maintained in a graph database.
After the service management console 11 obtains the current node attributes and the connection relationships between the nodes, the service management console may update the original node topology data according to the node attributes and the connection relationships between the nodes, so as to obtain updated node topology data.
For example, for the case that the original offline node is online, the node attribute of the original offline node may be changed to "online".
For example, for the case that the original online node goes offline, the node attribute of the original online node may be changed to "offline".
For example, for the case of the newly added node, the newly added node is added into the topological graph of the graph database, and a connecting line corresponding to the newly added node and the connecting relationship thereof is formed in the topological graph according to the connecting relationship between the newly added node and other nodes. In addition, the node attribute corresponding to the newly added node in the node topology data can be set to be on-line, and the connection relationship between the newly added node and other nodes can be updated to the node topology data.
For example, for a deleted node, the deleted node and a connection line corresponding to the original connection relationship thereof may be deleted in the topology map. If the deleted node is the API gateway node, the connection between the service node and the API gateway node in the original topology map that has a connection relationship with the deleted node should be disconnected. In addition, for the deleted node, the connection relationship between the deleted node and other nodes in the node topology data can also be deleted.
It is worth pointing out that any one of the addition, deletion, online and offline of the node triggers the update of the node topology data, thereby triggering the update of the subsequent path and the routing information.
Step S130: and calling a graph calculation engine to calculate a path between the service consumption node and the service providing node according to the node topology data, the service consumption node and the service providing node which are included in the consumption service application information.
In the embodiment of the present application, the service management console 11 searches for node topology data by using a service consuming node as a starting point and a service providing node as an ending point, and by calling a graph calculation engine to calculate, thereby determining a path through which the service consuming node can reach the service providing node.
Of course, for the historical service consuming nodes and the historical service providing nodes existing in the historical period, if the historical service consuming nodes continue to access the historical service providing nodes to the current period, the service management console 11 may also call the graph calculation engine to update the paths between the historical service consuming nodes and the historical service providing nodes according to the current node topology data, the historical service consuming nodes, and the historical service providing nodes, so as to avoid unreachable between the historical service consuming nodes and the historical service providing nodes caused by node change.
Of course, the path between the service consuming node and the service providing node calculated here may also include at least one of a reachable path, a shortest path, or an optimal path.
Step S140: and generating routing information according to the path, and sending the routing information to the API gateway node included in the path, so that the service consumption node completes access to the service providing node according to the routing information stored in the API gateway node included in the path.
The API gateway node included in the path is the API gateway node which is needed to pass through the path used by the service consumption node when accessing the service providing node.
It is worth pointing out that if the service consumption node and the service providing node belong to the same cluster, the consumption of the service can be completed in the cluster, and the related API gateway node is the first type API gateway in the cluster; if the service consumption node and the service providing node belong to different clusters, for example, the service consumption node belongs to a cluster A, and the service providing node belongs to a cluster B, the service consumption can be completed only by crossing the clusters, and the related API gateway nodes at least comprise a first type API gateway in the cluster A, a second type API gateway in the cluster A, the first type API gateway in the cluster B and the second type API gateway in the cluster B.
Correspondingly, if the service consumption node and the service providing node belong to the same cluster, the API gateway node included in the path is the first type of API gateway in the cluster.
If a plurality of first type API gateways exist in the cluster, and the service consumption node and the service providing node are respectively connected with different first type API gateways, the API gateway nodes included in the path at least include the first type API gateway connected with the service consumption node and the first type API gateway connected with the service providing node in the cluster.
Correspondingly, according to the above example, if the service consuming node and the service providing node belong to different clusters, the API gateway nodes included in the path at least include the first type API gateway in cluster a, the second type API gateway in cluster a, the first type API gateway in cluster B, and the second type API gateway in cluster B.
After the routing information is issued to the API gateway node related to the path between the service consumption node and the service providing node, the service consumption node can send an access request to the API gateway node directly connected with the service consumption node, after the API gateway node obtains the access request, the API gateway node inquires the routing information issued in advance according to the service consumption node and the service providing party carried in the access request, and forwards the access request to the next node according to the routing information inquiry result, so that the access request is finally transmitted to the service providing node, and the effect that the service consumption node accesses the service providing node is achieved.
When the access requirement exists and the routing information needs to be determined, the service management console 11 may determine an reachable path between the service consumption node and the service providing node according to the current node attributes and the connection relationship between the nodes, so that the service management console 11 may calculate the currently reachable routing information according to the determined path and issue the route information to the API gateway node through which the path needs to pass, thereby enabling the service consumption node to successfully access the service providing node. Because the routing information is calculated by the service management console 11 in real time according to the current node attributes and the connection relationships between nodes, instead of using the static configuration routing in the prior art (in the prior art, the gateways do not have a function of transmitting node change information and may cause access unreachable), in the process, even if there is node change and the path corresponding to the original routing information is unreachable, the service management console 11 may calculate reachable paths as much as possible according to the current node attributes and the connection relationships between nodes, thereby avoiding access unreachable caused by node change.
For the situation that a new node exists, the pressure is generally balanced for the original node with the same function. However, in the prior art, because the service management console 11 cannot sense the dynamic capacity expansion of the node, the node with the same function cannot be applied to the actual access request in time, so that the newly added node cannot exhibit the effect of spreading the pressure in time.
By the route determination scheme provided by the embodiment of the application, because dynamic expansion of the nodes can be sensed in real time, when a path is determined, the effect of pressure equalization of newly added nodes can be realized in time through a series of load balancing strategies.
In addition, in some embodiments, when the original node goes offline or is deleted, the service management console 11 may move out of the routing information that has been issued last time, and there is associated routing information with the offline original node or the deleted original node, so as to avoid that the access is not reachable.
In addition, if the offline node or the deleted node is a service node and the service node is a current service providing node, at this time, after deleting the routing information related to the offline or the deleted service node, the service management console 11 may also search whether there is a target service node that provides the same service as the offline or the deleted service node, so as to replace the offline or the deleted service node, and determine the target service node as the current service providing node. If the target service node does not exist, the service management console 11 sends out a disaster tolerance alarm to remind the user that the service is not available.
And if the node which is down-line or deleted is the API gateway node, and the API gateway node is the API gateway node which is required to pass through in the current access request. At this time, after removing the routing information related to the offline or deleted API gateway node, the service management console 11 may also search whether an API gateway node that can replace the offline exists, so as to access a target gateway node that can reach the service providing node. If the target API gateway node does not exist, the service management console 11 sends out a disaster tolerance alarm to remind the user that the service is not available.
Of course, in some embodiments, the above nodes may be applied to a 5G core network, that is, the above mentioned complex network environment is the 5G core network, and the route determining method provided in this embodiment of the present application is used to implement call interaction between services in the 5G core network.
In addition, please refer to fig. 4, an embodiment of the present application further provides a route determining method, which is applied to the API gateway node. The method comprises the following steps.
Step S210: when any registered service node initiates consumption service application information between service nodes, the consumption service application information is sent to a service management console, so that the service management console calls a graph calculation engine to calculate a path between the service consumption node and the service providing node according to node topology data stored in a graph database, the service consumption node and the service providing node included in the consumption service application information.
Step S220: and receiving the routing information generated by the service management console according to the path.
Step S230: and executing consumption service access between service nodes according to the routing information.
In addition, in some embodiments, when acquiring a node change of a service node having a registration relationship with the API gateway node, the API gateway node may further generate node change information according to the node change; and then the node change information is sent to the service management console, so that the service management console updates the node topology data stored in the graph database according to the node change information. The node change comprises at least one of the original online service node being offline and the original offline service node being online.
In addition, as shown in fig. 5, an embodiment of the present application further provides a route determining apparatus 400, where the route determining apparatus 400 may include: an acquisition module 410, an update module 420, a calculation module 430, and a delivery module 440.
An obtaining module 410, configured to obtain attributes of each node and a connection relationship between nodes when receiving consumption service application information between service nodes sent by an API gateway node, where the nodes include the API gateway node and service nodes registered in each API gateway node;
an updating module 420, configured to update the node topology data stored in the graph database according to the node attributes and the connection relationships between the nodes;
a calculation module 430, configured to invoke a graph calculation engine to calculate a path between the service consumption node and the service providing node according to the node topology data and the service consumption node and the service providing node included in the consumption service application information;
the issuing module 440 is configured to generate routing information according to the path, and issue the routing information to the API gateway node included in the path, so that the service consumption node completes access to the service providing node according to the routing information stored in the API gateway node included in the path.
In a possible implementation manner, the obtaining module 410 is configured to, when determining that the node change information is obtained, update the previously stored node attributes and the connection relationships between the nodes according to the node attributes and the connection relationships included in the node change information, so as to obtain the connection relationships between the node attributes and the nodes; and when determining that the node change information is not acquired, determining the previously stored node attributes and the connection relationship between the nodes as the connection relationship between the node attributes and the nodes.
In a possible implementation manner, the generation of the node change information is triggered by at least one of an original offline node being online, an original online node being offline, a newly added node being registered, and an original node being deleted.
In a possible implementation manner, the apparatus further includes a deleting module, configured to delete, when generation of the node change information is triggered by an offline of an original online node or by deletion of an original node, routing information that is associated with the offline original node and the deleted original node in routing information that has been issued last time.
In a possible implementation, the calculating module 430 is configured to calculate at least one of a reachable path, a shortest path, or an optimal path between the service consuming node and the service providing node.
The route determining apparatus 400 provided in the embodiment of the present application has the same implementation principle and the same technical effect as those of the foregoing method embodiments, and for the sake of brief description, reference may be made to the corresponding contents in the foregoing method embodiments for parts of the embodiments of the apparatus that are not mentioned.
In addition, as shown in fig. 6, an embodiment of the present application further provides a route determining apparatus 500, which is applied to an API gateway node, and includes a sending module 510, a receiving module 520, and an accessing module 530.
A sending module 510, configured to send consumption service application information to a service management console when any registered service node initiates the consumption service application information between service nodes, so that the service management console invokes a graph calculation engine to calculate a path between a service consumption node and a service providing node according to node topology data stored in a graph database, the service consumption node and the service providing node included in the consumption service application information;
a receiving module 520, configured to receive routing information generated by the service management console according to the path;
an accessing module 530, configured to perform a consuming service access between service nodes according to the routing information.
In a possible implementation, the route determining apparatus 500 further includes an obtaining module and a generating module.
The system comprises an acquisition module, a registration module and a registration module, wherein the acquisition module is used for acquiring node changes of service nodes having registration relations with the acquisition module, and the node changes comprise at least one of the offline of the original online service nodes and the online of the original offline service nodes;
a generation module for generating node change information according to the node change;
the sending module 510 is further configured to send the node change information to the service management console, so that the service management console updates the node topology data stored in the graph database according to the node change information.
In addition, an embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a computer, the steps included in the route determining method are executed.
In addition, please refer to fig. 7, an electronic device 100 is further provided in an embodiment of the present invention.
Alternatively, the electronic Device 100 may be, but is not limited to, a Personal Computer (PC), a Mobile Internet Device (MID), a server, and the like. The server may be, but is not limited to, a web server, a cloud server, and the like, and the management platform 10 is deployed on the electronic device 100.
Among them, the electronic device 100 may include: a processor 110, a memory 120.
It should be noted that the components and structure of electronic device 100 shown in FIG. 7 are exemplary only, and not limiting, and electronic device 100 may have other components and structures as desired.
The processor 110, memory 120, and other components that may be present in the electronic device 100 are electrically connected to each other, directly or indirectly, to enable the transfer or interaction of data. For example, the processor 110, the memory 120, and other components that may be present may be electrically coupled to each other via one or more communication buses or signal lines.
The memory 120 is used for storing a program, for example, a program corresponding to the route determination method appearing above or the route determination device appearing above. Optionally, when the route determination device is stored in the memory 120, the route determination device includes at least one software function module that can be stored in the memory 120 in the form of software or firmware (firmware).
Alternatively, the software function module included in the route determining apparatus may also be solidified in an Operating System (OS) of the electronic device 100.
The processor 110 is adapted to execute executable modules stored in the memory 120, such as software functional modules or computer programs comprised by the route determination device. The processor 110, upon receiving the execution instruction, may execute a computer program, for example, to perform the aforementioned route determination method.
Of course, the method disclosed in any of the embodiments of the present application can be applied to the processor 110, or implemented by the processor 110.
In summary, according to the route determining method, the apparatus, the electronic device, and the computer-readable storage medium provided in the embodiments of the present invention, when there is an access requirement between service nodes and routing information needs to be determined, the service management console may determine, according to the obtained node attributes and the connection relationship between the nodes, an reachable path between the service consumption node and the service providing node, so that the service management console may calculate, according to the determined path, currently reachable routing information and issue the route to the API gateway node that the path needs to pass through, so that the service consumption node may successfully access the service providing node. In the process, even if the original node is changed to possibly cause that the path corresponding to the original routing information is unreachable, the reachable path can be calculated as far as possible according to the currently acquired node attributes and the connection relationship between the nodes, so that the unreachable access caused by the node change is avoided.
It should be noted that, in the present specification, the embodiments are all described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a notebook computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application.
Claims (10)
1. A method for determining a route, applied to a service management console, the method comprising:
when receiving consumption service application information between service nodes sent by API gateway nodes, acquiring the attribute of each node and the connection relation between the nodes, wherein the nodes comprise the API gateway nodes and the service nodes registered in each API gateway node;
updating node topological data stored in a graph database according to the attribute of each node and the connection relation between the nodes;
calling a graph calculation engine to calculate a path between the service consumption node and the service providing node according to the node topology data, the service consumption node and the service providing node which are included in the consumption service application information;
and generating routing information according to the path, and sending the routing information to the API gateway node included in the path, so that the service consumption node completes access to the service providing node according to the routing information stored in the API gateway node included in the path.
2. The method according to claim 1, wherein the obtaining the node attributes and the connection relationships between nodes comprises:
when the node change information is determined to be acquired, updating the previously stored node attributes and the connection relations among the nodes according to the node attributes and the connection relations included in the node change information to obtain the connection relations among the node attributes and the nodes;
and when determining that the node change information is not acquired, determining the previously stored node attributes and the connection relationship between the nodes as the connection relationship between the node attributes and the nodes.
3. The method of claim 2, wherein the generation of the node change information is triggered by at least one of an original offline node being online, an original online node being offline, a newly added node being registered, and an original node being deleted.
4. The method of claim 3, wherein when the generation of the node change information is triggered by an original online node going down or an original node being deleted, the method further comprises:
and deleting the routing information which is associated with the original node of the offline and the deleted original node in the routing information issued last time.
5. A method for determining a route, applied to an API gateway node, the method comprising:
when any registered service node initiates consumption service application information between service nodes, the consumption service application information is sent to a service management console, so that the service management console calls a graph calculation engine to calculate a path between the service consumption node and the service providing node according to node topology data stored in a graph database, the service consumption node and the service providing node included in the consumption service application information;
receiving routing information generated by the service management console according to the path;
and executing consumption service access between service nodes according to the routing information.
6. The method of claim 5, further comprising:
acquiring node changes of service nodes having registration relations with the service nodes, wherein the node changes comprise at least one of the offline of the original online service nodes and the online of the original offline service nodes;
generating node change information according to the node change;
and sending the node change information to the service management console so that the service management console updates the node topology data stored in the graph database according to the node change information.
7. A route determining apparatus applied to a service management console, the apparatus comprising:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring the attribute of each node and the connection relation between the nodes when receiving consumption service application information between service nodes sent by an API gateway node, and the nodes comprise the API gateway node and the service nodes registered in each API gateway node;
the updating module is used for updating the node topological data stored in the graph database according to the node attributes and the connection relation among the nodes;
a computation module, configured to invoke a graph computation engine to compute a path between the service consumption node and the service providing node according to the node topology data, the service consumption node and the service providing node included in the consumption service application information;
and the issuing module is used for generating routing information according to the path and issuing the routing information to the API gateway node included in the path so that the service consumption node completes the access to the service providing node according to the routing information stored in the API gateway node included in the path.
8. A route determination apparatus, applied to an API gateway node, the apparatus comprising:
a sending module, configured to send consumption service application information to a service management console when any registered service node initiates the consumption service application information between service nodes, so that the service management console invokes a graph calculation engine to calculate a path between a service consumption node and a service providing node according to node topology data stored in a graph database, the service consumption node and the service providing node included in the consumption service application information;
a receiving module, configured to receive routing information generated by the service management console according to the path;
and the access module is used for executing consumption service access between the service nodes according to the routing information.
9. An electronic device, comprising: a memory and a processor, the memory and the processor connected;
the memory is used for storing programs;
the processor calls a program stored in the memory to perform the method of any of claims 1-6.
10. A computer-readable storage medium, on which a computer program is stored which, when executed by a computer, performs the method of any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011419943.XA CN112615786B (en) | 2020-12-04 | 2020-12-04 | Route determining method and device, electronic equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011419943.XA CN112615786B (en) | 2020-12-04 | 2020-12-04 | Route determining method and device, electronic equipment and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112615786A true CN112615786A (en) | 2021-04-06 |
| CN112615786B CN112615786B (en) | 2023-04-04 |
Family
ID=75229242
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011419943.XA Active CN112615786B (en) | 2020-12-04 | 2020-12-04 | Route determining method and device, electronic equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112615786B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113392350A (en) * | 2021-06-11 | 2021-09-14 | 中国联合网络通信集团有限公司 | Page routing processing method, device, equipment, storage medium and program product |
Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140282968A1 (en) * | 2013-03-15 | 2014-09-18 | Vonage Network Llc | Method for apparatus for routing application programming interface (api) calls |
| CN106385364A (en) * | 2016-09-05 | 2017-02-08 | 杭州华三通信技术有限公司 | Route updating method and device |
| CN107612955A (en) * | 2016-07-12 | 2018-01-19 | 深圳市远行科技股份有限公司 | Micro services provide method, apparatus and system |
| US20180278705A1 (en) * | 2017-03-24 | 2018-09-27 | Accenture Global Solutions Limited | Reactive api gateway |
| CN108900329A (en) * | 2018-06-21 | 2018-11-27 | 珠海宏桥高科技有限公司 | Real-time dynamic forwarding method based on gateway infrastructure service |
| CN109639572A (en) * | 2018-12-06 | 2019-04-16 | 网易（杭州）网络有限公司 | Route management method, device and micro services system |
| US10362141B1 (en) * | 2016-03-29 | 2019-07-23 | Amazon Technologies, Inc. | Service group interaction management |
| CN110336753A (en) * | 2019-06-19 | 2019-10-15 | 腾讯科技（深圳）有限公司 | A kind of service calling method, device, equipment and the storage medium in across a network region |
| CN110971449A (en) * | 2019-10-25 | 2020-04-07 | 武汉烽火众智数字技术有限责任公司 | Service management and control system based on micro-service architecture |
| CN111049695A (en) * | 2020-01-09 | 2020-04-21 | 深圳壹账通智能科技有限公司 | Cloud gateway configuration method and system |
| CN111092816A (en) * | 2019-11-26 | 2020-05-01 | 金蝶软件（中国）有限公司 | Gateway dynamic routing method, gateway dynamic routing device, computer equipment and storage medium |
| CN111314141A (en) * | 2020-02-21 | 2020-06-19 | 腾讯云计算（北京）有限责任公司 | Route updating method and device |
| CN111343237A (en) * | 2020-02-07 | 2020-06-26 | 广州亚美信息科技有限公司 | Server cluster communication method, communication device and computer storage medium |
| CN111464352A (en) * | 2020-03-31 | 2020-07-28 | 中国工商银行股份有限公司 | Call link data processing method and device |
| CN111539622A (en) * | 2020-04-22 | 2020-08-14 | 国网信通亿力科技有限责任公司 | Collective enterprise project management platform based on cloud platform and micro-service architecture |
| CN111884917A (en) * | 2020-07-28 | 2020-11-03 | 浪潮云信息技术股份公司 | Gateway system based on micro service and gateway dynamic routing method |
| CN111935286A (en) * | 2020-08-12 | 2020-11-13 | 创意信息技术股份有限公司 | Micro-service framework for software development and construction method thereof |
-
2020
- 2020-12-04 CN CN202011419943.XA patent/CN112615786B/en active Active
Patent Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140282968A1 (en) * | 2013-03-15 | 2014-09-18 | Vonage Network Llc | Method for apparatus for routing application programming interface (api) calls |
| US10362141B1 (en) * | 2016-03-29 | 2019-07-23 | Amazon Technologies, Inc. | Service group interaction management |
| CN107612955A (en) * | 2016-07-12 | 2018-01-19 | 深圳市远行科技股份有限公司 | Micro services provide method, apparatus and system |
| CN106385364A (en) * | 2016-09-05 | 2017-02-08 | 杭州华三通信技术有限公司 | Route updating method and device |
| US20180278705A1 (en) * | 2017-03-24 | 2018-09-27 | Accenture Global Solutions Limited | Reactive api gateway |
| CN108900329A (en) * | 2018-06-21 | 2018-11-27 | 珠海宏桥高科技有限公司 | Real-time dynamic forwarding method based on gateway infrastructure service |
| CN109639572A (en) * | 2018-12-06 | 2019-04-16 | 网易（杭州）网络有限公司 | Route management method, device and micro services system |
| CN110336753A (en) * | 2019-06-19 | 2019-10-15 | 腾讯科技（深圳）有限公司 | A kind of service calling method, device, equipment and the storage medium in across a network region |
| CN110971449A (en) * | 2019-10-25 | 2020-04-07 | 武汉烽火众智数字技术有限责任公司 | Service management and control system based on micro-service architecture |
| CN111092816A (en) * | 2019-11-26 | 2020-05-01 | 金蝶软件（中国）有限公司 | Gateway dynamic routing method, gateway dynamic routing device, computer equipment and storage medium |
| CN111049695A (en) * | 2020-01-09 | 2020-04-21 | 深圳壹账通智能科技有限公司 | Cloud gateway configuration method and system |
| CN111343237A (en) * | 2020-02-07 | 2020-06-26 | 广州亚美信息科技有限公司 | Server cluster communication method, communication device and computer storage medium |
| CN111314141A (en) * | 2020-02-21 | 2020-06-19 | 腾讯云计算（北京）有限责任公司 | Route updating method and device |
| CN111464352A (en) * | 2020-03-31 | 2020-07-28 | 中国工商银行股份有限公司 | Call link data processing method and device |
| CN111539622A (en) * | 2020-04-22 | 2020-08-14 | 国网信通亿力科技有限责任公司 | Collective enterprise project management platform based on cloud platform and micro-service architecture |
| CN111884917A (en) * | 2020-07-28 | 2020-11-03 | 浪潮云信息技术股份公司 | Gateway system based on micro service and gateway dynamic routing method |
| CN111935286A (en) * | 2020-08-12 | 2020-11-13 | 创意信息技术股份有限公司 | Micro-service framework for software development and construction method thereof |
Non-Patent Citations (1)
| Title |
|---|
| 赵 丹: "服务中心网络的服务寻址与路由关键技术研究", 《中国优秀硕士学位论文全文数据库》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113392350A (en) * | 2021-06-11 | 2021-09-14 | 中国联合网络通信集团有限公司 | Page routing processing method, device, equipment, storage medium and program product |
| CN113392350B (en) * | 2021-06-11 | 2023-07-04 | 中国联合网络通信集团有限公司 | Page routing processing method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112615786B (en) | 2023-04-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111193605B (en) | Fault positioning method and device and storage medium | |
| CN102571417A (en) | Method for realizing dynamic topology | |
| CN104199957A (en) | Redis universal agent implementation method | |
| CN106790131B (en) | Parameter modification method and device and distributed platform | |
| CN105099761A (en) | Method and system for concentratedly managing configuration information of client | |
| CN107404509B (en) | Distributed service configuration system and information management method | |
| CN103338243A (en) | Method and system for updating cache data of Web node | |
| WO2017036332A1 (en) | Distributed system-based gated launch method, client end and platform | |
| US8751711B2 (en) | Storage topology manager | |
| US7805503B2 (en) | Capability requirements for group membership | |
| CN109213604A (en) | A kind of management method and device of data source | |
| CN112615786B (en) | Route determining method and device, electronic equipment and computer readable storage medium | |
| CN113342547A (en) | Remote service calling method and device, electronic equipment and readable storage medium | |
| CN110213073B (en) | Data flow direction changing method, electronic device, computing node and storage medium | |
| CN108810166A (en) | Route management method, system, computer equipment and computer readable storage medium | |
| CN104660689A (en) | Distributed computing system | |
| CN111949831A (en) | Graphic database establishing method and device and readable storage medium | |
| CN111352716A (en) | Task request method, device and system based on big data and storage medium | |
| CN113127526A (en) | Distributed data storage and retrieval system based on Kubernetes | |
| CN103209196A (en) | Portal access method and device | |
| CN103685405B (en) | Network service system and the method updating firmware thereof | |
| CN111274004A (en) | Process instance management method and device and computer storage medium | |
| CN111147312A (en) | Resource allocation management method and device, resource allocation cache management method and device, and allocation management system | |
| KR101275995B1 (en) | Data storing system and data processing method of informational household appliance | |
| CN112804299B (en) | Node mapping method, node mapping device, mapping equipment and readable 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 | ||
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Hu Tianqi Inventor after: Dong Yue Inventor before: Hu Tianqi |