Method and device and system for supporting ultimate consistency of micro-service architecture transaction

Abstract

The invention provides a method and a device and a system for supporting the ultimate consistency of a micro-service architecture transaction. The method for supporting the ultimate consistency of the micro-service architecture transaction used for a transmitting end comprises the steps that a service call is initiated, the logs are recorded, when the logs are written with actions, uninitiated service calls or logs with not returned results when the specified time is exceeded are checked regularly, and call requests are sent; the returned receipt information is received, the log records are queried, the call treatments are judged whether or not they have been completed according to the log status, if the calls are being treated, the returned results are called, and corresponding transaction interfaces are called according to the returned results, service calls are continually initiated, then through the method for supporting the ultimate consistency of the micro-service architecture transaction used for the message queueing services and the payments of a receiving end, asynchronous data calls for services are achieved through the logs and the message queueing, and the ultimate consistency of inter-service data is finally achieved.

Description

technical field [0001] The present invention relates to the field of microservices, in particular, to a method, device and system for supporting eventual consistency of microservice architecture transactions. Background technique [0002] At present, in the environment of Internet development, a unified large application system can no longer meet the growing demand for scalability. In order to improve the running speed of the system and support flexible dynamic expansion, the business system will generally be split into multiple microservices, that is, each service only provides relatively independent partial functions, and implements system functions by deploying new services. Expansion, and at the same time, when the pressure on the system is too high, it can more accurately expand the services that need to be added, and avoid other services from occupying unnecessary system resources. [0003] The invocation process of a business service may pass through multiple applica...

AI Technical Summary

Problems solved by technology

Specifically, in the way of service invocation, when a service request is initiated from application A, it may be necessary to call the services of multiple applications such as application B and application C. In order to ensure transaction consistency, if application C fails to be invoked, application B The data cannot be rolled back and an error occurs. At this time, the business logic of the application A can call the direction service of the application B here. However, it will bring two problems: on the one hand, the complexity of the business logic is high, and errors are prone to occur. ; On the other hand, if the A application, B application or C application is down, the data may not be rolled back, and ultimately the data consistency cannot be guaranteed

Images