Distributed transaction solution under micro-service architecture

Abstract

The invention provides a distributed transaction solution under a micro-service architecture. The method comprises the following steps: a user client initiates a registration request to a front-end web server, and the front-end web server sends the registration request of the user to a user micro-service server; the user micro-service server processes a registration transaction event of the user and sends the registration transaction event of the user to a message-oriented middleware, and the message-oriented middleware forwards the registration transaction event of the user to an account micro-service server; and the account micro-service server processes the registration transaction event of the user. According to the distributed transaction solution provided by the invention, the reliable transmission and final consistency of messages can be ensured through the own transaction message re-transmission mechanism and transaction re-processing mechanism of each micro-service so as to ensure that the implementation of the scheme does not depend on the reliable transmission mechanism of the third-party message-oriented middleware, and thus the coupling with a certain type of message-oriented middleware can be weakened; and the abnormal loss of the transaction message events can be timely found and the transaction message events can be timely self-healed through the global audit and self-healing mechanisms.

Description

technical field [0001] The invention relates to the technical field of wireless communication, in particular to a distributed transaction solution method under a microservice architecture. Background technique [0002] The traditional monolithic application is not enough to meet the business volume and data volume of modern Internet applications. At this time, the application and database need to be split, and an application needs to access two or more databases at the same time. At this time, we use distributed transactions to ensure consistency, which is what we often call 2PC (Two Phase Commitment Protocol, the abbreviation of Two Phase Commitment Protocol). However, traditional distributed transactions such as 2PC are not the best choice for consistency in microservice architecture: [0003] First of all, for the microservice architecture, not only the database is split, but also the application is split, and data access becomes more complicated. This is because the dat...

AI Technical Summary

Problems solved by technology

[0006] 1: The requirements for the message middleware itself are extremely high. All messages of the transaction are stored in the message middleware. Once the message middleware fails, it will not only affect the business, but may also cause unrecoverable data loss;

[0007] 2: The microservice system is highly dependent on the message middleware, resulting in strong coupling between the application system and the third-party middleware. Once a third-party middleware is selected, it is difficult to replace it. Three-party message middleware for complex system transformation;

[0008] 3: High-reliability message middleware is often a commercial software product, which increases the cost of system construction

Images