CN106533805B - Micro-service request processing method, micro-service controller and micro-service architecture - Google Patents
Micro-service request processing method, micro-service controller and micro-service architecture Download PDFInfo
- Publication number
- CN106533805B CN106533805B CN201611206619.3A CN201611206619A CN106533805B CN 106533805 B CN106533805 B CN 106533805B CN 201611206619 A CN201611206619 A CN 201611206619A CN 106533805 B CN106533805 B CN 106533805B
- Authority
- CN
- China
- Prior art keywords
- micro
- service
- micro service
- request
- microservice
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/16—Threshold monitoring
-
- 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/133—Protocols for remote procedure calls [RPC]
Abstract
The invention discloses a micro-service request processing method, which comprises the following steps: receiving a micro-service request sent by a user; sending the micro-service request to a micro-service message queue; sending a success response message to the user; therefore, in the scheme, when the micro-service controller receives a micro-service request sent by a user, the micro-service controller directly sends the micro-service request to the micro-service queue so that the micro-service queue processes the micro-service request through an asynchronous calling mechanism and directly replies successful response information to the user, so that the successful response information can be automatically sent to the user when the request cannot be successfully processed by a certain micro-service, the system can automatically remove the micro-service with faults, the safety of a micro-service framework is improved, and the user experience is improved; the invention also discloses a micro-service controller and a micro-service architecture, which can also realize the technical effects.
Description
Technical Field
The present invention relates to the field of micro service architecture, and more particularly, to a micro service request processing method, a micro service controller, and a micro service architecture.
Background
Microservice is an emerging software architecture that splits a large single application and service into tens of supporting microservices. A microservice policy may facilitate work by extending individual components rather than the entire application stack to meet service level agreements. At present, with the development of micro-service architectures and more enterprise applications, after a single architecture with centralized functions and running in the same application is split into a plurality of mutually independent micro-service architectures, although the global failure risk of loss can be reduced, because a large number of dependency relationships exist among micro-services, each micro-service may fail, and if a certain micro-service fails, the request of the micro-service cannot be processed all the time, so that the request is blocked, and the user cannot receive response information, so that the user experience is reduced. Therefore, how to ensure that the system automatically removes the failed microservices and improve the user experience is a problem to be solved by the technical personnel in the field.
Disclosure of Invention
The invention aims to provide a micro-service request processing method, a micro-service controller and a micro-service architecture, so as to ensure that a system automatically eliminates a micro-service with a fault, improve the safety of the micro-service architecture and improve the user experience.
In order to achieve the above purpose, the embodiment of the present invention provides the following technical solutions:
a micro-service request processing method comprises the following steps:
receiving a micro-service request sent by a user;
sending the micro-service request to a micro-service message queue;
and sending success response information to the user.
Wherein after sending the microservice request to a microservice message queue, the method further comprises:
judging whether the micro service corresponding to the micro service request is a critical micro service;
if not, executing the step of sending the successful response information to the user.
Before receiving a micro-service request sent by a user, the method further includes:
detecting whether each micro service meets a preset fault condition in real time, and taking the micro service meeting the fault condition as a fault micro service;
after sending the microservice request to a microservice message queue, the method further includes:
judging whether the micro service corresponding to the micro service request is a fault micro service; and if so, executing the step of sending the successful response information to the user.
The method comprises the following steps of detecting whether each micro service meets a preset fault condition in real time, and taking the micro service meeting the fault condition as a fault micro service, wherein the step of detecting whether each micro service meets the preset fault condition in real time comprises the following steps:
detecting whether the request duration of each micro-service request is greater than a preset duration threshold or not in real time;
and if so, taking the micro service with the request duration being greater than the preset threshold value as the fault micro service.
The method comprises the following steps of detecting whether each micro service meets a preset fault condition in real time, and taking the micro service meeting the fault condition as a fault micro service, wherein the step of detecting whether each micro service meets the preset fault condition in real time comprises the following steps:
detecting whether micro-services with service failure times larger than a preset time threshold exist in real time;
and if so, taking the micro service with the service failure times larger than a preset time threshold value as the fault micro service.
The method comprises the following steps of detecting whether each micro service meets a preset fault condition in real time, and taking the micro service meeting the fault condition as a fault micro service, wherein the step of detecting whether each micro service meets the preset fault condition in real time comprises the following steps:
detecting whether available nodes exist in each microservice in real time;
and taking the micro service without the available node as the fault micro service.
A microservice controller comprising:
the receiving module is used for receiving a micro-service request sent by a user;
the micro-service request sending module is used for sending the micro-service request to a micro-service message queue;
and the response information sending module is used for sending successful response information to the user.
Wherein, still include:
the first judgment module is used for judging whether the micro service corresponding to the micro service request is a key micro service after the micro service request is sent to a micro service message queue;
and the response information sending module is used for sending successful response information to the user when the micro service corresponding to the micro service request is not a critical micro service.
Wherein, still include:
the detection module is used for detecting whether each micro service meets a preset fault condition in real time before receiving a micro service request sent by a user, and taking the micro service meeting the fault condition as a fault micro service;
the second judgment module is used for judging whether the micro service corresponding to the micro service request is a fault micro service after the micro service request is sent to a micro service message queue;
and the response information sending module is used for sending successful response information to the user when the micro service corresponding to the micro service request is the fault micro service.
A micro-service architecture comprises any micro-service controller.
According to the above scheme, the method for processing the micro-service request provided by the embodiment of the invention comprises the following steps: receiving a micro-service request sent by a user; sending the micro-service request to a micro-service message queue; sending a success response message to the user; therefore, in the scheme, when the micro-service controller receives a micro-service request sent by a user, the micro-service controller directly sends the micro-service request to the micro-service queue so that the micro-service queue processes the micro-service request through an asynchronous calling mechanism and directly replies successful response information to the user, so that the successful response information can be automatically sent to the user when the request cannot be successfully processed by a certain micro-service, the system can automatically remove the micro-service with faults, the safety of a micro-service framework is improved, and the user experience is improved; the invention also discloses a micro-service controller and a micro-service architecture, which can also realize the technical effects.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flow chart illustrating a method for processing a microservice request according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a micro service architecture according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a micro service controller according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The embodiment of the invention discloses a micro-service request processing method, a micro-service controller and a micro-service architecture, which are used for ensuring that a system automatically eliminates a micro-service with a fault, improving the safety of the micro-service architecture and improving the user experience.
Referring to fig. 1, a method for processing a microservice request provided by an embodiment of the present invention includes:
s101, receiving a micro-service request sent by a user;
s102, sending the micro-service request to a micro-service message queue;
specifically, in the scheme, after a micro-service request sent by a user is received, the request is sent to a micro-service message queue, and the request is processed by adopting an asynchronous calling mechanism through the message queue, so that the micro-service request is prevented from being blocked.
S103, sending success response information to the user.
Specifically, for the micro-Service architecture, a User sends a large number of micro-Service request User requests to access a Service, the Service depends on the cooperation completion of 4 micro-services, request information is sent to a message queue through a micro-Service controller Service, referring to fig. 2, it is assumed that a Service b fails, and the Service b is not critical, and operation failure can also continue, for example, User registration needs to call a Service to send a mail with successful registration to the User, if the Service of sending the mail is unavailable, but User registration is not affected, so User registration is successful, the mail can be sent again after Service recovery, only time delay, therefore, in the scheme, after the micro-Service request is sent to the message queue, a successful response message is directly sent to the User, so that the system automatically eliminates the failed micro-Service, and improves the security of the micro-Service architecture, the user experience is improved.
Based on the foregoing embodiment, in this embodiment, after the sending the microservice request to the microservice message queue, the method further includes:
judging whether the micro service corresponding to the micro service request is a critical micro service;
if not, executing the step of sending the successful response information to the user.
Specifically, in this embodiment, before sending the successful response information to the user, it may be determined whether the micro service corresponding to the access request sent by the user is a critical micro service, and if not, a successful response is sent. It should be noted that there may be a plurality of micro services corresponding to the access request, and if there is a critical micro service in the plurality of micro services, it is important to represent the access request, so that the user may not directly send a successful response message to the user, and may send a successful response message after all the requests are executed, thereby improving user experience.
Based on the foregoing embodiment, in this embodiment, before receiving the micro-service request sent by the user, the method further includes:
detecting whether each micro service meets a preset fault condition in real time, and taking the micro service meeting the fault condition as a fault micro service;
after sending the microservice request to a microservice message queue, the method further includes:
judging whether the micro service corresponding to the micro service request is a fault micro service; and if so, executing the step of sending the successful response information to the user.
Specifically, in this embodiment, before sending the successful response information to the user, the micro service controller may detect whether there is a failed micro service in real time, and mark the failed micro service as a failed micro service; if receiving the micro service request sent by the user, the method can check whether the micro service with faults exists in the request, if so, the method can directly execute the step of sending the successful response information to the user, and if not, the method can wait for successfully responding the request and then send the successful response information, thereby improving the user experience.
The method comprises the following steps of detecting whether each micro service meets a preset fault condition in real time, and taking the micro service meeting the fault condition as a fault micro service, wherein the step of detecting whether each micro service meets the preset fault condition in real time comprises the following steps:
detecting whether the request duration of each micro-service request is greater than a preset duration threshold or not in real time;
and if so, taking the micro service with the request duration being greater than the preset threshold value as the fault micro service.
Specifically, in this embodiment, when determining a faulty microservice, if the access duration of a certain access request is greater than a predetermined threshold, it indicates that the corresponding microservice has a fault when responding to the access request, and therefore in this embodiment, when it is detected that the request duration of the access request is greater than the predetermined duration threshold, it is determined that the microservice corresponding to the access request is the faulty microservice.
It should be noted that the request duration of the access request in this embodiment may be the request duration of accessing a certain microservice, for example: when the access request accesses the micro service A, timing is started through a timer, if the timing duration is greater than a preset duration threshold, the micro service A is judged to have a fault, and therefore the micro service A is used as a fault micro service; the request duration of the access request in this embodiment may also be the request duration of the access that has already ended, for example: and when the access request accesses the micro service B, timing the access from the beginning to the end of the access, and if the access time length is greater than a preset time length threshold value, taking the micro service B as a fault micro service. However, in order to avoid the timeout condition of a micro service due to non-failure reasons, the number of times of timeout of each micro service may be counted, and when the counted number is greater than the number threshold, the micro service is regarded as a failed micro service.
The method comprises the following steps of detecting whether each micro service meets a preset fault condition in real time, and taking the micro service meeting the fault condition as a fault micro service, wherein the step of detecting whether each micro service meets the preset fault condition in real time comprises the following steps:
detecting whether micro-services with service failure times larger than a preset time threshold exist in real time;
and if so, taking the micro service with the service failure times larger than a preset time threshold value as the fault micro service.
Specifically, the service failure times in this embodiment may be failure times of a certain micro service within a predetermined time, or failure times of the same access request accessing the same micro service, which is not limited herein; when the accumulated service failure times of a micro service are more than the preset time threshold value, the probability of successfully processing the access request on the basis of the micro service becomes low, and the micro service is likely to have a fault, so that the micro service with the service failure times more than the preset time threshold value is taken as the fault micro service.
The method comprises the following steps of detecting whether each micro service meets a preset fault condition in real time, and taking the micro service meeting the fault condition as a fault micro service, wherein the step of detecting whether each micro service meets the preset fault condition in real time comprises the following steps:
detecting whether available nodes exist in each microservice in real time;
and taking the micro service without the available node as the fault micro service.
Specifically, in this embodiment, each microservice may have a plurality of nodes, and if there is no available node in the microservice, it represents that the microservice has no capability to respond to the access request. It should be noted that, in the above embodiment, three methods for determining the faulty microservice are provided, that is: the micro service controller may perform the three determination methods at the same time, or may perform any one or both of them, by determining the access duration, the service failure number, and the number of available nodes, which is not specifically limited herein.
In the following, the micro service controller provided in the embodiment of the present invention is introduced, and the micro service controller described below and the micro service request processing method described above may be referred to each other.
Referring to fig. 3, an embodiment of the present invention provides a micro service controller, including:
a receiving module 100, configured to receive a micro service request sent by a user;
a micro service request sending module 200, configured to send the micro service request to a micro service message queue;
a response message sending module 300, configured to send a successful response message to the user.
Based on the above embodiment, this embodiment further includes:
the first judgment module is used for judging whether the micro service corresponding to the micro service request is a key micro service after the micro service request is sent to a micro service message queue;
and the response information sending module is used for sending successful response information to the user when the micro service corresponding to the micro service request is not a critical micro service.
Based on the above embodiment, this embodiment further includes:
the detection module is used for detecting whether each micro service meets a preset fault condition in real time before receiving a micro service request sent by a user, and taking the micro service meeting the fault condition as a fault micro service;
the second judgment module is used for judging whether the micro service corresponding to the micro service request is a fault micro service after the micro service request is sent to a micro service message queue;
and the response information sending module is used for sending successful response information to the user when the micro service corresponding to the micro service request is the fault micro service.
An embodiment of the present invention provides a micro service architecture, including the micro service controller described in any of the above embodiments.
The method for processing the micro-service request provided by the embodiment of the invention comprises the following steps: receiving a micro-service request sent by a user; sending the micro-service request to a micro-service message queue; sending a success response message to the user; therefore, in the scheme, when the micro-service controller receives a micro-service request sent by a user, the micro-service controller directly sends the micro-service request to the micro-service queue so that the micro-service queue processes the micro-service request through an asynchronous calling mechanism and directly replies successful response information to the user, so that the successful response information can be automatically sent to the user when the request cannot be successfully processed by a certain micro-service, the system can automatically remove the micro-service with faults, the safety of a micro-service framework is improved, and the user experience is improved; the invention also discloses a micro-service controller and a micro-service architecture, which can also realize the technical effects.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (6)
1. A method for processing microservice requests, comprising:
receiving a micro-service request sent by a user;
sending the micro-service request to a micro-service message queue;
sending a success response message to the user;
wherein after sending the microservice request to a microservice message queue, the method further comprises:
judging whether the micro service corresponding to the micro service request is a critical micro service;
if not, executing the step of sending the successful response information to the user; if yes, sending a successful response message after the request is completely executed;
before receiving a micro-service request sent by a user, the method further includes:
detecting whether each micro service meets a preset fault condition in real time, and taking the micro service meeting the fault condition as a fault micro service;
after sending the microservice request to a microservice message queue, the method further includes:
judging whether the micro service corresponding to the micro service request is a fault micro service; and if so, executing the step of sending the successful response information to the user.
2. The method for processing the microservice request according to claim 1, wherein the real-time detection of whether each microservice satisfies a preset fault condition, and the step of using the microservice satisfying the fault condition as the fault microservice comprises:
detecting whether the request duration of each micro-service request is greater than a preset duration threshold or not in real time;
and if so, taking the micro service with the request duration being greater than the preset threshold value as the fault micro service.
3. The method for processing the microservice request according to claim 1, wherein the real-time detection of whether each microservice satisfies a preset fault condition, and the step of using the microservice satisfying the fault condition as the fault microservice comprises:
detecting whether micro-services with service failure times larger than a preset time threshold exist in real time;
and if so, taking the micro service with the service failure times larger than a preset time threshold value as the fault micro service.
4. The method for processing the microservice request according to claim 1, wherein the real-time detection of whether each microservice satisfies a preset fault condition, and the step of using the microservice satisfying the fault condition as the fault microservice comprises:
detecting whether available nodes exist in each microservice in real time;
and taking the micro service without the available node as the fault micro service.
5. A microservice controller, comprising:
the receiving module is used for receiving a micro-service request sent by a user;
the micro-service request sending module is used for sending the micro-service request to a micro-service message queue;
a response message sending module, configured to send a successful response message to the user;
the first judgment module is used for judging whether the micro service corresponding to the micro service request is a key micro service after the micro service request is sent to a micro service message queue;
the response information sending module is used for sending successful response information to the user when the micro service corresponding to the micro service request is not a critical micro service; when the micro service corresponding to the micro service request is a key micro service, sending a successful response message after the request is completely executed;
the detection module is used for detecting whether each micro service meets a preset fault condition in real time before receiving a micro service request sent by a user, and taking the micro service meeting the fault condition as a fault micro service;
the second judgment module is used for judging whether the micro service corresponding to the micro service request is a fault micro service after the micro service request is sent to a micro service message queue;
and the response information sending module is used for sending successful response information to the user when the micro service corresponding to the micro service request is the fault micro service.
6. A microservice architecture comprising a microservice controller according to claim 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611206619.3A CN106533805B (en) | 2016-12-23 | 2016-12-23 | Micro-service request processing method, micro-service controller and micro-service architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611206619.3A CN106533805B (en) | 2016-12-23 | 2016-12-23 | Micro-service request processing method, micro-service controller and micro-service architecture |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106533805A CN106533805A (en) | 2017-03-22 |
| CN106533805B true CN106533805B (en) | 2020-02-04 |
Family
ID=58337515
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611206619.3A Active CN106533805B (en) | 2016-12-23 | 2016-12-23 | Micro-service request processing method, micro-service controller and micro-service architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106533805B (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109582471A (en) | 2017-09-29 | 2019-04-05 | 西门子公司 | Information processing method, device and system |
| CN108173911B (en) * | 2017-12-18 | 2020-08-21 | 中国科学院声学研究所 | Micro-service fault detection processing method and device |
| CN109491801A (en) * | 2018-09-27 | 2019-03-19 | 平安科技（深圳）有限公司 | Micro services access scheduling method, apparatus, medium and electronic equipment |
| CN110086853B (en) * | 2019-03-28 | 2021-08-06 | 浙江明度智控科技有限公司 | Industrial Internet of things information visualization method, server and storage medium |
| CN110149364A (en) * | 2019-04-15 | 2019-08-20 | 厦门市美亚柏科信息股份有限公司 | Method, apparatus, the storage medium of micro services are provided based on data service platform |
| CN110445643B (en) * | 2019-07-25 | 2021-11-16 | 泰康保险集团股份有限公司 | Asynchronous microservice call link tracking method, device, medium and electronic equipment |
| CN110673941B (en) * | 2019-09-27 | 2020-07-17 | 掌阅科技股份有限公司 | Migration method of micro-services in multiple computer rooms, electronic equipment and storage medium |
| CN111580945A (en) * | 2020-04-21 | 2020-08-25 | 智业互联（厦门）健康科技有限公司 | Micro-service task coordination scheduling method and system |
| CN112214334A (en) * | 2020-09-28 | 2021-01-12 | 亚信科技（中国）有限公司 | Micro-service calling method and device, electronic equipment and computer-readable storage medium |
| CN115001933A (en) * | 2022-07-01 | 2022-09-02 | 国家电网有限公司华东分部 | Architecture for non-intrusive microservices and micro-applications |
| CN115562880B (en) * | 2022-08-12 | 2023-09-12 | 华能烟台八角热电有限公司 | Micro-service-based treatment method and system |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105550130A (en) * | 2015-12-14 | 2016-05-04 | 中电科华云信息技术有限公司 | Container based dynamic arrangement method for application environment and system applying method |
| CN106227611A (en) * | 2016-07-26 | 2016-12-14 | 北京北森云计算股份有限公司 | The dynamic micro services call method of a kind of multilingual cloud compiling and device |
-
2016
- 2016-12-23 CN CN201611206619.3A patent/CN106533805B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105550130A (en) * | 2015-12-14 | 2016-05-04 | 中电科华云信息技术有限公司 | Container based dynamic arrangement method for application environment and system applying method |
| CN106227611A (en) * | 2016-07-26 | 2016-12-14 | 北京北森云计算股份有限公司 | The dynamic micro services call method of a kind of multilingual cloud compiling and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106533805A (en) | 2017-03-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106533805B (en) | Micro-service request processing method, micro-service controller and micro-service architecture | |
| CN108173911B (en) | Micro-service fault detection processing method and device | |
| CN106656604A (en) | Microservice request management method, microservice controller and high-concurrence microservice architecture | |
| CN109274544B (en) | Fault detection method and device for distributed storage system | |
| JP2015510201A (en) | Method and apparatus for rapid disaster recovery preparation in a cloud network | |
| CN111078453B (en) | Method, device, computer equipment and storage medium for automatically fusing and recovering micro-service | |
| CN107508694B (en) | Node management method and node equipment in cluster | |
| EP2800024A1 (en) | System and methods for identifying applications in mobile networks | |
| US10355963B2 (en) | Heartbeat period setting method, and terminal | |
| US10320680B1 (en) | Load balancer that avoids short circuits | |
| CN105049549A (en) | Method and system for realizing automatic drift of floating IP (Internet Protocol) address | |
| CN109361542A (en) | The fault handling method of client, device, system, terminal and server | |
| CN114356557A (en) | Cluster capacity expansion method and device | |
| CN113852506A (en) | Fault processing method and device, electronic equipment and storage medium | |
| US10474518B1 (en) | Obtaining historical information in a device core dump | |
| CN111901176A (en) | Fault determination method, device, equipment and storage medium | |
| US10659366B1 (en) | Load balancer metadata forwarding on secure connections | |
| CN108235800B (en) | Network fault detection method, control center equipment and computer storage medium | |
| CN114168071A (en) | Distributed cluster capacity expansion method, distributed cluster capacity expansion device and medium | |
| CN111949421B (en) | SDK calling method, device, electronic equipment and computer readable storage medium | |
| WO2012139466A1 (en) | Resource management method and device | |
| JP6269199B2 (en) | Management server, failure recovery method, and computer program | |
| CN110740064A (en) | Distributed cluster node fault processing method, device, equipment and storage medium | |
| US10674337B2 (en) | Method and device for processing operation for device peripheral | |
| CN113688021B (en) | Load balancing service processing method, device, equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20191213 Address after: 215100 No. 1 Guanpu Road, Guoxiang Street, Wuzhong Economic Development Zone, Suzhou City, Jiangsu Province Applicant after: Suzhou Wave Intelligent Technology Co., Ltd. Address before: 450018 Henan province Zheng Dong New District of Zhengzhou City Xinyi Road No. 278 16 floor room 1601 Applicant before: Zhengzhou Yunhai Information Technology Co. Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |