CN106656604A - Microservice request management method, microservice controller and high-concurrence microservice architecture - Google Patents
Microservice request management method, microservice controller and high-concurrence microservice architecture Download PDFInfo
- Publication number
- CN106656604A CN106656604A CN201611213457.6A CN201611213457A CN106656604A CN 106656604 A CN106656604 A CN 106656604A CN 201611213457 A CN201611213457 A CN 201611213457A CN 106656604 A CN106656604 A CN 106656604A
- Authority
- CN
- China
- Prior art keywords
- microservice
- faulty
- request
- fault condition
- satisfies
- 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.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 16
- 238000001514 detection method Methods 0.000 claims description 18
- 238000011897 real-time detection Methods 0.000 claims description 14
- 230000000694 effects Effects 0.000 abstract description 3
- 238000000034 method Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
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
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- 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
- H04L41/0681—Configuration of triggering conditions
-
- 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/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Maintenance And Management Of Digital Transmission (AREA)
Abstract
本发明公开了一种微服务请求管理方法，包括：实时检测每个微服务是否满足预设故障条件；将满足故障条件的微服务作为故障微服务；接收到所述故障微服务的访问请求后，直接返回相应的访问失败信息；可见，在本方案中，当微服务控制器检测到某一微服务满足预设的故障条件后，直接将对该微服务的访问请求拦截，直接回复访问失败的信息，从而保证了系统的整体可用，确保单个微服务故障不会扩展到整个系统；本发明还公开了一种微服务控制器及高并发微服务架构，同样能实现上述技术效果。
The invention discloses a microservice request management method, comprising: detecting in real time whether each microservice satisfies a preset fault condition; using the microservice satisfying the fault condition as a faulty microservice; receiving the access request of the faulty microservice , directly returns the corresponding access failure information; it can be seen that in this solution, when the microservice controller detects that a certain microservice meets the preset failure conditions, it directly intercepts the access request of the microservice and directly replies the access failure information, thereby ensuring the overall availability of the system and ensuring that a single microservice failure will not extend to the entire system; the invention also discloses a microservice controller and a high-concurrency microservice architecture, which can also achieve the above technical effects.
Description
技术领域technical field
本发明涉及微服务架构领域，更具体地说，涉及一种微服务请求管理方法、微服务控制器及高并发微服务架构。The present invention relates to the field of microservice architecture, and more specifically, to a microservice request management method, a microservice controller and a high-concurrency microservice architecture.
背景技术Background technique
微服务是一个新兴的软件架构，就是把一个大型的单个应用程序和服务拆分为数十个的支持微服务。一个微服务的策略可以让工作变得更为简便，它可扩展单个组件而不是整个的应用程序堆栈，从而满足服务等级协议。目前，随着微服务架构的发展、企业应用越来越多把功能集中的且运行在同一个应用中的单体架构拆分成多个相互独立的微服务架构后，虽然可以降低一损俱损的全局性故障风险，但由于微服务之间存在大量的依赖关系，而且每个微服务都可能发生故障。因此，如何确保单个微服务故障不会扩展到整个系统，是本领域技术人员需要解决的问题。Microservice is an emerging software architecture that splits a large single application and service into dozens of supporting microservices. A microservices strategy can make life easier by scaling individual components rather than the entire application stack to meet service level agreements. At present, with the development of micro-service architecture and more and more enterprise applications, after splitting the monolithic architecture with centralized functions and running in the same application into multiple independent micro-service architectures, although it can reduce the loss of all However, due to the large number of dependencies between microservices, each microservice may fail. Therefore, how to ensure that a failure of a single microservice does not spread to the entire system is a problem to be solved by those skilled in the art.
发明内容Contents of the invention
本发明的目的在于提供一种微服务请求管理方法、微服务控制器及高并发微服务架构，以确保单个微服务故障不会扩展到整个系统。The purpose of the present invention is to provide a micro-service request management method, a micro-service controller and a high-concurrency micro-service architecture to ensure that a single micro-service failure will not extend to the entire system.
为实现上述目的，本发明实施例提供了如下技术方案：In order to achieve the above object, the embodiment of the present invention provides the following technical solutions:
一种微服务请求管理方法，包括：A microservice request management method, comprising:
实时检测每个微服务是否满足预设故障条件；Real-time detection of whether each microservice meets preset failure conditions;
将满足故障条件的微服务作为故障微服务；Use the microservice that meets the fault condition as the faulty microservice;
接收到所述故障微服务的访问请求后，直接返回相应的访问失败信息。After receiving the access request of the faulty microservice, directly return the corresponding access failure information.
其中，所述实时检测每个微服务是否满足预设故障条件，将满足故障条件的微服务作为故障微服务包括：Wherein, the real-time detection of whether each microservice satisfies a preset fault condition, and using the microservice that meets the fault condition as a faulty microservice includes:
实时检测每个访问请求的请求时长是否大于预定时长阈值；Detect in real time whether the request duration of each access request is greater than the predetermined duration threshold;
若是，则将请求时长大于预定阈值的微服务作为所述故障微服务。If yes, the microservice whose request duration is longer than the predetermined threshold is taken as the faulty microservice.
其中，所述实时检测每个微服务是否满足预设故障条件，将满足故障条件的微服务作为故障微服务包括：Wherein, the real-time detection of whether each microservice satisfies a preset fault condition, and using the microservice that meets the fault condition as a faulty microservice includes:
实时检测是否存在服务失败次数大于预定次数阈值的微服务；Detect in real time whether there are microservices whose number of service failures is greater than the predetermined threshold;
若存在，则将服务失败次数大于预定次数阈值的微服务作为所述故障微服务。If it exists, a microservice whose service failure times are greater than a predetermined number threshold is taken as the faulty microservice.
其中，所述实时检测每个微服务是否满足预设故障条件，将满足故障条件的微服务作为故障微服务包括：Wherein, the real-time detection of whether each microservice satisfies a preset fault condition, and using the microservice that meets the fault condition as a faulty microservice includes:
实时检测每个微服务内是否存在可用节点；Real-time detection of whether there are available nodes in each microservice;
将不存在可用节点的微服务作为所述故障微服务。A microservice with no available nodes is taken as the faulty microservice.
其中，所述将满足故障条件的微服务作为故障微服务之后，还包括：Wherein, after the microservice satisfying the fault condition is regarded as the faulty microservice, it also includes:
向预定终端发送故障提示信息。Send fault prompt information to the predetermined terminal.
一种微服务控制器，包括：A microservice controller comprising:
检测模块，用于实时检测每个微服务是否满足预设故障条件；A detection module is used to detect in real time whether each microservice satisfies preset failure conditions;
故障微服务确定模块，用于将满足故障条件的微服务作为故障微服务；A faulty microservice determination module, configured to use the microservice meeting the fault condition as the faulty microservice;
响应模块，用于接收到所述故障微服务的访问请求后，直接返回相应的访问失败信息。The response module is configured to directly return corresponding access failure information after receiving the access request of the faulty microservice.
其中，所述检测模块包括：Wherein, the detection module includes:
第一检测单元，用于实时检测每个访问请求的请求时长是否大于预定时长阈值；The first detection unit is used to detect in real time whether the request duration of each access request is greater than a predetermined duration threshold;
所述故障微服务确定模块，用于将请求时长大于预定阈值的微服务作为所述故障微服务。The faulty microservice determining module is configured to use a microservice whose request duration is greater than a predetermined threshold as the faulty microservice.
其中，所述检测模块包括：Wherein, the detection module includes:
统计单元，用于实时统计每个微服务的服务失败的次数；Statistical unit, used to count the number of service failures of each microservice in real time;
所述故障微服务确定模块，用于将服务失败次数大于预定次数阈值的微服务作为所述故障微服务。The faulty microservice determination module is configured to use a microservice whose number of service failures is greater than a predetermined threshold as the faulty microservice.
其中，所述检测模块包括：Wherein, the detection module includes:
第二检测单元，用于实时检测每个微服务内是否存在可用节点；The second detection unit is used to detect in real time whether there are available nodes in each microservice;
所述故障微服务确定模块，用于将不存在可用节点的微服务作为所述故障微服务。The faulty microservice determination module is configured to use a microservice with no available nodes as the faulty microservice.
一种高并发微服务架构，包括上述任意一项所述的微服务控制器。A high-concurrency microservice architecture, including any one of the microservice controllers described above.
通过以上方案可知，本发明实施例提供的一种微服务请求管理方法，包括：实时检测每个微服务是否满足预设故障条件；将满足故障条件的微服务作为故障微服务；接收到所述故障微服务的访问请求后，直接返回相应的访问失败信息；可见，在本方案中，当微服务控制器检测到某一微服务满足预设的故障条件后，直接将对该微服务的访问请求拦截，直接回复访问失败的信息，从而保证了系统的整体可用，确保单个微服务故障不会扩展到整个系统；本发明还公开了一种微服务控制器及高并发微服务架构，同样能实现上述技术效果。It can be seen from the above solutions that a microservice request management method provided by the embodiment of the present invention includes: detecting in real time whether each microservice satisfies a preset fault condition; taking the microservice that meets the fault condition as a faulty microservice; receiving the After the access request of the faulty microservice, it directly returns the corresponding access failure information; it can be seen that in this solution, when the microservice controller detects that a certain microservice meets the preset failure conditions, it directly sends the access to the microservice The request is intercepted and the access failure information is directly replied, thereby ensuring the overall availability of the system and ensuring that a single microservice failure will not extend to the entire system; the invention also discloses a microservice controller and a high-concurrency microservice architecture, which can also Realize above-mentioned technical effect.
附图说明Description of drawings
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work.
图1为本发明实施例公开的一种微服务请求管理方法流程示意图；FIG. 1 is a schematic flow diagram of a microservice request management method disclosed in an embodiment of the present invention;
图2为本发明实施例公开的一种微服务控制器结构示意图；FIG. 2 is a schematic structural diagram of a microservice controller disclosed in an embodiment of the present invention;
图3为本发明实施例公开的一种高并发微服务架构结构示意图。FIG. 3 is a schematic structural diagram of a high-concurrency microservice architecture disclosed by an embodiment of the present invention.
具体实施方式detailed description
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.
本发明实施例公开了一种微服务请求管理方法、微服务控制器及高并发微服务架构，以确保单个微服务故障不会扩展到整个系统。The embodiment of the present invention discloses a micro-service request management method, a micro-service controller and a high-concurrency micro-service architecture, so as to ensure that a single micro-service failure does not extend to the entire system.
参见图1，本发明实施例提供的一种微服务请求管理方法，包括：Referring to Fig. 1, a microservice request management method provided by an embodiment of the present invention includes:
S101、实时检测每个微服务是否满足预设故障条件；S101. Detect in real time whether each microservice satisfies a preset failure condition;
具体的，在本实施例中的预设故障条件可以根据实际情况进行设定，只要能判定微服务出现故障的条件均可。Specifically, the preset failure conditions in this embodiment can be set according to actual conditions, as long as the failure conditions of the microservice can be determined.
S102、将满足故障条件的微服务作为故障微服务；S102. Use the microservice that satisfies the fault condition as the faulty microservice;
其中，所述将满足故障条件的微服务作为故障微服务之后，还包括：向预定终端发送故障提示信息。Wherein, after the microservice meeting the failure condition is used as the failure microservice, the method further includes: sending failure prompt information to a predetermined terminal.
具体的，若判定某一微服务为故障微服务时，可以生成对应的日志信息，也可以将该微服务故障的提示信息发送至预定终端，以便及时提醒工作人员进行维护。Specifically, if it is determined that a certain microservice is a faulty microservice, corresponding log information can be generated, and a prompt message of the microservice failure can also be sent to a predetermined terminal, so as to promptly remind staff to perform maintenance.
S103、接收到所述故障微服务的访问请求后，直接返回相应的访问失败信息。S103. After receiving the access request of the faulty microservice, directly return corresponding access failure information.
需要说明的是，参见图3，由于微服务控制器控制多个微服务，因此在S101中需对每个微服务进行检测，若检测到某一微服务满足预设故障条件，则通过S102将该微服务确定为故障微服务，这样若微服务控制器接收到对该故障服务器的访问请求后，则直接拦截，并回复访问失败的信息，从而保证系统整体可用。It should be noted that, referring to Figure 3, since the microservice controller controls multiple microservices, each microservice needs to be detected in S101, and if it is detected that a certain microservice satisfies the preset failure condition, the The microservice is determined to be a faulty microservice, so that if the microservice controller receives an access request to the faulty server, it will directly intercept it and reply with a message of access failure, thereby ensuring the overall availability of the system.
基于上述实施例，在本实施例中，所述实时检测每个微服务是否满足预设故障条件，将满足故障条件的微服务作为故障微服务包括：Based on the above embodiment, in this embodiment, the real-time detection of whether each microservice satisfies the preset failure condition, and the microservice meeting the failure condition as the failure microservice includes:
实时检测每个访问请求的请求时长是否大于预定时长阈值；Detect in real time whether the request duration of each access request is greater than the predetermined duration threshold;
若是，则将请求时长大于预定阈值的微服务作为所述故障微服务。If yes, the microservice whose request duration is longer than the predetermined threshold is taken as the faulty microservice.
具体的，在本实施例中，若某一访问请求的访问时长大于预定阈值，则说明在响应该访问请求时，对应的微服务出现了故障，因此在本实施例中，当检测到存在访问请求的请求时长大于预定时长阈值时，则判定与该访问请求对应的微服务为故障微服务。Specifically, in this embodiment, if the access duration of an access request is greater than a predetermined threshold, it means that the corresponding microservice has failed when responding to the access request. Therefore, in this embodiment, when it is detected that there is an access When the request duration of the request is greater than the predetermined duration threshold, it is determined that the microservice corresponding to the access request is a faulty microservice.
需要说明的是，本实施例中的访问请求的请求时长，可以是正在访问某微服务的请求时长，例如：访问请求访问微服务A时，通过计时器开始计时，若该计时时长大于预设时长阈值，则判定微服务A出现故障，因此，将微服务A作为故障微服务，并执行S103；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 microservice A, the timer starts counting, if the timing duration is longer than the preset duration threshold, it is determined that microservice A is faulty, therefore, microservice A is regarded as a faulty microservice, and S103 is executed;
本实施例中的访问请求的请求时长同样也可以是已经结束访问的请求时长，例如：访问请求访问微服务B时，对该访问从开始访问至访问结束进行计时，若该访问时长大于预定时长阈值，则将微服务B作为故障微服务。但是，为了避免某一微服务由于非故障原因导致出现超时情况，可对每个微服务的超时次数进行统计，当统计次数大于次数阈值时，再将该微服务作为故障微服务。The request duration of the access request in this embodiment can also be the request duration of the access that has ended, for example: when the access request visits microservice B, the access is timed from the beginning of the access to the end of the access, if the access duration is longer than the predetermined duration threshold, microservice B is regarded as a faulty microservice. However, in order to avoid a microservice from timeout due to non-fault reasons, the number of timeouts of each microservice can be counted, and when the count is greater than the number threshold, the microservice is regarded as a faulty microservice.
基于上述任意实施例，在本实施例中，所述实时检测每个微服务是否满足预设故障条件，将满足故障条件的微服务作为故障微服务包括：Based on any of the above embodiments, in this embodiment, the real-time detection of whether each microservice satisfies a preset fault condition, and taking the microservice that meets the fault condition as a faulty microservice includes:
实时检测是否存在服务失败次数大于预定次数阈值的微服务；Detect in real time whether there are microservices whose number of service failures is greater than the predetermined threshold;
若存在，则将服务失败次数大于预定次数阈值的微服务作为所述故障微服务。If it exists, a microservice whose service failure times are greater than a predetermined number threshold is taken as the faulty microservice.
具体的，本实施例中的服务失败次数可以为预定时长内某微服务出现的失败次数，也可以是同一访问请求访问同一微服务出现失败的次数，在此并不限定；当某一微服务累积的服务失败次数大于预定次数阈值时，代表该微服务成功处理访问请求的概率变低，很可能出现故障，因此将服务失败次数大于预定次数阈值的微服务作为故障微服务。Specifically, the number of service failures in this embodiment may be the number of failures of a certain microservice within a predetermined period of time, or the number of failures of the same access request to access the same microservice, which is not limited here; when a certain microservice When the accumulated number of service failures is greater than the predetermined number threshold, it means that the probability of the microservice successfully processing the access request becomes low, and a failure is likely to occur. Therefore, the microservice with the number of service failures greater than the predetermined number threshold is regarded as a faulty microservice.
基于上述任意实施例，在本实施例中，所述实时检测每个微服务是否满足预设故障条件，将满足故障条件的微服务作为故障微服务包括：Based on any of the above embodiments, in this embodiment, the real-time detection of whether each microservice satisfies a preset fault condition, and taking the microservice that meets the fault condition as a faulty microservice includes:
实时检测每个微服务内是否存在可用节点；Real-time detection of whether there are available nodes in each microservice;
将不存在可用节点的微服务作为所述故障微服务。A microservice with no available nodes is taken as the faulty microservice.
具体的，参见图3，在本实施例中的每个微服务可能存在多个节点，若该微服务中不存在可用节点时，则代表该微服务已经没有能力响应访问请求，因此，在本实施例中，若检测到某微服务不存在可用节点，则将该微服务作为故障微服务。需要说明的是，在上述实施例中，提供了三种判定故障微服务的方法，即：通过访问时长、服务失败次数和可用节点数量进行判定，微服务控制器可同时执行这三种判定方法，也可以执行任意一者或者任意两者，在此并不具体限定。Specifically, referring to FIG. 3, each microservice in this embodiment may have multiple nodes. If there is no available node in the microservice, it means that the microservice has no ability to respond to the access request. Therefore, in this In the embodiment, if it is detected that there is no available node for a certain microservice, this microservice is regarded as a faulty microservice. It should be noted that in the above embodiment, three methods for judging the faulty microservice are provided, that is, judging by the access duration, number of service failures and the number of available nodes, and the microservice controller can execute these three judging methods at the same time , and any one or both may be performed, which is not specifically limited here.
下面对本发明实施例提供的微服务控制器进行介绍，下文描述的微服务控制器与上文描述的微服务请求管理方法可以相互参照。The microservice controller provided by the embodiment of the present invention is introduced below, and the microservice controller described below and the microservice request management method described above may refer to each other.
参见图2，本发明实施例提供的一种微服务控制器100，包括：Referring to FIG. 2, a microservice controller 100 provided by an embodiment of the present invention includes:
检测模块110，用于实时检测每个微服务是否满足预设故障条件；A detection module 110, configured to detect in real time whether each microservice satisfies a preset failure condition;
故障微服务确定模块120，用于将满足故障条件的微服务作为故障微服务；A faulty microservice determination module 120, configured to use the microservice meeting the fault condition as a faulty microservice;
响应模块130，用于接收到所述故障微服务的访问请求后，直接返回相应的访问失败信息。The response module 130 is configured to directly return corresponding access failure information after receiving the access request of the faulty microservice.
基于上述实施例，所述检测模块包括：Based on the foregoing embodiments, the detection module includes:
第一检测单元，用于实时检测每个访问请求的请求时长是否大于预定时长阈值；The first detection unit is used to detect in real time whether the request duration of each access request is greater than a predetermined duration threshold;
所述故障微服务确定模块，用于将请求时长大于预定阈值的微服务作为所述故障微服务。The faulty microservice determining module is configured to use a microservice whose request duration is greater than a predetermined threshold as the faulty microservice.
基于上述实施例，所述检测模块包括：Based on the foregoing embodiments, the detection module includes:
统计单元，用于实时统计每个微服务的服务失败的次数；Statistical unit, used to count the number of service failures of each microservice in real time;
所述故障微服务确定模块，用于将服务失败次数大于预定次数阈值的微服务作为所述故障微服务。The faulty microservice determination module is configured to use a microservice whose number of service failures is greater than a predetermined threshold as the faulty microservice.
基于上述实施例，所述检测模块包括：Based on the foregoing embodiments, the detection module includes:
第二检测单元，用于实时检测每个微服务内是否存在可用节点；The second detection unit is used to detect in real time whether there are available nodes in each microservice;
所述故障微服务确定模块，用于将不存在可用节点的微服务作为所述故障微服务。The faulty microservice determination module is configured to use a microservice with no available nodes as the faulty microservice.
参见图3，本发明实施例提供的一种高并发微服务架构，包括上述任意一项所述的微服务控制器100。Referring to FIG. 3 , a high-concurrency microservice architecture provided by an embodiment of the present invention includes the microservice controller 100 described in any one of the foregoing.
具体的，还包括计数器200和超时器300；计数器用于统计每个微服务的服务失败次数，超时器，用于统计每个访问请求的访问时长。Specifically, it also includes a counter 200 and a timeout 300; the counter is used to count the number of service failures of each microservice, and the timeout is used to count the access duration of each access request.
本发明实施例提供的一种微服务请求管理方法，包括：实时检测每个微服务是否满足预设故障条件；将满足故障条件的微服务作为故障微服务；接收到所述故障微服务的访问请求后，直接返回相应的访问失败信息；可见，在本方案中，当微服务控制器检测到某一微服务满足预设的故障条件后，直接将对该微服务的访问请求拦截，直接回复访问失败的信息，从而保证了系统的整体可用，确保单个微服务故障不会扩展到整个系统；本发明还公开了一种微服务控制器及高并发微服务架构，同样能实现上述技术效果。A microservice request management method provided by an embodiment of the present invention includes: detecting in real time whether each microservice satisfies a preset fault condition; taking the microservice that meets the fault condition as a faulty microservice; receiving the access of the faulty microservice After the request, the corresponding access failure information is directly returned; it can be seen that in this solution, when the microservice controller detects that a certain microservice meets the preset failure conditions, it directly intercepts the access request of the microservice and directly replies Access to failed information ensures the overall availability of the system and ensures that a single microservice failure will not spread to the entire system; the invention also discloses a microservice controller and a high-concurrency microservice architecture, which can also achieve the above technical effects.
本说明书中各个实施例采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似部分互相参见即可。Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same and similar parts of each embodiment can be referred to each other.
对所公开的实施例的上述说明，使本领域专业技术人员能够实现或使用本发明。对这些实施例的多种修改对本领域的专业技术人员来说将是显而易见的，本文中所定义的一般原理可以在不脱离本发明的精神或范围的情况下，在其它实施例中实现。因此，本发明将不会被限制于本文所示的这些实施例，而是要符合与本文所公开的原理和新颖特点相一致的最宽的范围。The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention will not 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 (10)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611213457.6A CN106656604A (en) | 2016-12-23 | 2016-12-23 | Microservice request management method, microservice controller and high-concurrence microservice architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611213457.6A CN106656604A (en) | 2016-12-23 | 2016-12-23 | Microservice request management method, microservice controller and high-concurrence microservice architecture |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106656604A true CN106656604A (en) | 2017-05-10 |
Family
ID=58827749
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611213457.6A Pending CN106656604A (en) | 2016-12-23 | 2016-12-23 | Microservice request management method, microservice controller and high-concurrence microservice architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106656604A (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108173911A (en) * | 2017-12-18 | 2018-06-15 | 中国科学院声学研究所 | A microservice fault detection and processing method and device |
| CN108712309A (en) * | 2018-06-11 | 2018-10-26 | 郑州云海信息技术有限公司 | A kind of micro services node means of defence under micro services framework and system |
| CN109743367A (en) * | 2018-12-24 | 2019-05-10 | 青岛海信智能商用系统股份有限公司 | Service processing method, device, electronic equipment and readable storage medium storing program for executing |
| CN109766210A (en) * | 2019-01-17 | 2019-05-17 | 多点生活(成都)科技有限公司 | Service fusing control method, service fusing control device and server cluster |
| CN110673941A (en) * | 2019-09-27 | 2020-01-10 | 掌阅科技股份有限公司 | Migration method of micro-services in multiple computer rooms, electronic equipment and storage medium |
| CN110784554A (en) * | 2019-11-05 | 2020-02-11 | 杭州安恒信息技术股份有限公司 | Method and device for processing service error of web microservice cluster |
| CN110990245A (en) * | 2019-12-04 | 2020-04-10 | 北京明略软件系统有限公司 | Micro-service operation state judgment method and device based on call chain data |
| CN110995504A (en) * | 2019-12-18 | 2020-04-10 | 北京百度网讯科技有限公司 | Microservice node exception handling method, device and system |
| CN111427674A (en) * | 2020-03-19 | 2020-07-17 | 成都云盯科技有限公司 | Micro-service management method, device and system |
| CN111464373A (en) * | 2019-01-18 | 2020-07-28 | 苏宁易购集团股份有限公司 | Micro-service full-link monitoring system and method |
| CN113407224A (en) * | 2020-03-17 | 2021-09-17 | 北京亿阳信通科技有限公司 | Micro-service management method and device |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101883028A (en) * | 2010-06-30 | 2010-11-10 | 中兴通讯股份有限公司 | Method and device for detecting network file system server |
| CN103345439A (en) * | 2013-07-17 | 2013-10-09 | 国家电网公司 | Method and device for monitoring health states of full links in information system |
| CN104408110A (en) * | 2014-11-24 | 2015-03-11 | 北京奇虎科技有限公司 | Method, device and system for requesting data |
| CN105515759A (en) * | 2015-11-27 | 2016-04-20 | 国网信息通信产业集团有限公司 | Micro service registration method and micro service registration system |
| CN105808414A (en) * | 2016-03-08 | 2016-07-27 | 联想(北京)有限公司 | Log processing method and log processing electronic equipment |
| CN105824375A (en) * | 2016-04-05 | 2016-08-03 | 浪潮电子信息产业股份有限公司 | Server |
| CN106230987A (en) * | 2016-09-21 | 2016-12-14 | 南方电网科学研究院有限责任公司 | Information integration system and method based on electric power PaaS cloud platform |
| CN106227611A (en) * | 2016-07-26 | 2016-12-14 | 北京北森云计算股份有限公司 | The dynamic micro services call method of a kind of multilingual cloud compiling and device |
| CN106227605A (en) * | 2016-07-26 | 2016-12-14 | 北京北森云计算股份有限公司 | The dynamic micro services expansion method of a kind of multilingual cloud compiling and device |
| CN106250199A (en) * | 2016-07-26 | 2016-12-21 | 北京北森云计算股份有限公司 | The dynamic micro services call method of a kind of multilingual cloud compiling and device |
-
2016
- 2016-12-23 CN CN201611213457.6A patent/CN106656604A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101883028A (en) * | 2010-06-30 | 2010-11-10 | 中兴通讯股份有限公司 | Method and device for detecting network file system server |
| CN103345439A (en) * | 2013-07-17 | 2013-10-09 | 国家电网公司 | Method and device for monitoring health states of full links in information system |
| CN104408110A (en) * | 2014-11-24 | 2015-03-11 | 北京奇虎科技有限公司 | Method, device and system for requesting data |
| CN105515759A (en) * | 2015-11-27 | 2016-04-20 | 国网信息通信产业集团有限公司 | Micro service registration method and micro service registration system |
| CN105808414A (en) * | 2016-03-08 | 2016-07-27 | 联想(北京)有限公司 | Log processing method and log processing electronic equipment |
| CN105824375A (en) * | 2016-04-05 | 2016-08-03 | 浪潮电子信息产业股份有限公司 | Server |
| CN106227611A (en) * | 2016-07-26 | 2016-12-14 | 北京北森云计算股份有限公司 | The dynamic micro services call method of a kind of multilingual cloud compiling and device |
| CN106227605A (en) * | 2016-07-26 | 2016-12-14 | 北京北森云计算股份有限公司 | The dynamic micro services expansion method of a kind of multilingual cloud compiling and device |
| CN106250199A (en) * | 2016-07-26 | 2016-12-21 | 北京北森云计算股份有限公司 | The dynamic micro services call method of a kind of multilingual cloud compiling and device |
| CN106230987A (en) * | 2016-09-21 | 2016-12-14 | 南方电网科学研究院有限责任公司 | Information integration system and method based on electric power PaaS cloud platform |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108173911A (en) * | 2017-12-18 | 2018-06-15 | 中国科学院声学研究所 | A microservice fault detection and processing method and device |
| CN108173911B (en) * | 2017-12-18 | 2020-08-21 | 中国科学院声学研究所 | Microservice fault detection and processing method and device |
| CN108712309A (en) * | 2018-06-11 | 2018-10-26 | 郑州云海信息技术有限公司 | A kind of micro services node means of defence under micro services framework and system |
| CN108712309B (en) * | 2018-06-11 | 2022-03-25 | 郑州云海信息技术有限公司 | Microservice node protection method and system under microservice architecture |
| CN109743367A (en) * | 2018-12-24 | 2019-05-10 | 青岛海信智能商用系统股份有限公司 | Service processing method, device, electronic equipment and readable storage medium storing program for executing |
| CN109766210A (en) * | 2019-01-17 | 2019-05-17 | 多点生活(成都)科技有限公司 | Service fusing control method, service fusing control device and server cluster |
| CN109766210B (en) * | 2019-01-17 | 2022-04-22 | 多点生活(成都)科技有限公司 | Service fusing control method, service fusing control device and server cluster |
| CN111464373A (en) * | 2019-01-18 | 2020-07-28 | 苏宁易购集团股份有限公司 | Micro-service full-link monitoring system and method |
| CN110673941A (en) * | 2019-09-27 | 2020-01-10 | 掌阅科技股份有限公司 | Migration method of micro-services in multiple computer rooms, electronic equipment and storage medium |
| CN110784554A (en) * | 2019-11-05 | 2020-02-11 | 杭州安恒信息技术股份有限公司 | Method and device for processing service error of web microservice cluster |
| CN110784554B (en) * | 2019-11-05 | 2022-07-08 | 杭州安恒信息技术股份有限公司 | Method and device for processing service error of web microservice cluster |
| CN110990245A (en) * | 2019-12-04 | 2020-04-10 | 北京明略软件系统有限公司 | Micro-service operation state judgment method and device based on call chain data |
| CN110995504A (en) * | 2019-12-18 | 2020-04-10 | 北京百度网讯科技有限公司 | Microservice node exception handling method, device and system |
| CN113407224A (en) * | 2020-03-17 | 2021-09-17 | 北京亿阳信通科技有限公司 | Micro-service management method and device |
| CN113407224B (en) * | 2020-03-17 | 2025-01-03 | 北京亿阳信通科技有限公司 | A microservice management method and device |
| CN111427674A (en) * | 2020-03-19 | 2020-07-17 | 成都云盯科技有限公司 | Micro-service management method, device and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106656604A (en) | Microservice request management method, microservice controller and high-concurrence microservice architecture | |
| CN106533805B (en) | Micro-service request processing method, micro-service controller and micro-service architecture | |
| JP7020616B2 (en) | Methods and systems for resource scheduling | |
| CN110830283B (en) | Fault detection method, apparatus, equipment and system | |
| CN108737574A (en) | A kind of node off-line judgment method, device, equipment and readable storage medium storing program for executing | |
| CN105991412A (en) | Method and device for pushing message | |
| CN104506392B (en) | A kind of delay machine detection method and equipment | |
| CN105095001A (en) | Virtual machine exception recovery method under distributed environment | |
| CN111901422A (en) | Method, system and device for managing nodes in cluster | |
| CN102970167B (en) | The fault detection method of network node, network node and system in group system | |
| WO2017215430A1 (en) | Node management method in cluster and node device | |
| WO2015058711A1 (en) | Rapid fault detection method and device | |
| CN113067875B (en) | Access method, device and equipment based on dynamic flow control of micro-service gateway | |
| CN108092857A (en) | A kind of distributed system heartbeat detecting method and relevant apparatus | |
| CN106375150A (en) | Server disconnection control method and device | |
| CN108833190A (en) | A kind of NFS service failure warning method, device and storage medium | |
| WO2020098266A1 (en) | Abnormal response method and device | |
| CN103731315A (en) | Server failure detecting method | |
| CN109586989B (en) | State checking method, device and cluster system | |
| CN111064802B (en) | Network request processing method and device, electronic equipment and storage medium | |
| CN101719853B (en) | How to detect the running status of the server | |
| CN104702439B (en) | The method and apparatus for monitoring network node | |
| CN108235800B (en) | A network fault detection method, control center device and computer storage medium | |
| CN108964992A (en) | A kind of node failure detection method, device and computer readable storage medium | |
| CN109218137A (en) | The condition detection method and device of a kind of node in distributed system |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170510 |