CN111770176A - Traffic scheduling method and device - Google Patents
Traffic scheduling method and device Download PDFInfo
- Publication number
- CN111770176A CN111770176A CN202010605250.3A CN202010605250A CN111770176A CN 111770176 A CN111770176 A CN 111770176A CN 202010605250 A CN202010605250 A CN 202010605250A CN 111770176 A CN111770176 A CN 111770176A
- Authority
- CN
- China
- Prior art keywords
- information
- service
- micro
- user
- access
- 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 76
- 230000004044 response Effects 0.000 claims abstract description 25
- 238000012986 modification Methods 0.000 claims description 21
- 230000004048 modification Effects 0.000 claims description 21
- 230000015654 memory Effects 0.000 claims description 19
- 238000012217 deletion Methods 0.000 claims description 2
- 230000037430 deletion Effects 0.000 claims description 2
- 238000012423 maintenance Methods 0.000 abstract description 8
- 230000000875 corresponding effect Effects 0.000 description 35
- 238000010586 diagram Methods 0.000 description 13
- 238000004891 communication Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 7
- 230000003993 interaction Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 239000003795 chemical substances by application Substances 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 108010001267 Protein Subunits Proteins 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- 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
-
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- 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/14—Session management
- H04L67/141—Setup of application sessions
-
- 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/2866—Architectures; Arrangements
- H04L67/30—Profiles
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The application discloses a traffic scheduling method and device, and relates to the technical field of remote procedure call, information flow and cloud service. The specific implementation scheme is as follows: in response to the fact that the micro service is determined to be on line, obtaining configuration meta-information of the micro service, wherein the configuration meta-information is used for representing users with the permission of accessing the micro service and access strategies to the micro service; and sending the configuration meta-information to a server for deploying the micro-service, and establishing a stable connection with the micro-service based on the configuration meta-information so as to provide the user with the access right to the micro-service and access the micro-service based on the configuration meta-information. According to the scheme, based on the identity information of the user requesting access, the flow division and the service load balance at the client side are realized, the introduction of additional gateway service nodes is avoided, and the service deployment and the service operation and maintenance are simplified.
Description
Technical Field
The embodiment of the disclosure relates to the technical field of computers, in particular to remote procedure call, information flow and cloud service technologies, and provides a traffic scheduling method and device.
Background
In a traditional micro-service architecture, traffic management is generally implemented through a service gateway. On one hand, the service gateway is responsible for routing forwarding, receiving all external requests and forwarding the external requests to the micro-service at the rear end; on the other hand, the service gateway can complete a series of crosscut functions, such as permission verification, current limitation, monitoring and the like.
Disclosure of Invention
The present disclosure provides a traffic scheduling method, apparatus, device, and storage medium.
According to a first aspect, the present disclosure provides a traffic scheduling method applied to a scheduling component, including: in response to the fact that the micro service is determined to be on line, obtaining configuration meta-information of the micro service, wherein the configuration meta-information is used for representing users with the permission of accessing the micro service and access strategies to the micro service; and sending the configuration meta-information to a server for deploying the micro-service, and establishing a stable connection with the micro-service based on the configuration meta-information so as to provide the user with the access right to the micro-service and access the micro-service based on the configuration meta-information.
According to a second aspect, the present disclosure provides a traffic scheduling method applied to a client, including: acquiring configuration meta-information of the micro-service in the scheduling component, wherein the configuration meta-information is used for representing a user with the permission of accessing the micro-service and an access strategy of the micro-service; and determining an access request for representing the access micro-service according to the received user request and the configuration meta-information, and accessing the micro-service based on the access request.
According to a third aspect, the present disclosure provides a traffic scheduling method applied to a server, including: acquiring configuration meta-information of the deployed micro-service, wherein the configuration meta-information is used for representing a user with the permission of accessing the micro-service and an access strategy of the micro-service; and establishing stable connection with the scheduling component based on the configuration meta-information so as to provide the user with the authority of accessing the micro-service and access the micro-service based on the configuration meta-information.
According to a fourth aspect, the present disclosure provides a traffic scheduling apparatus, which is applied to a scheduling component, and includes: the first acquisition unit is configured to respond to the fact that the micro service is determined to be on line, and acquire configuration meta-information of the micro service, wherein the configuration meta-information is used for representing a user with the authority of accessing the micro service and an access strategy of the micro service; and the first contact unit is configured to send the configuration meta-information to a server for deploying the micro-service, and establish stable contact with the micro-service based on the configuration meta-information, so that a user with the permission to access the micro-service can access the micro-service based on the configuration meta-information.
According to a fifth aspect, the present disclosure provides a traffic scheduling apparatus, applied to a client, including: the second acquisition unit is configured to acquire configuration meta-information of the micro-service in the scheduling component, wherein the configuration meta-information is used for representing a user with the authority of accessing the micro-service and an access strategy of the micro-service; and the access unit is configured to determine an access request for characterizing the access micro-service according to the received user request and the configuration meta-information, and access the micro-service based on the access request.
According to a sixth aspect, the present disclosure provides a traffic scheduling apparatus, applied to a server, including: the third acquisition unit is configured to acquire configuration meta-information of the deployed micro-service, wherein the configuration meta-information is used for representing a user with the authority of accessing the micro-service and an access strategy of the micro-service; and the second contact unit is configured to establish stable contact with the scheduling component based on the configuration meta-information so as to provide the users with the authority of accessing the micro-service and access the micro-service based on the configuration meta-information.
According to a seventh aspect, there is provided an electronic device comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of the first, second or third aspects.
According to an eighth aspect, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to perform the method of any of the first, second, third aspects above.
According to the technology of the application, based on the identity information of the user requesting access, the flow division and the service load balance at the client side are realized, the introduction of additional gateway service nodes is avoided, and the service deployment and the service operation and maintenance are simplified.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
FIG. 1 is an exemplary system architecture diagram in which one embodiment of the present disclosure may be applied;
FIG. 2 is a flow diagram of one embodiment of a traffic scheduling method applied to a scheduling component, in accordance with the present disclosure;
fig. 3 is a schematic diagram of an application scenario of a traffic scheduling method according to the present disclosure;
FIG. 4 is a flow diagram of yet another embodiment of a traffic scheduling method applied to a scheduling component in accordance with the present disclosure;
FIG. 5 is a flow diagram for one embodiment of a traffic scheduling method applied to a client, in accordance with the present disclosure;
FIG. 6 is a flow diagram for one embodiment of a traffic scheduling method applied to a server, in accordance with the present disclosure;
FIG. 7 is a flow diagram for one embodiment of traffic scheduler coordination, according to the present disclosure;
FIG. 8 is a flow diagram for one embodiment of a traffic scheduling apparatus applied to a scheduling component, in accordance with the present disclosure;
FIG. 9 is a flow diagram for one embodiment of a traffic scheduling apparatus applied to a client, according to the present disclosure;
FIG. 10 is a flow diagram for one embodiment of a traffic scheduling apparatus applied to a server, according to the present disclosure;
FIG. 11 is a schematic block diagram of a computer system suitable for use with an electronic device/terminal device or server embodying embodiments of the present disclosure.
Detailed Description
The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 shows an exemplary architecture 100 to which the traffic scheduling method and apparatus of the present application may be applied.
As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, a server 105, and a scheduling component 106. The network 104 serves to provide a medium for communication links between the terminal devices 101, 102, 103, the server 105 and the scheduling component 106. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The terminal devices 101, 102, 103 may be hardware devices or software that support network connections for data interaction and data processing. When the terminal devices 101, 102, and 103 are hardware, they may be various electronic devices supporting functions of information interaction, network connection, image capturing, and the like, including but not limited to smart phones, tablet computers, e-book readers, laptop portable computers, desktop computers, and the like. When the terminal apparatuses 101, 102, 103 are software, they can be installed in the electronic apparatuses listed above. It may be implemented, for example, as multiple software or software modules to provide distributed services, or as a single software or software module. And is not particularly limited herein.
The server 105 may be a server that provides various services, such as a background processing server that operates microservices deployed therein based on access requests sent by the terminal devices 101, 102, 103. Optionally, the background processing server may further feed back the operation result to the terminal device for the terminal device to use. As an example, the server 105 may be a cloud server.
The server may be hardware or software. When the server is hardware, it may be implemented as a distributed server cluster formed by multiple servers, or may be implemented as a single server. When the server is software, it may be implemented as multiple pieces of software or software modules (e.g., software or software modules used to provide distributed services), or as a single piece of software or software module. And is not particularly limited herein.
The scheduling component 106 can be an end device that provides traffic scheduling functionality including, but not limited to, a smartphone, a tablet, an e-book reader, a laptop portable computer, a desktop computer, a server, and the like. The contact of the microservice with the user is established, for example, on the basis of configuration meta-information of the microservice deployed in the server, so that the user can directly access the control component of the microservice in the server via the terminal device.
It should be further noted that, in the traffic scheduling method provided by the embodiments of the present disclosure, the scheduling method applied to the server may be executed by the server, the scheduling method applied to the client may be executed by the terminal device, the scheduling method applied to the scheduling component may be executed by the scheduling component, and the server, the terminal device, and the scheduling component are executed in cooperation with each other. Accordingly, the traffic scheduling apparatus includes various parts (e.g., various units, sub-units, modules, and sub-modules), the scheduling apparatus applied to the server may be disposed in the server, the scheduling apparatus applied to the client may be disposed in the terminal device, and the scheduling apparatus applied to the scheduling component may be disposed in the scheduling component.
It should be understood that the number of terminal devices, networks, servers, and scheduling components in fig. 1 are merely illustrative. There may be any number of terminal devices, networks, servers, and scheduling components, as desired for an implementation. When the electronic device on which the traffic scheduling method operates does not need to perform data transmission with other electronic devices, the system architecture may include only the electronic device (e.g., a server or a terminal device and a scheduling component) on which the traffic scheduling method operates.
With continuing reference to fig. 2, a flow 200 of one embodiment of a traffic scheduling method is shown, applied to a scheduling component, comprising the steps of:
In this embodiment, in response to determining that the micro service is online, the execution main body (e.g., the scheduling component in fig. 1) may obtain the configuration meta information of the micro service from a remote location or a local location through a wired connection or a wireless connection. The configuration meta-information is used for representing users having the right to access the micro-service and access strategies to the micro-service.
In this embodiment, the microservice is a small service composed of a single application, and has its own process and lightweight processing, and its service is designed according to business functions, deployed in a fully automatic manner, and communicates with other services. Different microservices in the same application may be deployed in different servers.
The configuration meta-information of the micro-service is used for representing the access strategy of the user with the right to access the micro-service to the micro-service. As an example, the configuration meta-information may include traffic load information that the micro-service can bear, resource size required by the micro-service, and other attribute information.
Specifically, the configuration meta-information may be specifically set according to the type of the micro-service, the overall resource of the micro-service architecture, and the like, and is not limited herein. As an example, corresponding default configuration meta-information may be set for various types of micro-services.
In some optional implementations of this embodiment, the configuration meta information includes identity information of a user having a right to access the micro service, and attribution information of the micro service to the server. The served object of the micro service can be determined by configuring the identity information of the user with the access micro service authority in the meta information; by configuring the attribution information of the micro-service to the server in the meta-information, the access address of the micro-service can be determined. Therefore, the execution main body can enable the served object to establish a connection with the micro-service, so that the served object can access the micro-service in the server represented by the attribution information, and the access efficiency is improved.
In some optional implementations of this embodiment, for a case where the same micro service is deployed in multiple servers, the configuration meta information further includes traffic allocation information of the micro service for the multiple servers. The traffic allocation information can indicate the traffic proportion of the terminal device in each server. As an example, if a micro service is configured in 3 servers and the traffic allocation information in the configuration meta information of the micro service is 1:2:1, the actual access traffic ratio in the 3 servers of the plurality of terminal devices that finally access the micro service is approximately 1:2: 1. In this way, the flexibility of client-side based traffic distribution is further improved, and load balancing is better achieved.
In this embodiment, after the micro service is online, a configuration meta-information obtaining request may be sent to the execution main body to obtain configuration meta-information corresponding to the micro service. The execution main body responds to a received configuration meta-information acquisition request sent by the micro-service, and acquires configuration meta-information corresponding to the positioning identification information according to the positioning identification information of the micro-service.
In this embodiment, the execution subject may send the configuration meta information obtained in step 201 to a server for deploying the micro service, and establish a stable connection with the micro service based on the configuration meta information, so that a user having an authority to access the micro service accesses the micro service based on the configuration meta information.
The execution main body establishes stable connection with the micro-service based on the configuration meta-information, and is used for representing the micro-service to comply with the configuration of the micro-service according to the corresponding configuration meta-information. Taking the identity information of the user with the access micro-service authority in the configuration meta-information as an example, the micro-service obeys the setting of the configuration meta-information on the authority user, and can accept the access of the user with the access micro-service authority in the configuration meta-information.
Wherein the stable connection may be a stable connection within a preset time period. If there is a need to continue establishing a stable connection, the execution main body may continue to establish a stable connection in a next preset time period after the preset time period is ended.
As an example, the enforcement agent may employ a lease mechanism to establish a stable association with the microservice. In order to ensure high availability of the microservice in the distributed system, another microservice instance needs to be started in time to replace the failed service when the microservice fails. The health of the service process can be determined by a heartbeat connection between the microservice and the executing agent. However, due to the complexity of the actual network situation, when the execution main body cannot receive the heartbeat information, it cannot be accurately determined whether the micro service fails or the network between the micro service and the execution main body fails. To avoid the situation where the control center falsely enables a new microservice in such a situation could result in a "dual master", a lease mechanism may be employed. The micro-service continuously applies for a lease within a preset time period from the execution main body, and the execution main body cannot start new micro-service before the issued lease is expired; and when the lease of the micro service is expired, if the micro service cannot apply for a new lease from the execution main body, the link is interrupted.
In the embodiment, the micro-service of the server and the user of the served party can accurately establish an access relation based on the same configuration meta-information, so as to ensure that the user with the access micro-service authority directly and accurately accesses the micro-service.
With continuing reference to fig. 3, fig. 3 is a schematic diagram of an application scenario of the traffic scheduling method according to the present embodiment. In the application scenario of fig. 3, user 301, user 302, terminal device 303, terminal device 304, scheduling component 305, server 306, server 307, and server 308 are included. Wherein, different micro services are deployed in the server 306, the server 307 and the server 308. The user 301 needs to access the microservice through the terminal device 303. First, the scheduling component 305 obtains configuration meta-information of each micro-service in response to determining that the micro-service in each server is online, wherein the configuration meta-information is used for representing a user having a right to access the corresponding micro-service and an access policy for the micro-service. Then, the scheduling component 305 sends each piece of configuration meta-information to a server that deploys the corresponding microservice, and establishes a stable connection with the microservice corresponding to the configuration meta-information based on the configuration meta-information, so that a user having a right to access the microservice can access the microservice based on the configuration meta-information. Finally, it is determined that the user 301 accesses the micro-service in the server 306 through the terminal device 303, and the user 302 accesses the micro-service in the server 307 through the terminal device 304.
In the embodiment, based on the identity information of the user requesting access, the flow division and the service load balancing at the client side are realized based on the configuration meta information, so that the introduction of an additional gateway service node is avoided, and the service deployment and the service operation and maintenance are simplified.
In some optional implementations of this embodiment, the execution subject deletes the configuration meta-information of the microservice in response to determining that the microservice is offline.
In this embodiment, after the micro service is offline, the execution main body deletes the configuration meta information of the micro service to prevent the terminal device from invalid accessing the offline micro service, thereby improving the intelligence degree and the access effectiveness of this embodiment.
With continuing reference to fig. 4, an exemplary flow 400 of another embodiment of a traffic scheduling method according to the present application is shown, comprising the steps of:
In this embodiment, step 401 is substantially the same as step 201 in the corresponding embodiment of fig. 2, and is not described herein again.
In this embodiment, the execution main body of the traffic scheduling method may receive a modification instruction for the configuration meta-information of the microservice, and update the configuration meta-information according to an instruction of the modification instruction.
The modification instruction may be a modification instruction for modifying any information in the configuration meta-information, for example, the modification instruction may characterize a modification instruction for modifying identity information of a user having access to the micro-service in the configuration meta-information, attribution information of the micro-service for the server, and traffic allocation information of the micro-service for the plurality of servers.
As an example, the configuration meta-information may be configured and modified by acquiring the configuration meta-information and the modification instruction through a human-computer interaction platform that performs communication and interaction with the execution subject.
And step 403, sending the updated configuration meta-information to a server for deploying the micro-service, and reestablishing a stable connection with the micro-service based on the updated configuration meta-information.
In this embodiment, the execution main body may send the updated configuration meta-information to a server that deploys the microservice, and reestablish a stable connection with the microservice based on the updated configuration meta-information.
In this embodiment, as can be seen from fig. 4, compared with the embodiment corresponding to fig. 2, the flow 400 of the traffic scheduling method in this embodiment highlights the modification of the configuration meta-information and the reestablishment of the stable connection with the microservice based on the updated configuration meta-information. Therefore, the configuration meta-information of the microservice can be adjusted according to actual requirements, and the flexibility of flow configuration is improved.
With continuing reference to fig. 5, a flow 500 of one embodiment of a traffic scheduling method is shown, as applied to a client, comprising the steps of:
In this embodiment, an execution subject (for example, the terminal device in fig. 1) of the traffic scheduling method may obtain configuration meta information of the micro service in the scheduling component. The configuration meta-information is used for representing users having the right to access the micro-service and access strategies to the micro-service.
As an example, the execution subject and the scheduling component may perform information interaction, and obtain configuration meta-information of the micro-service based on identity information monitoring of the micro-service. In response to the update of the configuration meta-information, the execution subject may obtain the updated configuration meta-information. The configuration meta-information includes, but is not limited to, identity information of a user having access to the micro-service, home information of the micro-service for the server, and traffic distribution information of the micro-service for the plurality of servers.
In this embodiment, the execution subject determines an access request for characterizing access to the microservice according to the received user request and the configuration meta information, and accesses the microservice based on the access request.
In some optional implementations of this embodiment, the executing may execute step 502 by:
first, the execution agent determines identity information of a user corresponding to a user request.
When a user uses a terminal device to request to access the micro service, the identity information of the user can be obtained based on the user request.
Then, it is determined whether the user corresponding to the user request is a user having a right to access the microservice.
As an example, when the identity information of the user corresponding to the user request is included in the identity information of the user having the right to access the micro service, it is determined that the user corresponding to the user request is the user having the right to access the micro service; otherwise, it is determined that the user corresponding to the user request is not a user having rights to access the microservice.
And finally, in response to the fact that the user corresponding to the user request is determined to be the user with the access micro-service authority, determining the access request representing the server to which the user corresponding to the user request accesses the micro-service according to the identity information of the user corresponding to the user request and the attribution information of the micro-service for the server.
As an example, a served object of the microservice may be determined by identity information of the user corresponding to the user request; by configuring the attribution information of the micro-service to the server in the meta-information, the access address of the micro-service can be determined. In this way, the executing agent may determine an access request including the served object and the access address, so that the executing agent may access the microservice in the server characterized by the home information. Therefore, the execution main body as the served object directly establishes the relation with the micro-service, so that the served object accesses the micro-service in the server represented by the attribution information, and the access efficiency is improved.
In some optional implementation manners of this embodiment, specifically, for a case that the same micro service is deployed in multiple servers, the configuration meta information further includes traffic allocation information of the micro service for the multiple servers. The execution main body determines an access request which represents the user corresponding to the user request and accesses a target server in the plurality of servers to which the micro service belongs according to the identity information of the user corresponding to the user request, the attribution information of the micro service to the servers and the flow distribution information of the micro service to the plurality of servers. In this way, the flexibility of client-side based traffic distribution is further improved, and load balancing is better achieved.
In the embodiment, based on the identity information of the user requesting access, the flow division and the service load balancing at the client side are realized, the introduction of additional gateway service nodes is avoided, and the service deployment and the service operation and maintenance are simplified.
With continuing reference to fig. 6, a flow 600 of one embodiment of a traffic scheduling method is shown, applied to a server, comprising the steps of:
In this embodiment, the execution subject of the traffic scheduling method may obtain the configuration meta information of the deployed microservice. The configuration meta-information is used for representing users having the right to access the micro-service and access strategies to the micro-service.
As an example, after the micro service is deployed in the execution subject, a configuration meta-information obtaining request may be sent to the scheduling component to obtain the configuration meta-information of the deployed micro service from the scheduling component.
In this embodiment, the execution subject may establish a stable relationship with the scheduling component based on the configuration meta information. The terminal equipment which needs to access the micro-service in the execution main body determines an access request based on the same configuration meta-information as the accessed micro-service so as to directly access the micro-service.
In the embodiment, based on the identity information of the user requesting access, the flow division and the service load balancing at the client side are realized, the introduction of additional gateway service nodes is avoided, and the service deployment and the service operation and maintenance are simplified.
In some optional implementation manners of this embodiment, the execution main body may operate the micro service according to the access request in response to receiving the access request sent by the terminal device. Therefore, the execution main body can directly receive the access request of the user, and the access efficiency is improved.
With further reference to FIG. 7, a orchestration workflow 700 is shown for one embodiment of a traffic scheduling method applied to schedule groups, clients, and servers, respectively, comprising the steps of:
step 701, in response to the deployed microservice being online, the server sends a request for obtaining configuration meta-information of the microservice to the scheduling component.
Step 702, the scheduling component obtains the configuration meta-information according to the received configuration meta-information obtaining request, and sends the configuration meta-information to the server.
Step 703, based on the configuration meta-information, a stable association is established between the scheduling component and the server.
In step 704, the client obtains configuration meta-information for the microservice in the scheduling component.
Step 705, the client determines to access the request for the microservice according to the configuration meta-information.
At step 706, the client sends an access request to a server deploying the microservice.
In the embodiment, the flow scheduling methods respectively applied to the scheduling groups, the client and the server are coordinated and matched, based on the identity information of the user requesting access, flow division and service load balancing at the client side are realized, additional gateway service nodes are avoided, and service deployment and service operation and maintenance are simplified.
With further reference to fig. 8, as an implementation of the method shown in fig. 2-4, the present disclosure provides an embodiment of a traffic scheduling apparatus, which corresponds to the embodiment of the method shown in fig. 2, and which may include the same or corresponding features as the embodiment of the method shown in fig. 2 and produce the same or corresponding effects as the embodiment of the method shown in fig. 2, in addition to the features described below. The device can be applied to various electronic equipment.
As shown in fig. 8, the traffic scheduling apparatus of this embodiment, applied to a scheduling component, includes: a first obtaining unit 801 configured to, in response to determining that the micro service is online, obtain configuration meta information of the micro service, where the configuration meta information is used to characterize a user having a right to access the micro service, and an access policy to the micro service; the first contact unit 802 is configured to send the configuration meta-information to a server deploying the micro-service, and establish a stable contact with the micro-service based on the configuration meta-information, so that a user having a right to access the micro-service can access the micro-service based on the configuration meta-information.
In some embodiments, the configuration meta-information includes identity information of a user having access to the micro-service, and attribution information of the micro-service to the server.
In some embodiments, the microservice is deployed in a plurality of servers, and the configuration meta-information further includes traffic allocation information for the microservice for the plurality of servers.
In some embodiments, the first obtaining unit 801 is further configured to: and responding to a configuration meta-information acquisition request sent after the micro-service is online, and acquiring configuration meta-information corresponding to the positioning identification information according to the positioning identification information of the micro-service.
In some embodiments, the above apparatus further comprises: a modification unit (not shown in the figure) configured to, in response to receiving a modification instruction for the configuration meta-information of the microservice, update the configuration meta-information according to an indication of the modification instruction; and a first contacting unit 801, further configured to: and sending the updated configuration meta-information to a server for deploying the micro-service, and reestablishing a stable connection with the micro-service based on the updated configuration meta-information.
In some embodiments, the above apparatus further comprises: a deletion unit (not shown in the figure) configured to delete the configuration meta-information of the micro-service in response to determining that the micro-service is offline.
With further reference to fig. 9, as an implementation of the method shown in fig. 5, the present disclosure provides an embodiment of a traffic scheduling apparatus, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 5, and besides the features described below, the embodiment of the apparatus may further include the same or corresponding features as the embodiment of the method shown in fig. 5, and produce the same or corresponding effects as the embodiment of the method shown in fig. 5. The device can be applied to various terminal equipment.
As shown in fig. 9, the traffic scheduling apparatus of the present embodiment, applied to a client, includes: a second obtaining unit 901, configured to obtain configuration meta-information of the micro-service in the scheduling component, where the configuration meta-information is used to characterize a user having a right to access the micro-service and an access policy to the micro-service; an accessing unit 902 configured to determine an access request for characterizing access to the microservice according to the received user request and the configuration meta-information, and access the microservice based on the access request.
In some embodiments, the configuration meta-information includes identity information of a user having access to the micro-service, attribution information of the micro-service to the server; an access unit 902, further configured to: determining identity information of a user corresponding to the user request; determining whether a user corresponding to the user request is a user having a right to access the microservice; and in response to determining that the user corresponding to the user request is a user with access micro-service authority, determining an access request for characterizing the server to which the user corresponding to the user request accesses the micro-service according to the identity information of the user corresponding to the user request and the attribution information of the micro-service for the server.
In some embodiments, the microservice is deployed in a plurality of servers, the configuration meta-information further includes traffic allocation information for the microservice for the plurality of servers; an access unit 902, further configured to: and determining an access request which characterizes the user corresponding to the user request and accesses a target server in the plurality of servers to which the micro service belongs according to the identity information of the user corresponding to the user request, the attribution information of the micro service to the servers and the flow distribution information of the micro service to the plurality of servers.
With further reference to fig. 10, as an implementation of the method shown in fig. 6, the present disclosure provides an embodiment of a traffic scheduling apparatus, which corresponds to the embodiment of the method shown in fig. 6, and which may include the same or corresponding features as the embodiment of the method shown in fig. 6 and produce the same or corresponding effects as the embodiment of the method shown in fig. 6, in addition to the features described below. The device can be applied to various terminal equipment.
As shown in fig. 10, the traffic scheduling apparatus of this embodiment, applied to a server, includes: a third obtaining unit 1001 configured to obtain configuration meta-information of the deployed microservice, where the configuration meta-information is used to characterize a user having a right to access the microservice and an access policy for the microservice; a second contact unit 1002 configured to establish a stable contact with the scheduling component based on the configuration meta-information for a user having a right to access the microservice based on the configuration meta-information.
In some embodiments, the above apparatus further comprises: and the operation unit (not shown in the figure) is configured to respond to the received access request sent by the terminal equipment and operate the micro service according to the access request.
The flow scheduling device respectively applied to the scheduling component, the client and the server realizes flow division and service load balancing at the client side on the basis of the identity information of the user requesting access, avoids introducing extra gateway service nodes, and simplifies service deployment and service operation and maintenance.
According to an embodiment of the present application, an electronic device and a readable storage medium are also provided.
Fig. 11 is a block diagram of an electronic device according to an embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.
As shown in fig. 11, the electronic apparatus includes: one or more processors 1101, a memory 1102, and interfaces for connecting the various components, including a high speed interface and a low speed interface. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions for execution within the electronic device, including instructions stored in or on the memory to display graphical information of a GUI on an external input/output apparatus (such as a display device coupled to the interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple electronic devices may be connected, with each device providing portions of the necessary operations (e.g., as a server array, a group of blade servers, or a multi-processor system). In fig. 11, a processor 1101 is taken as an example.
The memory 1102 is a non-transitory computer readable storage medium as provided herein. The memory stores instructions executable by at least one processor to cause the at least one processor to perform the traffic scheduling method provided by the present application. A non-transitory computer readable storage medium of the present application stores computer instructions for causing a computer to perform the traffic scheduling method provided herein.
The memory 1102, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the traffic scheduling method in the embodiments of the present application (for example, the first obtaining unit 801, the first linking unit 802, the second obtaining unit 901, the accessing unit 902, the third obtaining unit 1001, and the second linking unit 1002 shown in fig. 8 to 10). The processor 1101 executes various functional applications of the server and data processing by running non-transitory software programs, instructions and modules stored in the memory 1102, that is, implements the traffic scheduling method in the above method embodiment.
The memory 1102 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the traffic scheduling electronic device, and the like. Further, the memory 1102 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 1102 may optionally include memory located remotely from the processor 1101, which may be connected to traffic scheduling electronics over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The electronic device of the traffic scheduling method may further include: an input device 1103 and an output device 1104. The processor 1101, the memory 1102, the input device 1103 and the output device 1104 may be connected by a bus or other means, and are exemplified by being connected by a bus in fig. 11.
The input device 1103 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the flow scheduling electronics, such as a touch screen, keypad, mouse, track pad, touch pad, pointer, one or more mouse buttons, track ball, joystick, or other input device. The output devices 1104 may include a display device, auxiliary lighting devices (e.g., LEDs), tactile feedback devices (e.g., vibrating motors), and the like. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device can be a touch screen.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
These computer programs (also known as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
According to the technical scheme of the embodiment of the application, based on the identity information of the user requesting access, the flow division and the service load balance at the client side are realized, the introduction of additional gateway service nodes is avoided, and the service deployment and the service operation and maintenance are simplified.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, and the present invention is not limited thereto as long as the desired results of the technical solutions disclosed in the present application can be achieved.
The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (24)
1. A traffic scheduling method is applied to a scheduling component and comprises the following steps:
in response to the fact that the micro service is determined to be on line, obtaining configuration meta-information of the micro service, wherein the configuration meta-information is used for representing a user with the authority of accessing the micro service and an access strategy of the user to the micro service;
and sending the configuration meta-information to a server for deploying the micro-service, establishing a stable relation with the micro-service based on the configuration meta-information, so that a user with the permission to access the micro-service can access the micro-service based on the configuration meta-information.
2. The method of claim 1, wherein the configuration meta information comprises identity information of a user having a right to access the micro service, and attribution information of the micro service to a server.
3. The method of claim 2, wherein the microservice is deployed in a plurality of servers, the configuration meta-information further comprising traffic allocation information for the microservice for the plurality of servers.
4. The method of claim 1, wherein said obtaining configuration meta-information for a microservice in response to determining that the microservice is online comprises:
and responding to a configuration meta-information acquisition request sent after the micro-service is received to be on-line, and acquiring the configuration meta-information corresponding to the positioning identification information according to the positioning identification information of the micro-service.
5. The method of claim 1, wherein the method further comprises:
in response to receiving a modification instruction for configuration meta-information of the microservice, updating the configuration meta-information according to an indication of the modification instruction; and
the sending the configuration meta-information to a server deploying the micro-service and establishing a stable connection with the micro-service based on the configuration meta-information includes:
and sending the updated configuration meta-information to a server for deploying the micro-service, and reestablishing a stable connection with the micro-service based on the updated configuration meta-information.
6. The method of claim 1, wherein the method further comprises:
in response to determining that the microservice is offline, deleting configuration meta-information of the microservice.
7. A traffic scheduling method is applied to a client and comprises the following steps:
acquiring configuration meta-information of the micro-service in a scheduling component, wherein the configuration meta-information is used for representing a user with the authority of accessing the micro-service and an access strategy of the micro-service;
and according to the received user request and the configuration meta-information, determining an access request for characterizing the access to the micro-service, and accessing the micro-service based on the access request.
8. The method of claim 7, wherein the configuration meta information includes identity information of a user having a right to access the micro service, home information of the micro service for a server;
determining, according to the received user request and the configuration meta information, an access request characterizing access to the microservice, including:
determining identity information of a user corresponding to the user request;
determining whether a user corresponding to the user request is a user having a right to access the microservice;
in response to determining that the user corresponding to the user request is a user with the authority to access the micro service, determining an access request for characterizing that the user corresponding to the user request accesses the server to which the micro service belongs according to the identity information of the user corresponding to the user request and the attribution information of the micro service for the server.
9. The method of claim 8, wherein the microservice is deployed in a plurality of servers, the configuration meta-information further comprising traffic allocation information for the microservice for the plurality of servers;
the determining, according to the identity information of the user corresponding to the user request and the attribution information of the micro service to the server, an access request characterizing that the user corresponding to the user request accesses the server to which the micro service belongs includes:
and determining an access request which characterizes the user corresponding to the user request and accesses a target server in the plurality of servers to which the micro service belongs according to the identity information of the user corresponding to the user request, the attribution information of the micro service to the servers and the flow distribution information of the micro service to the plurality of servers.
10. A traffic scheduling method is applied to a server and comprises the following steps:
acquiring configuration meta-information of the deployed micro-service, wherein the configuration meta-information is used for representing a user with the authority of accessing the micro-service and an access strategy of the micro-service;
and establishing a stable relation with a scheduling component based on the configuration meta-information so as to provide the user with the authority of accessing the micro-service, and accessing the micro-service based on the configuration meta-information.
11. The method of claim 10, wherein the method further comprises:
and responding to an access request sent by the terminal equipment, and operating the micro service according to the access request.
12. A traffic scheduling device is applied to a scheduling component and comprises:
the micro service management system comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring configuration meta-information of a micro service in response to the fact that the micro service is determined to be on line, the configuration meta-information is used for representing a user with the authority of accessing the micro service, and the access policy of the micro service is obtained;
the first contact unit is configured to send the configuration meta-information to a server deploying the micro-service, and establish a stable contact with the micro-service based on the configuration meta-information, so that a user having the authority to access the micro-service can access the micro-service based on the configuration meta-information.
13. The apparatus of claim 12, wherein the configuration meta information comprises identity information of a user having a right to access the micro service, and attribution information of the micro service to a server.
14. The apparatus of claim 13, wherein the microservice is deployed in a plurality of servers, the configuration meta-information further comprising traffic allocation information for the microservice for the plurality of servers.
15. The apparatus of claim 12, wherein the first obtaining unit is further configured to: and responding to a configuration meta-information acquisition request sent after the micro-service is received to be on-line, and acquiring the configuration meta-information corresponding to the positioning identification information according to the positioning identification information of the micro-service.
16. The apparatus of claim 12, wherein the apparatus further comprises:
a modification unit configured to update configuration meta-information of the microservice according to an indication of a modification instruction in response to receiving the modification instruction; and
the first contact unit is further configured to: and sending the updated configuration meta-information to a server for deploying the micro-service, and reestablishing a stable connection with the micro-service based on the updated configuration meta-information.
17. The apparatus of claim 12, wherein the apparatus further comprises:
a deletion unit configured to delete the configuration meta-information of the micro-service in response to determining that the micro-service is offline.
18. A traffic scheduling device applied to a client comprises:
the second acquisition unit is configured to acquire configuration meta-information of the micro-service in the scheduling component, wherein the configuration meta-information is used for representing a user with the authority of accessing the micro-service and an access policy of the micro-service;
an access unit configured to determine an access request for characterizing access to the microservice according to the received user request and the configuration meta-information, and access the microservice based on the access request.
19. The apparatus of claim 18, wherein the configuration meta information includes identity information of a user having a right to access the micro service, home information of the micro service for a server;
the access unit, further configured to:
determining identity information of a user corresponding to the user request; determining whether a user corresponding to the user request is a user having a right to access the microservice; in response to determining that the user corresponding to the user request is a user with the authority to access the micro service, determining an access request for characterizing that the user corresponding to the user request accesses the server to which the micro service belongs according to the identity information of the user corresponding to the user request and the attribution information of the micro service for the server.
20. The apparatus of claim 19, wherein the microservice is deployed in a plurality of servers, the configuration meta-information further comprising traffic allocation information for the microservice for the plurality of servers;
the access unit, further configured to: and determining an access request which characterizes the user corresponding to the user request and accesses a target server in the plurality of servers to which the micro service belongs according to the identity information of the user corresponding to the user request, the attribution information of the micro service to the servers and the flow distribution information of the micro service to the plurality of servers.
21. A traffic scheduling device applied to a server comprises:
a third obtaining unit, configured to obtain configuration meta-information of the deployed micro-service, wherein the configuration meta-information is used to characterize a user having a right to access the micro-service and an access policy to the micro-service;
a second contact unit configured to establish a stable contact with a scheduling component based on the configuration meta-information for a user having a right to access the micro-service based on the configuration meta-information.
22. The apparatus of claim 21, wherein the apparatus further comprises:
the operation unit is configured to respond to the received access request sent by the terminal equipment and operate the micro service according to the access request.
23. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-11.
24. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010605250.3A CN111770176B (en) | 2020-06-29 | 2020-06-29 | Traffic scheduling method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010605250.3A CN111770176B (en) | 2020-06-29 | 2020-06-29 | Traffic scheduling method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111770176A true CN111770176A (en) | 2020-10-13 |
| CN111770176B CN111770176B (en) | 2023-04-07 |
Family
ID=72723193
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010605250.3A Active CN111770176B (en) | 2020-06-29 | 2020-06-29 | Traffic scheduling method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111770176B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112910796A (en) * | 2021-01-27 | 2021-06-04 | 北京百度网讯科技有限公司 | Traffic management method, apparatus, device, storage medium, and program product |
| CN113746933A (en) * | 2021-09-14 | 2021-12-03 | 京东科技信息技术有限公司 | Method and device for displaying information |
| CN115134227A (en) * | 2022-06-17 | 2022-09-30 | 京东科技信息技术有限公司 | Method and apparatus for maintaining server |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180113790A1 (en) * | 2016-10-20 | 2018-04-26 | Cisco Technology, Inc. | Agentless distributed monitoring of microservices through a virtual switch |
| CN108809956A (en) * | 2018-05-23 | 2018-11-13 | 广州虎牙信息科技有限公司 | Method for authenticating, access request retransmission method based on micro services and device, system |
| CN109618002A (en) * | 2019-01-11 | 2019-04-12 | 武汉斗鱼鱼乐网络科技有限公司 | A kind of micro services gateway optimization method, device and storage medium |
| CN109688191A (en) * | 2018-10-24 | 2019-04-26 | 华为技术有限公司 | Traffic scheduling method and communication device |
| CN109818902A (en) * | 2017-11-21 | 2019-05-28 | 中国电信股份有限公司 | Automatic service deployment method, service dispatch management module and EPG platform |
| CN110944067A (en) * | 2019-12-27 | 2020-03-31 | 华为技术有限公司 | Load balancing method and server |
| CN110995511A (en) * | 2019-12-24 | 2020-04-10 | 邱瀚 | Cloud computing operation and maintenance management method and device based on micro-service architecture and terminal equipment |
| CN111124670A (en) * | 2019-12-05 | 2020-05-08 | 航天科工网络信息发展有限公司 | Tactical cloud-oriented micro-service platform |
| US20200162578A1 (en) * | 2018-11-19 | 2020-05-21 | International Business Machines Corporation | Microservices request flow control synchronization |
-
2020
- 2020-06-29 CN CN202010605250.3A patent/CN111770176B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180113790A1 (en) * | 2016-10-20 | 2018-04-26 | Cisco Technology, Inc. | Agentless distributed monitoring of microservices through a virtual switch |
| CN109818902A (en) * | 2017-11-21 | 2019-05-28 | 中国电信股份有限公司 | Automatic service deployment method, service dispatch management module and EPG platform |
| CN108809956A (en) * | 2018-05-23 | 2018-11-13 | 广州虎牙信息科技有限公司 | Method for authenticating, access request retransmission method based on micro services and device, system |
| CN109688191A (en) * | 2018-10-24 | 2019-04-26 | 华为技术有限公司 | Traffic scheduling method and communication device |
| US20200162578A1 (en) * | 2018-11-19 | 2020-05-21 | International Business Machines Corporation | Microservices request flow control synchronization |
| CN109618002A (en) * | 2019-01-11 | 2019-04-12 | 武汉斗鱼鱼乐网络科技有限公司 | A kind of micro services gateway optimization method, device and storage medium |
| CN111124670A (en) * | 2019-12-05 | 2020-05-08 | 航天科工网络信息发展有限公司 | Tactical cloud-oriented micro-service platform |
| CN110995511A (en) * | 2019-12-24 | 2020-04-10 | 邱瀚 | Cloud computing operation and maintenance management method and device based on micro-service architecture and terminal equipment |
| CN110944067A (en) * | 2019-12-27 | 2020-03-31 | 华为技术有限公司 | Load balancing method and server |
Non-Patent Citations (4)
| Title |
|---|
| ZENG JZ: "Service unit based network architecture and its micro-communication element system" * |
| 张晶;黄小锋;李春阳;: "微服务框架的设计与实现" * |
| 王亚军;: "微服务架构在容器中的应用实践" * |
| 罗光峰;陈慧光;徐洪磊;: "面向新架构的流量调度系统研究与设计" * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112910796A (en) * | 2021-01-27 | 2021-06-04 | 北京百度网讯科技有限公司 | Traffic management method, apparatus, device, storage medium, and program product |
| CN112910796B (en) * | 2021-01-27 | 2022-12-16 | 北京百度网讯科技有限公司 | Traffic management method, apparatus, device, storage medium, and program product |
| CN113746933A (en) * | 2021-09-14 | 2021-12-03 | 京东科技信息技术有限公司 | Method and device for displaying information |
| CN115134227A (en) * | 2022-06-17 | 2022-09-30 | 京东科技信息技术有限公司 | Method and apparatus for maintaining server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111770176B (en) | 2023-04-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111741026B (en) | Cross-chain transaction request processing method, device, equipment and storage medium | |
| CN111770176B (en) | Traffic scheduling method and device | |
| CN113742031B (en) | Node state information acquisition method and device, electronic equipment and readable storage medium | |
| CN110765024A (en) | Simulation test method, simulation test device, electronic equipment and computer-readable storage medium | |
| CN113783922A (en) | Load balancing method, system and device | |
| CN112437006B (en) | Request control method and device based on API gateway, electronic equipment and storage medium | |
| CN111510480B (en) | Request sending method and device and first server | |
| CN112771928B (en) | Method and device for determining satellite return information | |
| CN108023953A (en) | The high availability implementation method and device of FTP service | |
| CN111277647A (en) | Block chain network member management method, device, equipment and medium | |
| CN109828830B (en) | Method and apparatus for managing containers | |
| US20240313851A1 (en) | Method and device for determining satellite link information | |
| CN110659184B (en) | Health state checking method, device and system | |
| CN111966502B (en) | Method, apparatus, electronic device and readable storage medium for adjusting instance number | |
| US11831735B2 (en) | Method and device for processing mini program data | |
| EP3457668B1 (en) | Clustering in unified communication and collaboration services | |
| CN111683139A (en) | Method and apparatus for balancing load | |
| CN108958933B (en) | Configuration parameter updating method, device and equipment of task executor | |
| CN112565225B (en) | Method and device for data transmission, electronic equipment and readable storage medium | |
| CN112069137B (en) | Method, device, electronic equipment and computer readable storage medium for generating information | |
| CN111767149A (en) | Scheduling method, device, equipment and storage equipment | |
| US11381665B2 (en) | Tracking client sessions in publish and subscribe systems using a shared repository | |
| CN111090783A (en) | Recommendation method, device and system, graph-embedded wandering method and electronic equipment | |
| CN114661274A (en) | Method and device for generating intelligent contract | |
| CN114070889A (en) | Configuration method, traffic forwarding method, device, storage medium, and program product |
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 |