CN114296985A - Global exception handling method and platform in large-scale micro-service cluster scene - Google Patents
Global exception handling method and platform in large-scale micro-service cluster scene Download PDFInfo
- Publication number
- CN114296985A CN114296985A CN202111653425.9A CN202111653425A CN114296985A CN 114296985 A CN114296985 A CN 114296985A CN 202111653425 A CN202111653425 A CN 202111653425A CN 114296985 A CN114296985 A CN 114296985A
- Authority
- CN
- China
- Prior art keywords
- abnormal information
- service
- micro
- information
- abnormal
- 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
- 238000000034 method Methods 0.000 title claims abstract description 44
- 230000002159 abnormal effect Effects 0.000 claims abstract description 229
- 238000012545 processing Methods 0.000 claims abstract description 63
- 238000004806 packaging method and process Methods 0.000 claims abstract description 41
- 230000003068 static effect Effects 0.000 claims description 5
- 230000005856 abnormality Effects 0.000 description 4
- 230000010365 information processing Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Exchange Systems With Centralized Control (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to the field of computer micro-service application, and discloses a global exception handling method and a platform under a large-scale micro-service cluster scene, wherein the method comprises the following steps: acquiring all original abnormal information from the micro-service cluster; processing the micro-service abnormal information to obtain first splicing abnormal information, and processing the public component abnormal information to obtain second splicing abnormal information; sending the obtained first splicing abnormal information and the second splicing abnormal information to a Spring frame tangent plane for performing abnormal packaging processing to obtain corresponding first packaging abnormal information and second packaging abnormal information; and returning the first packaging abnormal information and the second packaging abnormal information to a sender of the corresponding original abnormal information. The invention can solve the problem that the processing of the abnormity in the existing system is difficult to manage in a unified way, and realizes the functions of global abnormity centralized storage, quick query, unified processing and the like with less resource consumption.
Description
Technical Field
The invention relates to the field of computer micro-service application, in particular to a global exception handling method and a global exception handling platform in a large-scale micro-service cluster scene.
Background
Microservices are a form of architectural design, where each microservice is deployed independently, focusing on completing only one task. The cluster mode realizes load balance of the services by deploying the same set of services on different servers for external access. At present, a plurality of large-scale complex application systems divide a service into a plurality of sub-services, then cluster deployment is carried out on each sub-service, and if a certain sub-service has a problem, the whole system can still keep normal action. Each sub-service may be composed of one or more micro-services, each micro-service generally includes an externally-facing service interface provided for an external client, and is used for providing services such as user login, registration and the like for the client; and providing an internal service interface for other micro-services for mutual service calling to realize a complete business process.
In practical application, no matter the micro-services are provided to an external client as a server side, or the micro-services are mutually called, abnormal conditions inevitably occur, and timely capture and processing are needed. The exception is divided into a checking type exception and a non-checking type exception, when various exceptions occur, the service code of the system needs to be processed, and the exception is prevented from being directly thrown out to a user. The check-type exceptions require processing on the code method that generated the exception, and the processing on the check-type exceptions may be distributed across the system; the handling of non-checking exceptions may be handled at the top of the method service call. Because there are numerous method services in a system, the handling of non-checking exceptions may also be at the invocation of each method service. Therefore, it is difficult to uniformly manage the problem that the processing for the abnormality may be distributed at various positions in the system.
In the industry, a service system is generally combined with a section feature of a Spring framework to perform global exception handling, the Spring framework is a micro-service framework, and a section consists of a tangent point and an enhancement and includes definitions of a crosscut logic and a connection point. The exception handling method defined by the Spring framework aims at annotating modified classes by a specific method, and can carry out business handling on specific exceptions. The method can complete the global exception handling in a single service, but is difficult to achieve high internal clustering of exception handling services, so the method cannot be well applied to a multi-service scene of a micro-service cluster. In addition, some fields in the exception information may need to be replaced, the contents thrown in different scenes are different, exception handling in a large-scale micro-service cluster scene needs to be performed in a unified manner, and meanwhile, the system is required to pay attention to exception handling as little as possible, so that the exception handling and the exception handling are balanced. Finally, each microservice may use a common component such as a database, and exception handling of the common component may have redundant code if placed in each microservice.
Disclosure of Invention
The technical purpose is as follows: aiming at the technical problems, the invention discloses a global anomaly handling method and a platform under a large-scale micro-service cluster scene, which can be used for carrying out centralized storage, quick query and unified handling on global anomalies under the large-scale micro-service cluster scene.
The technical scheme is as follows: in order to achieve the technical purpose, the invention adopts the following technical scheme:
a global exception handling method under a large-scale micro-service cluster scene is characterized by comprising the following steps:
acquiring all original abnormal information from the micro-service cluster;
classifying the acquired original abnormal information into micro-service abnormal information and public component abnormal information according to the difference of information formats, processing the micro-service abnormal information to obtain first splicing abnormal information, and splicing the public component abnormal information to obtain second splicing abnormal information;
sending the first splicing abnormal information and the second splicing abnormal information to a Spring frame tangent plane for performing abnormal packaging processing to obtain corresponding first packaging abnormal information and second packaging abnormal information;
and returning the first packaging abnormal information and the second packaging abnormal information to a sender of the corresponding original abnormal information.
Preferably, the obtained original abnormal information is classified into micro-service abnormal information and common component abnormal information, and the method comprises the following steps:
judging whether the original abnormal information is represented by a format comprising a micro-service name, an abnormal code, an abnormal message with a first variable and a second variable, if so, classifying the original abnormal information into the micro-service abnormal information, otherwise, classifying the original abnormal information into the public component abnormal information.
Preferably, the processing the micro-service abnormal information to obtain first splicing abnormal information, and the splicing processing the public component abnormal information to obtain second splicing abnormal information includes the steps:
for micro-service abnormal information, judging a micro-service source with abnormal occurrence according to a micro-service name, and replacing a first variable in the micro-service abnormal information with a second variable to obtain first splicing abnormal information;
and for the abnormal information of the public component, splicing the abnormal information of the public component according to a predefined format to obtain second spliced abnormal information.
Preferably, the original exception information is generated by any micro service in the micro service cluster, and is sent by the called micro service when the service call has an error; or when the common component is abnormal, the micro-service accessing and discovering the common component is used for sending the abnormal micro-service.
Preferably, the original exception information, the first concatenation exception information, and the second concatenation exception information are stored in the form of Map, key is an exception code, value is the content of the exception information, and the exception code is defined as a global static constant.
A global exception handling platform, comprising:
the device module is used for acquiring all original abnormal information from the micro-service cluster and classifying the acquired original abnormal information into micro-service abnormal information and common component abnormal information according to the difference of information formats; then processing the micro-service abnormal information to obtain first splicing abnormal information, and processing the public component abnormal information to obtain second splicing abnormal information;
the packaging module is used for sending the first splicing abnormal information and the second splicing abnormal information to a Spring frame tangent plane for performing abnormal packaging processing to obtain corresponding first packaging abnormal information and second packaging abnormal information;
and the feedback module is used for returning the first packaging abnormal information and the second packaging abnormal information to the corresponding sender of the original abnormal information.
Preferably, the service module is further included, and is configured to receive an exception information query request and perform an exception information query.
Preferably, the device further comprises a storage module, configured to store all original exception information, the first splicing exception information, and the second splicing exception information.
A medium storing computer-executable instructions, characterized in that: the instructions, when executed by the processing unit, are for implementing the method.
An electronic device, characterized in that: comprising a processing unit and a storage unit storing computer-executable instructions for implementing the method when executed by the processing unit.
Has the advantages that: compared with the prior art, the invention has the following technical effects:
the scheme adopted by the invention can solve the problem that the global exception handling in a large-scale micro-service cluster scene is difficult to uniformly manage, the exception information is uniformly processed through the exception handling platform, the section capability of the spring frame is combined, the functions of global exception centralized storage, quick query, uniform processing and the like are realized with less resource consumption, and the exception information processing amount in the system is reduced to the greatest extent.
Drawings
FIG. 1 is a flowchart of a global exception handling method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of the structure of the entire micro service group in the Internet according to the embodiment of the invention;
fig. 3 is a schematic structural diagram of a global exception handling platform in the embodiment of the present invention.
Detailed Description
Example 1
The embodiment provides a global exception handling method in a large-scale micro-service cluster scene, which comprises the following steps:
acquiring all original abnormal information from the micro-service cluster;
classifying the acquired original abnormal information into micro-service abnormal information and public component abnormal information according to the difference of information formats, processing the micro-service abnormal information to obtain first splicing abnormal information, and processing the public component abnormal information to obtain second splicing abnormal information;
sending the obtained first splicing abnormal information and the second splicing abnormal information to a Spring frame tangent plane for performing abnormal packaging processing to obtain corresponding first packaging abnormal information and second packaging abnormal information;
returning the first packaging abnormal information and the second packaging abnormal information to a sender of the corresponding original abnormal information;
the original abnormal information is generated by any micro service in the micro service cluster and is sent by the called micro service when the service calling has an error; or when the common component is abnormal, the micro-service accessing and discovering the common component is used for sending the abnormal micro-service.
Specifically, when classifying the acquired original abnormal information according to the difference of the information formats, the method includes the steps of:
analyzing the format of the received original abnormal information, if the original abnormal information is represented by the format comprising a micro-service ID, an abnormal code ID, an abnormal message with a first variable and a second variable, judging that the original abnormal information is classified into the micro-service abnormal information, otherwise, classifying the original abnormal information into the public component abnormal information.
Specifically, when the classified original abnormal information is processed, the method includes the steps of:
when the micro-service abnormal information is processed, judging a micro-service source with an abnormal micro-service according to the micro-service ID, and replacing a first variable in the original abnormal information with a second variable to obtain first splicing abnormal information; if the original information includes "device% s abnormal, PE 1" "% s" is a first variable, and "PE 1" is a second variable.
And when the abnormal information of the public component is processed, splicing the abnormal information of the public component according to a predefined format to obtain second spliced abnormal information.
The original abnormal information, the first splicing abnormal information and the second splicing abnormal information are stored in a Map form, the key is the content of the abnormal code, the value is the content of the abnormal information, and the abnormal code is defined as a global static constant.
Specifically, the micro service abnormality information includes: exceptinonenum, i.e. exception code, serviceId, i.e. micro service name, exception message exceptinomessage with a first variable errorVariable, second variable. Different microservices may define different microservice name serviceids.
Example 2
As shown in fig. 3, in the embodiment, a global exception handling platform is provided, where a unified exception handling platform decoupled from a service code needs to be established, the platform is divided into a detector module and a service module, the detector module is used for storing and processing exceptions, and the service module is used for querying exceptions. The processing of the detector module comprises two aspects, on one hand, splicing variables in the abnormal information, and on the other hand, the processing refers to the abnormal processing of the common component.
The method specifically comprises the following steps:
the device module is used for acquiring all original abnormal information from the micro-service cluster and classifying the acquired original abnormal information into micro-service abnormal information and common component abnormal information according to the difference of information formats; then processing the micro-service abnormal information to obtain first splicing abnormal information, and processing the public component abnormal information to obtain second splicing abnormal information;
the packaging module is used for sending the obtained first splicing abnormal information and the second splicing abnormal information to a Spring frame tangent plane for performing abnormal packaging processing to obtain corresponding first packaging abnormal information and second packaging abnormal information;
and the feedback module is used for returning the first packaging abnormal information and the second packaging abnormal information to a sender sending the corresponding original abnormal information.
And the service module is used for receiving the abnormal information query request and performing abnormal information query.
And the storage module stores all the original abnormal information, the first abnormal information and the second abnormal information into the storage module.
Furthermore, each micro-service is provided with a service release module, a business flow module, a remote calling module and an information processing module, wherein,
the service issuing module is used for sending a service request to the service flow module, receiving service requests sent by other micro services and sending the service requests to the service flow module;
the service flow module is used for carrying out service processing according to the information sent by the service release module and calling a detector module or a service module of the global exception handling platform when the service is called or the common component is abnormal;
the remote calling module is used for sending service requests to other micro-services or receiving packaged abnormal information sent by other micro-services;
and the information processing module is used for receiving the packaged abnormal information forwarded by the remote calling module and processing or forwarding the packaged abnormal information.
The service module relies on the detector module, a service query interface is provided for the outside, and abnormal information in the detector module is queried, for example, a URL query interface of a Get protocol is exposed for the outside, the interface is provided, if an abnormal information processing step is added subsequently, the information amount is large, a user can query for an abnormality according to an abnormal code displayed on the interface, and the abnormal information and the processing step are returned.
Example 3:
fig. 1 shows an application example of the global exception handling platform in embodiment 2.
A cluster service comprises a micro service A, a micro service B, a micro service C and a micro service D, wherein the micro service A calls the micro service B, the micro service B calls the micro services C and D, and in order to perform global exception handling, exception information of the micro service B, C, D needs to be defined in a detector module.
Taking the process of calling the micro service B by the micro service A as an example, the method comprises the following steps:
(1) the micro service A initiates remote micro service calling to the micro service B;
(2) the micro service B performs service processing according to the received instruction sent by the micro service A; if the business processing of the micro service B is error-free, response information is returned to the micro service A; if the error occurs, the microserver B calls a detector module of the global exception handling platform to carry out exception handling;
(3) the detector module generates spliced abnormal information and throws the information out;
(4) the spliced abnormal information is captured by the Spring frame section, and is returned to the micro-service B after being subjected to uniform abnormal packaging processing at the Spring frame section;
(5) the micro service B returns the packaged abnormal information to the micro service A;
(6) microservice a handles exceptions.
And adding a definition format of system exception information in a detector module. All the exception information is stored in the form of Map, key is the exception code, value is the content of the exception information.
1) And processing micro-service abnormal information:
defining a class BMircoServiceConstants of the micro-service B in a detector module, wherein the class BMircoServiceConstants are used for representing abnormal information of the micro-service B; defining a global static constant PE _ NOT _ EXIST, which represents an abnormal code which does NOT EXIST in PE equipment; defining a global Map structure for storing abnormal information; and storing the exception code and the exception information into the Map.
The method for processing the abnormal information of the micro-service B comprises the following steps: inputting a parameter exceptinonenum as an abnormal code, and error variable as a variable needing to be replaced in abnormal information; and calling a detector method in a detector module for processing, returning the packaged abnormal class of the micro service B, and finally throwing out the spliced abnormal information.
For example, the first variable in the microservice exception information before the splicing processing can be temporarily filled with% s, or other contents, and when the splicing processing is performed, the second variable is used for replacing the second variable errorVariable in the exception information. If the errorVariable is "PE 1" and the exceptinomessage is "device% s abnormal", the first abnormal information after the concatenation is "device PE1 abnormal".
2) Processing abnormal information of the public assembly:
and the detector module splices the abnormal information of the common assembly according to a predefined format to obtain second spliced abnormal information. The method specifically comprises the following steps: judging whether the public component abnormal information belongs to predefined identifiable public component abnormality, if so, packaging the public component abnormal information into second splicing abnormal information with an abnormal code and abnormal information, namely packaging the public component abnormal information into BaseException, and then throwing out a Spring frame section; if not, directly throwing out and processing by the corresponding micro-service.
Taking a database syntax exception as an example, the method comprises the following processing steps:
adding a Map in common constants of the class of common exceptions stored in the detector module, wherein the key of the Map is exception code, adding a global static constant, SQL _ SYNTAX _ ERROR, representing exception code, and putting the exception code into the Map, wherein value is 'database SYNTAX exception'.
And then directly executing a method handleException of common exception handler during common exception handling, wherein in the method, processing logic of 'syntax exception of a database' can be added, the logic is to firstly judge whether the exception is of MySQLSyntaxErrorException type, if so, a BaseException is defined and thrown out, and the content of the BaseException is the exception code and the exception information.
The definition, processing method and execution flow of the exception information of the micro service B calling the micro service C, D are similar and are not described again.
Example 4
Fig. 2 is a schematic diagram of a micro service group in which the global exception handling platform in embodiment 2 is located in a public network.
The micro-service is provided with an internal service calling interface facing the inside of the cluster and an external service interface facing the outside of the cluster, and the external service interface provides services to the public network through an API routing GateWay Spring Cloud GateWay, such as providing service interfaces for user login, registration and the like for an external client.
And the external client, such as a mobile phone terminal and a computer terminal, accesses the public network, and is connected to the micro-service cluster after the safety certification, the load balancing (Ribbon) or the service current limiting fusing (Sentiel) of the nginx reverse proxy and the API routing gateway. In the Spring Cloud-based micro-service architecture, an externally-facing service interface is exposed to a public network through an API (application programming interface) routing GateWay, an internally-facing service interface is shielded in the API routing GateWay, and micro-services among the internal micro-services are carried out in a micro-service cluster and are not exposed to the public network. All micro services register own information to Nacos, and a Nacos component is used for storing service information and providing a service list query interface for the outside. The Spring Cloud GateWay can query all the microservices at present through the Nacos.
In the global exception handling platform, a system development engineer writes exception information codes, and adds a definition format of system exception information and the like to a detector module. When the detector module processes the Exception of the public component, the Exception processing section of Spring defines the processing of Exception, and the processing content uses the public error result handling Exception (Exception ex) through Exception method at first.
If the defined BaseException is thrown, namely the exception is known, and the processing is finished, if the exception is not, the exception which is not processed exists in the system, and the code needs to be added for processing. Specifically, if the common component exception is a database exception, namely the common component exception is called, the common component exception is packaged into an identified custom BaseException exception and thrown out; and if the common component is not known to be abnormal, directly throwing the common component for respective micro-service processing.
In summary, the present invention builds a unified exception handling platform in a micro-service cluster scene, and combines the facet capability of a spring framework, where the spring framework includes an AOP module (Aspect organized Programming), i.e. a facet-Oriented Programming module, i.e. a logic or responsibility that is not related to a service but is called by the service module together is encapsulated on a facet, so as to reduce repeated codes of the system, reduce coupling degree between modules, and facilitate future operability and maintainability.
The present invention also provides a medium storing computer-executable instructions, which when executed by a processing unit, are configured to implement any one of the above-mentioned global exception handling methods.
The invention further provides an electronic device, which comprises a processing unit and a storage unit, and computer-executable instructions are stored in the storage unit, and when the instructions are executed by the processing unit, the instructions are used for realizing any one of the global exception handling methods.
The above description is only of the preferred embodiments of the present invention, and it should be noted that: it will be apparent to those skilled in the art that various modifications and adaptations can be made without departing from the principles of the invention and these are intended to be within the scope of the invention.
Claims (10)
1. A global exception handling method under a large-scale micro-service cluster scene is characterized by comprising the following steps:
acquiring all original abnormal information from the micro-service cluster;
classifying the acquired original abnormal information into micro-service abnormal information and public component abnormal information according to the difference of information formats, processing the micro-service abnormal information to obtain first splicing abnormal information, and splicing the public component abnormal information to obtain second splicing abnormal information;
sending the first splicing abnormal information and the second splicing abnormal information to a Spring frame tangent plane for performing abnormal packaging processing to obtain corresponding first packaging abnormal information and second packaging abnormal information;
and returning the first packaging abnormal information and the second packaging abnormal information to a sender of the corresponding original abnormal information.
2. The global exception handling method in the context of a large-scale microservice cluster according to claim 1, wherein classifying the obtained original exception information into microservice exception information and common component exception information comprises the steps of:
judging whether the original abnormal information is represented by a format comprising a micro-service name, an abnormal code, an abnormal message with a first variable and a second variable, if so, classifying the original abnormal information into the micro-service abnormal information, otherwise, classifying the original abnormal information into the public component abnormal information.
3. The global exception handling method in the context of a large-scale microservice cluster according to claim 2, wherein the method for processing microservice exception information to obtain first splicing exception information and for splicing common component exception information to obtain second splicing exception information comprises the steps of:
for micro-service abnormal information, judging a micro-service source with abnormal occurrence according to a micro-service name, and replacing a first variable in the micro-service abnormal information with a second variable to obtain first splicing abnormal information;
and for the abnormal information of the public component, splicing the abnormal information of the public component according to a predefined format to obtain second spliced abnormal information.
4. The global exception handling method in the context of a large-scale microservice cluster according to claim 1, wherein: the original abnormal information is generated by any micro service in the micro service cluster and is sent by the called micro service when the service calling has an error; or when the common component is abnormal, the micro-service accessing and discovering the common component is used for sending the abnormal micro-service.
5. The global exception handling method in the context of a large-scale microservice cluster according to claim 1, wherein: the original abnormal information, the first splicing abnormal information and the second splicing abnormal information are stored in a Map form, the key is the content of the abnormal code, the value is the content of the abnormal information, and the abnormal code is defined as a global static constant.
6. A global exception handling platform, comprising:
the device module is used for acquiring all original abnormal information from the micro-service cluster and classifying the acquired original abnormal information into micro-service abnormal information and common component abnormal information according to the difference of information formats; then processing the micro-service abnormal information to obtain first splicing abnormal information, and processing the public component abnormal information to obtain second splicing abnormal information;
the packaging module is used for sending the first splicing abnormal information and the second splicing abnormal information to a Spring frame tangent plane for performing abnormal packaging processing to obtain corresponding first packaging abnormal information and second packaging abnormal information;
and the feedback module is used for returning the first packaging abnormal information and the second packaging abnormal information to the corresponding sender of the original abnormal information.
7. The global exception handling platform of claim 6, wherein: the service module is used for receiving the abnormal information inquiry request and inquiring the abnormal information.
8. The global exception handling platform of claim 6, wherein: the device also comprises a storage module which is used for storing all original abnormal information, the first splicing abnormal information and the second splicing abnormal information.
9. A medium storing computer-executable instructions, characterized in that: the instructions, when executed by the processing unit, are for implementing the method of any one of claims 1 to 4.
10. An electronic device, characterized in that: comprising a processing unit and a storage unit, storing computer-executable instructions, which when executed by the processing unit, are adapted to carry out the method of any one of claims 1 to 4.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111653425.9A CN114296985A (en) | 2021-12-30 | 2021-12-30 | Global exception handling method and platform in large-scale micro-service cluster scene |
| PCT/CN2022/143273 WO2023125773A1 (en) | 2021-12-30 | 2022-12-29 | Global exception handling method and platform in large-scale micro-service cluster scenario |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111653425.9A CN114296985A (en) | 2021-12-30 | 2021-12-30 | Global exception handling method and platform in large-scale micro-service cluster scene |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114296985A true CN114296985A (en) | 2022-04-08 |
Family
ID=80973810
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111653425.9A Pending CN114296985A (en) | 2021-12-30 | 2021-12-30 | Global exception handling method and platform in large-scale micro-service cluster scene |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114296985A (en) |
| WO (1) | WO2023125773A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023125773A1 (en) * | 2021-12-30 | 2023-07-06 | 网络通信与安全紫金山实验室 | Global exception handling method and platform in large-scale micro-service cluster scenario |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110535902A (en) * | 2019-07-16 | 2019-12-03 | 平安普惠企业管理有限公司 | The processing method and electronic device of monitoring intelligent are realized based on micro services |
| CN110806921B (en) * | 2019-09-30 | 2023-02-07 | 烽火通信科技股份有限公司 | OVS (optical virtual system) abnormity alarm monitoring system and method |
| CN111061628B (en) * | 2019-11-21 | 2023-09-01 | 天翼数字生活科技有限公司 | Data analysis method, system, device, computer equipment and storage medium |
| CN111669425B (en) * | 2020-04-14 | 2022-12-09 | 福建天泉教育科技有限公司 | Method for monitoring microservice interface and storage medium |
| CN113190372B (en) * | 2021-05-24 | 2023-02-07 | 深圳赛安特技术服务有限公司 | Multi-source data fault processing method and device, electronic equipment and storage medium |
| CN113609012B (en) * | 2021-07-30 | 2024-03-29 | 南京控维通信科技有限公司 | Method and system for normalized processing back-end exception reporting |
| CN114296985A (en) * | 2021-12-30 | 2022-04-08 | 网络通信与安全紫金山实验室 | Global exception handling method and platform in large-scale micro-service cluster scene |
-
2021
- 2021-12-30 CN CN202111653425.9A patent/CN114296985A/en active Pending
-
2022
- 2022-12-29 WO PCT/CN2022/143273 patent/WO2023125773A1/en unknown
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023125773A1 (en) * | 2021-12-30 | 2023-07-06 | 网络通信与安全紫金山实验室 | Global exception handling method and platform in large-scale micro-service cluster scenario |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023125773A1 (en) | 2023-07-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8984535B2 (en) | System and method for facilitating the exchange of information among applications | |
| EP1025507B1 (en) | Combined internet and data access system | |
| US9229998B2 (en) | Method and system for exchanging information between back-end and front-end systems | |
| US7596623B2 (en) | Configurable connector | |
| US7346893B2 (en) | Exchange infrastructure system and method | |
| US20080282222A1 (en) | Xml push and remote execution of a wireless applications | |
| AU2002322282A1 (en) | Integrating enterprise support systems | |
| CN112540948A (en) | Route management through event stream processing cluster manager | |
| US20210034338A1 (en) | Communications Enablement Platform, System, and Method | |
| US20070266035A1 (en) | Methods, Systems and Computer Program Products for Web Service Interaction with a Resource Management System | |
| CN108446105A (en) | A kind of Lightweight AP I Server Development Frameworks and development approach | |
| CN113630310B (en) | Distributed high-availability gateway system | |
| CN111552568A (en) | Cloud service calling method and device | |
| WO2023125773A1 (en) | Global exception handling method and platform in large-scale micro-service cluster scenario | |
| AU2003223040B2 (en) | Exchange infrastructure system and method | |
| US20040243693A1 (en) | Inbound connector | |
| CN114416314B (en) | Service arrangement method based on API gateway | |
| US20040105537A1 (en) | Generic service component for message formatting | |
| Rojas et al. | Web and Telco Service Integration: A Dynamic and Adaptable Approach | |
| CN115225637A (en) | Cloud data display method and device, storage medium and electronic equipment | |
| CN113225249A (en) | Message processing method, system, device and medium | |
| CN112667247A (en) | Service management method, system, terminal and storage medium | |
| CN117527895A (en) | HTTP request processing method and system based on AOP | |
| CN116192440A (en) | Security arrangement and automatic response method and device, electronic equipment and storage medium | |
| CN116909657A (en) | Method for calling class method in dubbo application, dubbo server and 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 |