Transaction processing method, device and system of distributed system, medium and equipment

Abstract

The invention relates to a transaction processing method, device and system of a distributed system, a medium and equipment, and the method comprises: intercepting a service call request initiated bya service caller application, wherein the service call request comprises a service requested to be called; if the preset consistency identifier exists in the service calling request, constructing an event object according to the method metadata of the service requested to be called, and storing the event object in a published event list, wherein the initial state of the event object is non-published; and selecting a target object from event objects which are not published in the published event list, and sending a request message corresponding to the target object to message middleware, the request message including method metadata of a target service corresponding to the target object, so that a service provider application providing the target service provides the target service based onthe request message. Therefore, the final consistency of transaction processing of the distributed system can be ensured.

Description

technical field [0001] The present disclosure relates to the field of computer technology, and in particular, to a transaction processing method, device, system, medium and equipment of a distributed system. Background technique [0002] With the popularity and popularization of distributed service architecture, multiple logical operations originally performed in a single application are now split into remote calls between multiple services, and the ensuing challenge is the issue of distributed transactions . Since each service uses its own database maintained separately, the operations on the data are not in the same transaction when remote calling different services. For example, when service A calls service B, service A executes successfully, but service B fails. Since the transaction of service A has been committed, it cannot be rolled back, which will lead to data inconsistency. [0003] In the prior art, when solving the data inconsistency problem of service calls, i...

AI Technical Summary

Problems solved by technology

Since each service uses its own database maintained separately, the operations on the data are not in the same transaction when remote calling different services. For example, when service A calls service B, service A executes successfully, but service B fails. Since the transaction of service A has been committed, it cannot be rolled back, which will lead to the problem of data inconsistency

[0003] In the prior art, when solving the data inconsistency problem of service calls, it is usually based on TCC (TCC service is composed of Try / Confirm / Cancel business), distributed transactions such as flexible transactions such as message eventual consistency transactions, wherein TCC It is implemented based on the compensation mechanism, and in the message eventual consistency transaction, when the transaction processing of the distributed system is performed, the service call request message of the service caller application may be sent repeatedly, so that the service provider application has the same message The risk of being consumed multiple times

Images