CN111241112B - Micro-service call supervision system and method for ensuring idempotent - Google Patents
Micro-service call supervision system and method for ensuring idempotent Download PDFInfo
- Publication number
- CN111241112B CN111241112B CN201911380810.3A CN201911380810A CN111241112B CN 111241112 B CN111241112 B CN 111241112B CN 201911380810 A CN201911380810 A CN 201911380810A CN 111241112 B CN111241112 B CN 111241112B
- Authority
- CN
- China
- Prior art keywords
- transaction
- calling
- micro
- service
- module
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a micro-service call supervision system and method for ensuring idempotent, comprising a transaction application module, a transaction call module, a transaction follow-up result access module and a transaction management module, wherein the transaction application module is used for generating a transaction number before micro-service call, the transaction call module is used for processing each micro-service call, the transaction follow-up result access module is used for processing micro-service with longer time, the transaction management module is used for managing all micro-service calls, checking details of each call and providing a processing method aiming at abnormal call conditions; the method and the device ensure strict idempotent of the micro-service, shield the database operation consistency problem caused by calling among different systems and different databases, and avoid the problem that a calling end always waits or even overtime occurs due to overlong micro-service processing time.
Description
Technical Field
The disclosure relates to the technical field of micro-service invocation, in particular to a micro-service invocation supervision system and method for ensuring idempotent.
Background
The statements in this section merely provide background information related to the present disclosure and may not necessarily constitute prior art.
Under the micro-service architecture, the original single-body application and the database are split into a plurality of micro-service applications and a plurality of databases, the code logic call in the original single-body application is changed into the micro-service call among the plurality of applications, and the service data is saved by the single database and is changed into the sub-database sub-table. The calling end and the providing end of the code call in the single-body type application have no factors such as network, database separation and the like, the consistency of database operation at the two ends is ensured, and the providing end does not need to ensure idempotent operation.
The inventor discovers that under the micro-service architecture, the calling ends are positioned in different databases, the situation that the processing results of the providing ends cannot be fed back to the calling ends is easily caused by factors such as a network and the like, and in the situation, the calling ends can only initiate the calling again to acquire the processing results again, so that the consistency of the operation of the databases at the two ends can be ensured, the provider needs to ensure idempotent, each micro-service of a developer of the micro-service is ensured to be idempotent, and the difficulty and the workload of micro-service development are certainly increased.
Disclosure of Invention
In order to solve the defects of the prior art, the present disclosure provides a micro-service call supervision system and method for ensuring idempotent, which ensure strict idempotent of micro-services and shield database operation consistency problems caused by call among different systems and different databases.
In order to achieve the above purpose, the present disclosure adopts the following technical scheme:
a first aspect of the present disclosure provides a micro-service invocation monitoring system that ensures idempotent.
A micro-service call supervision system for ensuring idempotent comprises a transaction application module and a transaction call module;
the transaction application module comprises a calling end transaction application module and a providing end transaction application module, when the calling end initiates a calling application, the calling end initiates an application to the providing end transaction application module through the calling end transaction application module, the providing end transaction application module returns the generated transaction number to the calling end, and the calling end assembles calling parameters according to the transaction number;
the transaction calling module comprises a calling end transaction calling module and a providing end transaction calling module, the calling end initiates micro-service calling according to calling parameters through the calling end transaction calling module, and the providing end transaction calling module receives a calling request and performs transaction information verification;
if the transaction is the first occurrence, the transaction calling module at the providing end stores the transaction information, calls the micro-service implementation class, stores the transaction result, and returns the transaction result to the calling end through the transaction calling module at the calling end;
if the transaction does not happen for the first time, the transaction calling module of the providing end acquires transaction information, judges whether the transaction is completed, returns a transaction result to the calling end through the transaction calling module of the calling end if the transaction is completed, calls a micro-service implementation class and stores the transaction result if the transaction is not completed, and returns the transaction result to the calling end through the transaction calling module of the calling end.
As some possible implementation manners, the call supervision system further includes a transaction follow-up result access module, configured to receive a transaction follow-up result of the providing end, the calling end sends a call request of the transaction follow-up result to the providing end, the providing end determines whether the follow-up result is set, if the transaction is completed and the follow-up result is already set, the transaction follow-up result access module returns the follow-up result to the calling end, and the calling end processes according to the follow-up result; and if the transaction is not completed or the subsequent result is not set, the calling end waits for the opportunity to initiate the subsequent result acquisition request again.
As some possible implementations, the call supervision system further includes a transaction management module, configured to manage all micro-service transactions, view details of each transaction, and give a solution for a transaction anomaly.
As some possible implementations, the transaction number is used to mark one micro service transaction, and one micro service transaction may make multiple micro service calls, where the transaction number of each call is the same.
As some possible implementations, idempotent nature of the micro-service call is ensured by checking the transaction information within the provider transaction call module.
A second aspect of the present disclosure provides a method of ensuring idempotent micro-service invocation.
A micro-service calling method for ensuring idempotent comprises the following steps:
step 601: when the calling end initiates a calling application, firstly, an application is initiated to a transaction application module of the providing end through a transaction application module of the calling end, and the transaction application module of the providing end returns the generated transaction number;
step 602: the calling terminal assembles calling parameters according to the transaction number;
step 603: the calling end initiates micro-service call;
step 604: the providing end is connected to the call request, the micro-service transaction call module at the providing end performs transaction information verification, and verifies whether the transaction occurs for the first time, if so, the step is processed by the step 605, and if not, the step is processed by the step 609, wherein the exception of the previous transaction call is indicated;
step 605: the transaction happens for the first time, and transaction information is saved and used for judging whether the transaction happens or not in step 604;
step 606: calling a micro-service implementation class to obtain a transaction result;
step 607: storing the transaction result;
step 608: returning a transaction result;
step 609: when the transaction does not occur for the first time, transaction information is acquired;
step 610: whether the transaction is completed or not is judged, the step is used for judging whether the last call generates a transaction result or not when the transaction is not called for the first time, if the last call transaction is completed, the step is switched to 608, and if the transaction is not completed, the step is switched to 606 to resume the transaction processing.
As some possible implementation manners, after the providing end completes the service processing, the providing end sets a subsequent result of the micro-service transaction, and the acquisition of the subsequent result is initiated by the calling end, which specifically includes:
step 701: the calling end initiates a request to acquire a subsequent result;
step 702: the providing end judges whether the subsequent result is set or not, if the transaction is completed and the subsequent result is set, the process goes to step 703, and if the transaction is not completed or the subsequent result is not set, the process returns to step 701, and the calling end waits for the opportunity to initiate the subsequent result acquisition request again;
step 703: obtaining a subsequent result;
step 704: and the calling end processes according to the subsequent result.
As some possible implementations, all the micro-service transactions are managed in a centralized and visualized manner, the details of each transaction are checked in real time, and an exception solution is given for the case of transaction exceptions.
As some possible implementations, a micro-service transaction may have multiple micro-service calls, each call having the same transaction number, and the idempotent nature of the micro-service call is ensured by checking the transaction information in the provider transaction call module.
Compared with the prior art, the beneficial effects of the present disclosure are:
1. the content disclosed by the disclosure is combined with the micro-service transaction calling module through the micro-service transaction application module, so that strict idempotent of micro-service is ensured, and the problem of database operation consistency caused by calling among different systems and different databases is shielded.
2. The micro-service transaction follow-up module is arranged, so that a processing mode for avoiding calling party waiting and calling overtime is provided for micro-services with longer processing period, and the problem that a calling end always waits or even overtime occurs due to overlong micro-service processing time is avoided.
3. The micro service transaction management module is arranged, so that convenient visual management and control is provided for the call of the idempotent micro service, and the call condition can be conveniently and directly checked and the call abnormality problem can be processed.
Drawings
Fig. 1 is a timing chart of a micro service invocation procedure and setting acquisition of subsequent results provided in embodiment 1 of the present disclosure.
Fig. 2 is a flow chart of a micro service transaction calling process provided in embodiment 1 of the present disclosure.
Fig. 3 is a flowchart illustrating a procedure for obtaining and calling a subsequent result of a micro service transaction according to embodiment 1 of the present disclosure.
Detailed Description
It should be noted that the following detailed description is illustrative and is intended to provide further explanation of the present disclosure. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
It is noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of exemplary embodiments in accordance with the present disclosure. As used herein, the singular is also intended to include the plural unless the context clearly indicates otherwise, and furthermore, it is to be understood that the terms "comprises" and/or "comprising" when used in this specification are taken to specify the presence of stated features, steps, operations, devices, components, and/or combinations thereof.
Embodiments of the present disclosure and features of embodiments may be combined with each other without conflict.
Example 1:
the embodiment 1 of the disclosure provides a micro-service call supervision system for ensuring idempotent, as shown in fig. 1, comprising a transaction application module and a transaction call module;
the transaction application module comprises a calling end transaction application module and a providing end transaction application module, when the calling end initiates a calling application, the calling end initiates an application to the providing end transaction application module through the calling end transaction application module, the providing end transaction application module returns the generated transaction number to the calling end, and the calling end assembles calling parameters according to the transaction number;
the transaction calling module comprises a calling end transaction calling module and a providing end transaction calling module, the calling end initiates micro-service calling according to calling parameters through the calling end transaction calling module, and the providing end transaction calling module receives a calling request and performs transaction information verification;
if the transaction is the first occurrence, the transaction calling module at the providing end stores the transaction information, calls the micro-service implementation class, stores the transaction result, and returns the transaction result to the calling end through the transaction calling module at the calling end;
if the transaction does not happen for the first time, the transaction calling module of the providing end acquires transaction information, judges whether the transaction is completed, returns a transaction result to the calling end through the transaction calling module of the calling end if the transaction is completed, calls a micro-service implementation class and stores the transaction result if the transaction is not completed, and returns the transaction result to the calling end through the transaction calling module of the calling end.
The system comprises a providing end, a transaction follow-up result access module, a calling end and a calling end, wherein the providing end is used for receiving a transaction follow-up result of the providing end, the calling end is used for sending a calling request of the transaction follow-up result to the providing end, the providing end judges whether the follow-up result is set or not, if the transaction is completed and the follow-up result is set, the transaction follow-up result access module returns the follow-up result to the calling end, and the calling end processes according to the follow-up result; and if the transaction is not completed or the subsequent result is not set, the calling end waits for the opportunity to initiate the subsequent result acquisition request again.
The transaction management module is used for managing all the micro-service transactions, checking the details of each transaction and giving a solution to the abnormal situation of the transaction.
The transaction number is used for marking one-time micro-service transaction, the micro-service transaction can be subjected to multiple times of micro-service call, the transaction number of each call is the same, and idempotency of the micro-service call is ensured by checking transaction information in a transaction call module at a providing end.
Example 2:
the embodiment 2 of the disclosure provides a micro-service calling method for ensuring idempotent, wherein a calling end initiates a micro-service transaction to the end of the transaction is divided into two processes, namely micro-service transaction calling and subsequent result acquisition.
The process of micro service transaction call is shown in fig. 2, and specifically is as follows:
step 201: the service calling end applies for the transaction number from the micro-service transaction application module and stores the transaction number.
In the process described in detail in fig. 1, when a calling end initiates a calling application 101, firstly, the calling end initiates an application to a transaction application module of a providing end through a transaction application module of the calling end, and the transaction application module of the providing end returns a generated transaction number;
step 202: the calling terminal assembles calling parameters according to the transaction number;
step 203: the calling end initiates micro-service call;
step 204: the providing end is connected with the calling request, and the micro-service transaction calling module performs transaction information verification. Checking whether the transaction is first occurrence, if so, turning to step 205 for processing, and if not, turning to step 209 for processing, wherein the transaction call is abnormal before the transaction call is indicated;
step 205: the transaction happens for the first time, and transaction information is saved and used for judging whether the transaction happens or not in the step 204;
step 206: calling a micro-service implementation class, and taking a transaction result;
step 207: storing the transaction result;
step 208: returning a transaction result;
step 209: when the transaction does not occur for the first time, transaction information is acquired;
step 210: whether the transaction is completed or not is judged, the step is carried out when the transaction is not called for the first time, and is used for judging whether the last call has generated a transaction result or not, if the last call transaction is completed, the step is shifted to 208, and if the transaction is not completed, the step is shifted to 206 to carry out transaction processing again.
The setting of the subsequent results of the micro-service transaction is set by the service provider, and the process occurs after the provider completes the business processing.
Acquisition of subsequent results is initiated by the calling end, such as request 102 in FIG. 1.
The process of acquisition is as shown in fig. 3:
step 301: the calling end initiates a request to acquire a subsequent result;
step 302: the providing end judges whether the subsequent result is set, if the transaction is completed and the subsequent result is set, the step is shifted to 303, and if the transaction is not completed or the subsequent result is not set, the step is returned to 301, and the calling end waits for the opportunity to initiate the subsequent result acquisition request again;
step 303: obtaining a subsequent result;
step 304: and the calling end processes according to the subsequent result.
The foregoing description of the preferred embodiments of the present disclosure is provided only and not intended to limit the disclosure so that various modifications and changes may be made to the present disclosure by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present disclosure should be included in the protection scope of the present disclosure.
Claims (6)
1. The micro-service call supervision system for ensuring idempotent is characterized by comprising a transaction application module and a transaction call module;
the transaction application module comprises a calling end transaction application module and a providing end transaction application module, when the calling end initiates a calling application, the calling end initiates an application to the providing end transaction application module through the calling end transaction application module, the providing end transaction application module returns the generated transaction number to the calling end, and the calling end assembles calling parameters according to the transaction number;
the transaction calling module comprises a calling end transaction calling module and a providing end transaction calling module, the calling end initiates micro-service calling according to calling parameters through the calling end transaction calling module, and the providing end transaction calling module receives a calling request and performs transaction information verification;
if the transaction is the first occurrence, the transaction calling module at the providing end stores the transaction information, calls the micro-service implementation class, stores the transaction result, and returns the transaction result to the calling end through the transaction calling module at the calling end;
if the transaction does not happen for the first time, the transaction calling module of the providing end acquires transaction information, judges whether the transaction is completed or not, returns a transaction result to the calling end through the transaction calling module of the calling end if the transaction is completed, calls a micro-service implementation class and stores the transaction result if the transaction is not completed, and returns the transaction result to the calling end through the transaction calling module of the calling end;
the transaction number is used for marking one-time micro-service transaction, and one-time micro-service transaction can generate multiple micro-service calls, and the transaction numbers of each call are the same;
idempotent nature of the micro-service call is ensured by verification of transaction information within the provider transaction call module.
2. The system of claim 1, further comprising a transaction follow-up result access module for receiving a transaction follow-up result from the provider, the caller sending a call request for the transaction follow-up result to the provider, the provider determining if the follow-up result is set, the transaction follow-up result access module returning the follow-up result to the caller if the transaction is completed and the follow-up result is set, the caller processing according to the follow-up result; and if the transaction is not completed or the subsequent result is not set, the calling end waits for the opportunity to initiate the subsequent result acquisition request again.
3. The idempotent guaranteed micro service invocation and administration system according to claim 1, further comprising a transaction management module for managing all micro service transactions, looking at the details of each transaction, and giving a solution to the case of transaction anomalies.
4. A method for invoking a micro-service guaranteeing idempotent, comprising the steps of:
step 601: when the calling end initiates a calling application, firstly, an application is initiated to a transaction application module of the providing end through a transaction application module of the calling end, and the transaction application module of the providing end returns the generated transaction number;
step 602: the calling terminal assembles calling parameters according to the transaction number;
step 603: the calling end initiates micro-service call;
step 604: the providing end is connected to the call request, the micro-service transaction call module at the providing end performs transaction information verification, and verifies whether the transaction occurs for the first time, if so, the step is processed by the step 605, and if not, the step is processed by the step 609, wherein the exception of the previous transaction call is indicated;
step 605: the transaction happens for the first time, and transaction information is saved and used for judging whether the transaction happens or not in step 604;
step 606: calling a micro-service implementation class to obtain a transaction result;
step 607: storing the transaction result;
step 608: returning a transaction result;
step 609: when the transaction does not occur for the first time, transaction information is acquired;
step 610: judging whether the transaction is completed or not, when the transaction is not called for the first time, judging whether the last time the call has generated a transaction result or not, if the last time the call has been completed, turning to 608, and if the transaction is not completed, turning to 606 to re-process the transaction;
the micro-service call can be carried out for a plurality of times, the transaction numbers of each call are the same, and the idempotency of the micro-service call is ensured by checking the transaction information in the transaction call module at the providing end.
5. The method for invoking micro-services for ensuring idempotent as claimed in claim 4, wherein after the provider completes the service processing, the provider sets the subsequent results of the micro-service transaction, and the acquisition of the subsequent results is initiated by the caller, specifically:
step 701: the calling end initiates a request to acquire a subsequent result;
step 702: the providing end judges whether the subsequent result is set or not, if the transaction is completed and the subsequent result is set, the process goes to step 703, and if the transaction is not completed or the subsequent result is not set, the process returns to step 701, and the calling end waits for the opportunity to initiate the subsequent result acquisition request again;
step 703: obtaining a subsequent result;
step 704: and the calling end processes according to the subsequent result.
6. The method for invoking micro-services guaranteeing idempotent as claimed in claim 4, wherein all micro-service transactions are managed in a centralized and visualized manner, the details of each transaction are checked in real time, and an exception solution is given for the case of transaction exceptions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911380810.3A CN111241112B (en) | 2019-12-27 | 2019-12-27 | Micro-service call supervision system and method for ensuring idempotent |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911380810.3A CN111241112B (en) | 2019-12-27 | 2019-12-27 | Micro-service call supervision system and method for ensuring idempotent |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111241112A CN111241112A (en) | 2020-06-05 |
| CN111241112B true CN111241112B (en) | 2023-05-23 |
Family
ID=70868871
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911380810.3A Active CN111241112B (en) | 2019-12-27 | 2019-12-27 | Micro-service call supervision system and method for ensuring idempotent |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111241112B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114663226A (en) * | 2020-12-22 | 2022-06-24 | 网联清算有限公司 | Transaction request processing method and device and transaction transfer system |
| CN113744056A (en) * | 2021-09-07 | 2021-12-03 | 辽宁振兴银行股份有限公司 | Online transaction idempotent method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3376361A2 (en) * | 2017-10-19 | 2018-09-19 | Pure Storage, Inc. | Ensuring reproducibility in an artificial intelligence infrastructure |
| CN109165084A (en) * | 2018-08-20 | 2019-01-08 | 四川长虹电器股份有限公司 | Distributed transaction management method based on state stream |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7430559B2 (en) * | 2005-09-21 | 2008-09-30 | Microsoft Corporation | Generalized idempotent requests |
| US8984170B2 (en) * | 2011-09-09 | 2015-03-17 | Oracle International Corporation | Idempotence for database transactions |
| CN106921645B (en) * | 2016-06-28 | 2021-04-20 | 创新先进技术有限公司 | Information publishing method, client and server |
| CN106648936B (en) * | 2016-12-29 | 2020-09-22 | Tcl科技集团股份有限公司 | Cooperative processing method, system and server based on microservice |
| CN107580032B (en) * | 2017-08-23 | 2020-04-24 | 阿里巴巴集团控股有限公司 | Data processing method, device and equipment |
| CN109376155B (en) * | 2018-11-06 | 2021-07-20 | 泰康保险集团股份有限公司 | ID generation method and device, storage medium and electronic device |
| CN109542639B (en) * | 2018-11-06 | 2021-05-11 | 用友网络科技股份有限公司 | Processing method and processing device for guaranteeing consistency of microservice calling data |
| CN109697113B (en) * | 2018-12-29 | 2021-06-01 | 广州方硅信息技术有限公司 | Method, device and equipment for requesting retry and readable storage medium |
| CN110266799B (en) * | 2019-06-21 | 2022-07-05 | 国网山西省电力公司忻州供电公司 | Method for realizing idempotency based on cache |
-
2019
- 2019-12-27 CN CN201911380810.3A patent/CN111241112B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3376361A2 (en) * | 2017-10-19 | 2018-09-19 | Pure Storage, Inc. | Ensuring reproducibility in an artificial intelligence infrastructure |
| CN109165084A (en) * | 2018-08-20 | 2019-01-08 | 四川长虹电器股份有限公司 | Distributed transaction management method based on state stream |
Non-Patent Citations (3)
| Title |
|---|
| "一种数据同步系统的设计与实现";曾泽堂;《中国优秀硕士学位论文全文数据库 信息科技辑》(第07期);全文 * |
| "微服务的重试和幂等";October;《https://blog.csdn.net/weixin_41715077/article/details/83792542》;全文 * |
| Boyer, F., Etchevers, X., de Palma, N., Tao, X.." Architecture-Based Automated Updates of Distributed Microservices".《International Conference on Service-Oriented Computing》.2018,全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111241112A (en) | 2020-06-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111241112B (en) | Micro-service call supervision system and method for ensuring idempotent | |
| CN111277639B (en) | Method and device for maintaining data consistency | |
| CN108694104A (en) | A kind of interface function contrast test method, apparatus, electronic equipment and storage medium | |
| CN110225078B (en) | Application service updating method, system and terminal equipment | |
| CN109242460B (en) | Payment system based on multiple payment channels and account checking method thereof | |
| CN109885612B (en) | Synchronous validation method and device for intelligent contracts of block chains | |
| US20200379748A1 (en) | Upgrading method and apparatus | |
| US11734057B2 (en) | Method and apparatus for processing a service of an abnormal server | |
| CN110580556B (en) | Data processing method and system and processor | |
| CN108664343B (en) | State calling method and device for micro-service | |
| CN112131188A (en) | Batch file distribution processing method and device | |
| CN107277108B (en) | Method, device and system for processing messages at nodes of block chain | |
| US10861021B2 (en) | State value indexing into an action database | |
| CN110830662B (en) | Outbound telephone data generation method and device | |
| CN113592645A (en) | Data verification method and device | |
| CN111580998A (en) | RPC calling method of multiple tenants in SaaS service mode | |
| CN110543470A (en) | Message early warning method and device, storage medium and electronic device | |
| CN112261072A (en) | Service calling method, device, equipment and storage medium | |
| CN112965737A (en) | Service function calling method and device | |
| CN114189934B (en) | Repeated paging determining method, device, equipment and medium | |
| US20140119530A1 (en) | System and method for efficiently managing large contact centers | |
| CN110661792B (en) | Service ordered calling method and device, electronic equipment and storage medium | |
| CN114327602B (en) | Information processing method, device, electronic equipment and storage medium | |
| CN113778657B (en) | Data processing method and device | |
| CN116991630A (en) | Retry execution method, retry execution device, electronic device, and computer-readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |