Hotspot account transaction system and method

Abstract

The invention discloses a hotspot account transaction system and method. A transaction receiving module receives each account transaction request; a buffer scheduling module caches the account and theaccount balance in the borrowing database and the account and the account balance in the creditor database into a distributed memory; a transaction processing module processes each account transaction request, updates the account balance corresponding to the borrower and the account balance corresponding to the creditor in the distributed memory, and records each transaction detail of the borrower account and each transaction detail of the creditor account; a buffer processing module gathers each transaction detail of the borrower account and each transaction detail of the creditor account inbatches, gathers the transaction amount with the successful transaction state of the lender and the transaction amount with the failed transaction state of the lender, and updates the transaction amount with the successful transaction state into the lender account database; and summarizes the transaction amount of which the transaction state is successful and the transaction amount of which the transaction state is failed, and updates the transaction amount of which the transaction state is successful to the credit account database.

Description

Technical field [0001] The invention relates to the technical field of financial transaction systems, in particular to a hot account transaction system and method. Background technique [0002] In the existing accounting transaction system, the account balance update is a more prudent operation. In order to ensure that the balance update of each account is accurate, it is usually necessary to use a database lock to operate, and no matter which one is durable on the market The performance of a single data lock in a standardized database is not very high. Usually, both parties must participate in an account, so the logic of an account is to lock two accounts, calculate the balances of the two accounts, then update the balances of the two accounts, and finally release the lock. In the case of high concurrency, more When a thread competes for the same account for locks, there are bound to be many threads in the lock waiting state. When there are too many waiting threads, it will cau...

AI Technical Summary

Problems solved by technology

Usually a ledger must involve both parties, so the logic of a ledger is to lock two accounts, calculate the balance of the two accounts, then update the balance of the two accounts, and finally release the lock. When multiple threads compete for the lock on the same account, many threads are bound to be in the lock waiting state. When there are too many threads waiting, it will cause timeout, increase in failure rate, and congestion of the entire system and affect other normal records with low concurrency. account

Since the account balance is different from the transaction order, it can be realized by sub-database and sub-table. It is impossible to divide the balance of an account into multiple tables and multiple databases, otherwise the balance will be inaccurate or the business will not be satisfied.

Images