CN111241112A - Micro-service call supervision system and method for guaranteeing idempotent - Google Patents
Micro-service call supervision system and method for guaranteeing idempotent Download PDFInfo
- Publication number
- CN111241112A CN111241112A CN201911380810.3A CN201911380810A CN111241112A CN 111241112 A CN111241112 A CN 111241112A CN 201911380810 A CN201911380810 A CN 201911380810A CN 111241112 A CN111241112 A CN 111241112A
- Authority
- CN
- China
- Prior art keywords
- transaction
- calling
- module
- micro
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
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)
- Development Economics (AREA)
- Technology Law (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Debugging And Monitoring (AREA)
Abstract
The utility model provides a micro-service call supervision system and method for ensuring idempotency, which comprises a transaction application module, a transaction call module, a transaction subsequent result access module and a transaction management module, wherein the transaction application module is used for generating transaction numbers before micro-service call, the transaction call module is used for processing each micro-service call, the transaction subsequent result access module is used for processing the micro-service with longer processing time, the transaction management module is used for managing all micro-service calls, checking the details of each call and giving a processing method aiming at the abnormal call condition; the method and the device ensure strict idempotent of the micro-service, shield the problem of consistency of database operation caused by calling among different systems and different databases, and avoid the problem that the calling end waits all the time or even overtime because of overlong micro-service processing time.
Description
Technical Field
The disclosure relates to the technical field of micro-service invocation, and in particular relates to a monitoring system and a method for ensuring idempotent micro-service invocation.
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 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 application is changed into the micro-service call among the plurality of applications, and the service data is stored in the single database and is changed into the sub-database and sub-table. The factors such as network and library division do not exist between the calling end and the providing end of the code calling in the monolithic application, the consistency of database operation at two ends is ensured, and the providing end does not need to ensure operation power and the like.
The inventor of the present disclosure finds that, under a micro-service architecture, two calling ends are located in different databases, and a condition that a processing result of a providing end cannot be fed back to the calling end is easily influenced by factors such as a network between the calling end and the providing end, and in this condition, the calling end can only re-initiate calling to obtain the processing result again, so that consistency of operations of the databases at the two ends can be ensured, and thus, a provider needs to ensure power and the like, and each micro-service of a developer of the micro-service ensures power and the like, thereby undoubtedly increasing difficulty and workload of micro-service development.
Disclosure of Invention
In order to solve the defects of the prior art, the invention provides a micro-service call supervision system and method for ensuring power, which ensure strict power of micro-service and shield the problem of database operation consistency caused by calling among different systems and different databases.
In order to achieve the purpose, the following technical scheme is adopted in the disclosure:
a first aspect of the present disclosure provides an idempotent microservice invocation supervisory system.
A micro-service call supervision system for guaranteeing idempotency 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 transaction application module initiates an application to the providing end transaction application module, the providing end transaction application module returns a generated transaction number to the calling end, and the calling end assembles a calling parameter 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 checks transaction information;
if the transaction occurs for the first time, the providing end transaction calling module 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 calling end transaction calling module;
if the transaction does not occur for the first time, the providing terminal transaction calling module acquires transaction information and judges whether the transaction is completed or not, if the transaction is completed in the last time, the transaction result is returned to the calling terminal through the calling terminal transaction calling module, if the transaction is not completed, the micro-service implementation class is called and the transaction result is stored, and the transaction result is returned to the calling terminal through the calling terminal transaction calling module.
As some possible implementation manners, the calling monitoring system further includes a transaction subsequent result access module, configured to receive a transaction subsequent result of the providing end, send a calling request of the transaction subsequent result to the providing end by the calling end, the providing end determines whether the subsequent result is set, if the transaction is completed and the subsequent result is set, the transaction subsequent result access module returns the subsequent result to the calling end, and the calling end processes according to the subsequent result; if the transaction is not completed or the subsequent result is not set, the calling terminal waits for the opportunity to initiate the subsequent result acquisition request again.
As some possible implementation manners, the call supervision system further comprises a transaction management module, which is used for managing all micro-service transactions, checking the details of each transaction and giving a solution to the abnormal transaction condition.
As some possible implementations, the transaction number is used to mark one microservice transaction, and one microservice transaction may occur with multiple microservice invocations, with the same transaction number for each invocation.
As some possible implementations, the idempotency of microservice invocation is guaranteed by providing a check of the transaction information within the end transaction invocation module.
A second aspect of the disclosure provides an idempotent microservice invocation method.
A guaranteed idempotent microservice calling method comprises the following steps:
step 601: when a calling end initiates a calling application, firstly, a transaction application module of the calling end initiates an application to a transaction application module of a providing end, and the transaction application module of the providing end returns a generated transaction number;
step 602: the calling end assembles calling parameters according to the transaction number;
step 603: the calling end initiates micro-service calling;
step 604: the provider end is connected to the calling request, the provider end micro-service transaction calling module checks the transaction information, if the transaction is checked to occur for the first time, the 605 step is carried out for processing, if the transaction is not caused for the first time, the exception of the previous transaction calling is shown, and the 609 step is carried out for processing;
step 605: when the transaction occurs for the first time, the transaction information is stored and used for step 604 to judge whether the transaction occurs;
step 606: calling the micro-service implementation class to obtain a transaction result;
step 607: saving the transaction result;
step 608: returning a transaction result;
step 609: when the transaction does not occur for the first time, transaction information is obtained;
step 610: and judging whether the transaction is finished, wherein the step is performed when the call is not called for the first time, and is used for judging whether the transaction result is generated by the last call, if the transaction is finished by the last call, turning to the step 608, and if the transaction is not finished, turning to the step 606 to perform transaction processing again.
As some possible implementation manners, after the providing end completes the service processing, the providing end sets the subsequent result of the micro-service transaction, and the acquisition of the subsequent result is initiated by the invoking end, specifically:
step 701: the calling terminal initiates a request to obtain a subsequent result;
step 702: 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 step 703, if the transaction is not completed or the subsequent result is not set, the step is returned to step 701, and the calling end waits for the opportunity to initiate the subsequent result acquisition request again;
step 703: acquiring a subsequent result;
step 704: and the calling end processes according to the subsequent result.
As some possible implementation modes, all micro-service transactions are managed in a centralized and visual mode, details of each transaction are checked in real time, and an exception solution is given according to the abnormal condition of the transaction.
As some possible implementation modes, one micro-service transaction can be carried out for a plurality of times of micro-service invocation, the transaction number of each invocation is the same, and the idempotency of the micro-service invocation is ensured by checking the transaction information in the transaction invocation module of the providing end.
Compared with the prior art, the beneficial effect of this disclosure is:
1. the micro-service transaction application module is combined with the micro-service transaction calling module, so that strict idempotent of the micro-service is guaranteed, and the problem of database operation consistency caused by calling among different systems and different databases is solved.
2. According to the method and the device, the follow-up module of the micro-service transaction is arranged, a processing mode of avoiding waiting of a calling party and overtime calling is provided for the micro-service with a longer processing period, and the problem that the calling party always waits even overtime due to overlong micro-service processing time is avoided.
3. According to the method and the system, the micro-service transaction management module is arranged, convenient and visual management and control are provided for calling of the power micro-service, and calling conditions can be conveniently and directly checked and abnormal calling problems can be processed.
Drawings
Fig. 1 is a timing diagram of a micro-service invocation process and a setting of obtaining a subsequent result provided in embodiment 1 of the present disclosure.
Fig. 2 is a schematic diagram of a micro service transaction invocation process provided in embodiment 1 of the present disclosure.
Fig. 3 is a schematic flow chart of a process for acquiring and calling a subsequent result of a microservice transaction according to embodiment 1 of the present disclosure.
Detailed Description
It should be noted that the following detailed description is exemplary and is intended to provide further explanation of the 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 example embodiments according to the present disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, and it should be understood that when the terms "comprises" and/or "comprising" are used in this specification, they specify the presence of stated features, steps, operations, devices, components, and/or combinations thereof, unless the context clearly indicates otherwise.
The embodiments and features of the embodiments in the present disclosure may be combined with each other without conflict.
Example 1:
the embodiment 1 of the present disclosure provides a micro-service invocation monitoring system for guaranteeing idempotent, as shown in fig. 1, including a transaction application module and a transaction invocation 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 transaction application module initiates an application to the providing end transaction application module, the providing end transaction application module returns a generated transaction number to the calling end, and the calling end assembles a calling parameter 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 checks transaction information;
if the transaction occurs for the first time, the providing end transaction calling module 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 calling end transaction calling module;
if the transaction does not occur for the first time, the providing terminal transaction calling module acquires transaction information and judges whether the transaction is completed or not, if the transaction is completed in the last time, the transaction result is returned to the calling terminal through the calling terminal transaction calling module, if the transaction is not completed, the micro-service implementation class is called and the transaction result is stored, and the transaction result is returned to the calling terminal through the calling terminal transaction calling module.
The transaction subsequent result access module is used for receiving the transaction subsequent result of the providing end, the calling end sends a calling request of the transaction subsequent result to the providing end, the providing end judges whether the subsequent result is set, if the transaction is completed and the subsequent result is set, the transaction subsequent result access module returns the subsequent result to the calling end, and the calling end processes according to the subsequent result; if the transaction is not completed or the subsequent result is not set, the calling terminal waits for the opportunity to initiate the subsequent result acquisition request again.
The system also comprises a transaction management module which is used for managing all micro-service transactions, checking the details of each transaction and giving a solution for the abnormal condition of the transaction.
The transaction number is used for marking one-time micro-service transaction, the one-time micro-service transaction can be called for multiple times, the transaction number called for each time is the same, and the idempotency of the micro-service calling is ensured by checking the transaction information in the transaction calling module of the providing end.
Example 2:
the embodiment 2 of the present disclosure provides a micro service invoking method for guaranteeing idempotent, in which an invoking end initiates a micro service transaction to end the transaction and is divided into two processes, one is micro service transaction invoking and the other is subsequent result obtaining.
The micro service transaction invoking process, as shown in fig. 2, specifically includes:
step 201: and the service calling terminal applies for the transaction number to the micro-service transaction application module and stores the transaction number.
In fig. 1, the process is described in detail, when a calling end initiates a calling application 101, first, a transaction application module of the calling end initiates an application to a transaction application module of a providing end, and the transaction application module of the providing end returns a generated transaction number;
step 202: the calling end assembles calling parameters according to the transaction number;
step 203: the calling end initiates micro-service calling;
step 204: the providing end is connected to the calling request, and the micro-service transaction calling module checks the transaction information. Checking whether the transaction occurs for the first time or not, if so, turning to the step 205 for processing, and if not, indicating that the previous transaction call is abnormal, turning to the step 209 for processing;
step 205: when the transaction occurs for the first time, storing the transaction information for step 204 to judge whether the transaction occurs;
step 206: calling the micro-service implementation class to obtain a transaction result;
step 207: saving the transaction result;
step 208: returning a transaction result;
step 209: when the transaction does not occur for the first time, transaction information is obtained;
step 210: and judging whether the transaction is finished, wherein the step is performed when the call is not called for the first time, and is used for judging whether the transaction result is generated by the last call, if the transaction is finished by the last call, the step is shifted to the step 208, and if the transaction is not finished, the step is shifted to the step 206 to perform transaction processing again.
The setting of the follow-up result of the micro service transaction is set by the service providing terminal, and the process occurs after the providing terminal completes the service processing.
The acquisition of the subsequent result is initiated by the calling end, such as request 102 in fig. 1.
The process of acquisition is shown in fig. 3:
step 301: the calling terminal initiates a request to obtain a subsequent result;
step 302: the providing terminal judges whether the subsequent result is set, if the transaction is completed and the subsequent result is set, the step is turned to 303, if the transaction is not completed or the subsequent result is not set, the step is returned to 301, and the calling terminal waits for the opportunity to initiate the subsequent result acquisition request again;
step 303: acquiring a subsequent result;
step 304: and the calling end processes according to the subsequent result.
The above description is only a preferred embodiment of the present disclosure and is not intended to limit the present disclosure, and various modifications and changes may be made to the present disclosure by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present disclosure should be included in the protection scope of the present disclosure.
Claims (9)
1. A micro-service call supervision system for guaranteeing idempotency 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 transaction application module initiates an application to the providing end transaction application module, the providing end transaction application module returns a generated transaction number to the calling end, and the calling end assembles a calling parameter 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 checks transaction information;
if the transaction occurs for the first time, the providing end transaction calling module 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 calling end transaction calling module;
if the transaction does not occur for the first time, the providing terminal transaction calling module acquires transaction information and judges whether the transaction is completed or not, if the transaction is completed in the last time, the transaction result is returned to the calling terminal through the calling terminal transaction calling module, if the transaction is not completed, the micro-service implementation class is called and the transaction result is stored, and the transaction result is returned to the calling terminal through the calling terminal transaction calling module.
2. The system for scheduling and supervising micropower services according to claim 1, wherein the scheduling and supervising system further comprises a transaction subsequent result access module for receiving a transaction subsequent result from the provider, the caller sending a request for scheduling the transaction subsequent result to the provider, the provider determining whether the subsequent result is set, and if the transaction is completed and the subsequent result is set, the transaction subsequent result access module returning the subsequent result to the caller, the caller processing the subsequent result; if the transaction is not completed or the subsequent result is not set, the calling terminal waits for the opportunity to initiate the subsequent result acquisition request again.
3. The idempotent guaranteed microservice call supervision system according to claim 1 further comprising a transaction management module to manage all microservice transactions, view the details of each transaction, and present a solution to the case of transaction anomalies.
4. The idempotent guaranteed microservice invocation supervisory system of claim 1, wherein the transaction number is used to mark one microservice transaction, and wherein multiple microservice invocations can occur for one microservice transaction, with the same transaction number for each invocation.
5. The idempotent guaranteed microservice invocation supervisory system of claim 1, wherein idempotent of microservice invocations is guaranteed by verification of transaction information within a providing-side transaction invocation module.
6. A guaranteed idempotent microservice calling method is characterized by comprising the following steps:
step 601: when a calling end initiates a calling application, firstly, a transaction application module of the calling end initiates an application to a transaction application module of a providing end, and the transaction application module of the providing end returns a generated transaction number;
step 602: the calling end assembles calling parameters according to the transaction number;
step 603: the calling end initiates micro-service calling;
step 604: the provider end is connected to the calling request, the provider end micro-service transaction calling module checks the transaction information, if the transaction is checked to occur for the first time, the 605 step is carried out for processing, if the transaction is not caused for the first time, the exception of the previous transaction calling is shown, and the 609 step is carried out for processing;
step 605: when the transaction occurs for the first time, the transaction information is stored and used for step 604 to judge whether the transaction occurs;
step 606: calling the micro-service implementation class to obtain a transaction result;
step 607: saving the transaction result;
step 608: returning a transaction result;
step 609: when the transaction does not occur for the first time, transaction information is obtained;
step 610: and judging whether the transaction is finished, wherein the step is performed when the call is not called for the first time, and is used for judging whether the transaction result is generated by the last call, if the transaction is finished by the last call, turning to the step 608, and if the transaction is not finished, turning to the step 606 to perform transaction processing again.
7. The idempotent guaranteed microservice calling method according to claim 6, characterized in that after the service processing is completed at the providing end, the providing end sets the subsequent result of the microservice transaction, and the acquisition of the subsequent result is initiated by the calling end, specifically:
step 701: the calling terminal initiates a request to obtain a subsequent result;
step 702: 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 step 703, if the transaction is not completed or the subsequent result is not set, the step is returned to step 701, and the calling end waits for the opportunity to initiate the subsequent result acquisition request again;
step 703: acquiring a subsequent result;
step 704: and the calling end processes according to the subsequent result.
8. The idempotent guaranteed microservice calling method of claim 6 wherein all microservice transactions are managed centrally and visually, the details of each transaction are reviewed in real time, and exception resolution is given for the case of transaction exceptions.
9. The method for invoking micro-services to ensure idempotency of claim 6, wherein a micro-service transaction may occur for multiple times, the transaction number for each invocation is the same, and the idempotency of micro-service invocation is ensured by checking the transaction information in the providing end transaction invocation module.
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 true CN111241112A (en) | 2020-06-05 |
| CN111241112B 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) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113744056A (en) * | 2021-09-07 | 2021-12-03 | 辽宁振兴银行股份有限公司 | Online transaction idempotent method and device |
| WO2022135158A1 (en) * | 2020-12-22 | 2022-06-30 | 网联清算有限公司 | Transaction request processing method and apparatus, and transaction transfer system |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070067266A1 (en) * | 2005-09-21 | 2007-03-22 | Microsoft Corporation | Generalized idempotent requests |
| US20130066948A1 (en) * | 2011-09-09 | 2013-03-14 | Oracle International Corporation | Idempotence for database transactions |
| CN106648936A (en) * | 2016-12-29 | 2017-05-10 | Tcl集团股份有限公司 | Cooperative processing method and system based on microservices and server |
| CN106921645A (en) * | 2016-06-28 | 2017-07-04 | 阿里巴巴集团控股有限公司 | Information issuing method, client and service end |
| CN107580032A (en) * | 2017-08-23 | 2018-01-12 | 阿里巴巴集团控股有限公司 | Data processing method, device and equipment |
| 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 |
| CN109376155A (en) * | 2018-11-06 | 2019-02-22 | 泰康保险集团股份有限公司 | ID generation method and device, storage medium and electronic equipment |
| CN109542639A (en) * | 2018-11-06 | 2019-03-29 | 用友网络科技股份有限公司 | A kind of processing method, processing unit for ensureing micro services and calling data consistency |
| CN109697113A (en) * | 2018-12-29 | 2019-04-30 | 广州华多网络科技有限公司 | Request method, apparatus, equipment and the readable storage medium storing program for executing retried |
| CN110266799A (en) * | 2019-06-21 | 2019-09-20 | 国网山西省电力公司忻州供电公司 | A method of the idempotence based on caching is realized |
-
2019
- 2019-12-27 CN CN201911380810.3A patent/CN111241112B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070067266A1 (en) * | 2005-09-21 | 2007-03-22 | Microsoft Corporation | Generalized idempotent requests |
| US20130066948A1 (en) * | 2011-09-09 | 2013-03-14 | Oracle International Corporation | Idempotence for database transactions |
| CN106921645A (en) * | 2016-06-28 | 2017-07-04 | 阿里巴巴集团控股有限公司 | Information issuing method, client and service end |
| CN106648936A (en) * | 2016-12-29 | 2017-05-10 | Tcl集团股份有限公司 | Cooperative processing method and system based on microservices and server |
| CN107580032A (en) * | 2017-08-23 | 2018-01-12 | 阿里巴巴集团控股有限公司 | Data processing method, device and equipment |
| 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 |
| CN109376155A (en) * | 2018-11-06 | 2019-02-22 | 泰康保险集团股份有限公司 | ID generation method and device, storage medium and electronic equipment |
| CN109542639A (en) * | 2018-11-06 | 2019-03-29 | 用友网络科技股份有限公司 | A kind of processing method, processing unit for ensureing micro services and calling data consistency |
| CN109697113A (en) * | 2018-12-29 | 2019-04-30 | 广州华多网络科技有限公司 | Request method, apparatus, equipment and the readable storage medium storing program for executing retried |
| CN110266799A (en) * | 2019-06-21 | 2019-09-20 | 国网山西省电力公司忻州供电公司 | A method of the idempotence based on caching is realized |
Non-Patent Citations (4)
| Title |
|---|
| BOYER, F., ETCHEVERS, X., DE PALMA, N., TAO, X.: "\" Architecture-Based Automated Updates of Distributed Microservices\"", 《INTERNATIONAL CONFERENCE ON SERVICE-ORIENTED COMPUTING》 * |
| OCTOBER: ""微服务的重试和幂等"", 《HTTPS://BLOG.CSDN.NET/WEIXIN_41715077/ARTICLE/DETAILS/83792542》 * |
| 张杰: ""采用消息队列实现数据一致性方法"" * |
| 曾泽堂: ""一种数据同步***的设计与实现"", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022135158A1 (en) * | 2020-12-22 | 2022-06-30 | 网联清算有限公司 | Transaction request processing method and apparatus, and transaction transfer system |
| CN113744056A (en) * | 2021-09-07 | 2021-12-03 | 辽宁振兴银行股份有限公司 | Online transaction idempotent method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111241112B (en) | 2023-05-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109634728B (en) | Job scheduling method and device, terminal equipment and readable storage medium | |
| WO2019006654A1 (en) | Financial self-service equipment maintenance dispatch generation method, hand-held terminal and electronic device | |
| CN106021093A (en) | Test case reuse method and system | |
| CN108804215B (en) | Task processing method and device and electronic equipment | |
| CN105677465B (en) | The data processing method and device of batch processing are run applied to bank | |
| CN110175165A (en) | Transaction account checking method, device, computer equipment and storage medium | |
| CN107682572B (en) | Customer incoming line distribution method, system, computer equipment and storage medium | |
| CN111241112A (en) | Micro-service call supervision system and method for guaranteeing idempotent | |
| CN110503408B (en) | Business process management system based on custom configuration | |
| CN111208992A (en) | System scheduling workflow generation method and system | |
| CN111787171A (en) | Automatic outbound method, device, electronic equipment and computer readable storage medium | |
| CN106487712B (en) | For accessing the method, apparatus and server of multiple external systems | |
| US11734057B2 (en) | Method and apparatus for processing a service of an abnormal server | |
| CN112463820A (en) | Data calling method and device | |
| CN115509714A (en) | Task processing method and device, electronic equipment and storage medium | |
| WO2019062087A1 (en) | Attendance check data testing method, terminal and device, and computer readable storage medium | |
| CN111679899B (en) | Task scheduling method, device, platform equipment and storage medium | |
| CN113556430A (en) | Outbound system and outbound method | |
| CN112308622A (en) | Data processing method and device for virtual object, storage medium and electronic equipment | |
| CN111324654A (en) | Interface calling method, system, computer device and computer readable storage medium | |
| CN114900531B (en) | Data synchronization method, device and system | |
| CN111125223B (en) | Database connection pool updating method and device | |
| CN116633783A (en) | Batch job processing method, device, equipment and storage medium | |
| CN101964922A (en) | Abnormal condition capturing method and device | |
| CN117973825A (en) | Multi-bank channel task flow differentiation processing method and device |
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 |