Microservice transaction submission method based on single database

Abstract

The invention discloses a micro-service transaction submitting method based on a single database. The method comprises the following steps that: an external api gateway downloads a plurality of micro-services layer by layer; and the sql gateway distributes a transaction sql cache space for the transaction id, and all sql requests received by the sql gateway are stored in the transaction sql cachespace. The external api gateway executes the request for the first time, and 1, the external api gateway calculates the sql submission number sent by the transaction id and stores the sql submission number in the request type cache space; 2, the external api gateway sends a request for opening a transaction id to the sql gateway, and the sql submission number is stored in a transaction sql cache space; and when the sql gateway receives the sql request or opens the transaction id request, the sql gateway judges whether the number of the received sql reaches the submitting number, and if so, thesql gateway uniformly submits the sql. And when the same request is executed again later, only the step 2 is executed. According to the method, the strong consistency of multiple micro-service transactions can be ensured, and excessive sacrifice is not needed in performance.

Description

technical field [0001] The invention belongs to the field of ensuring consistency of microservice transactions, and in particular relates to a method for submitting microservice transactions to the same database. Background technique [0002] With the rapid development of microservice technology, more and more microservice applications support a large number of businesses, some of which need to ensure strong consistency of transactions, such as the payment and points system of an e-commerce website, when users make payments After the operation, it is necessary to deduct the user's payment and modify the points at the same time. These two operations are inseparable. It is not allowed that one succeeds and the other fails, which constitutes a transaction. [0003] The invention relates to the problem of database merging transaction of two or more microservices with close connection and frequent requests. The general characteristics of these microservices are: [0004] 1. Mic...

AI Technical Summary

Problems solved by technology

[0004] 1. Microservices are closely connected and may even be deployed on the same server in proportion

[0005] 2. The database operations required by the same API for microservices are similar (for example, they both execute certain two SQLs, but the parameters are different)

[0007] 4. The microservice business cannot use the final consistency guarantee (see subsequent description)

[0024] Two-phase commit: The main problem with two-phase commit is that during the first distributed commit, the transaction initiator needs to wait for all sub-transaction providers to successfully submit "preprocessing" before sending a commit request to the database. A one-step synchronous submission work, resulting in a very large performance loss and affecting availability

[0025] Ensure final consistency: The problem with ensuring final consistency is that although final consistency can meet most business requirements, there are still a small number of requirements that must implement the acid feature, so ensuring final consistency cannot meet all business requirements

Images