Hotspot account accounting method

Abstract

The invention discloses a hotspot account accounting method, which comprises the following steps: after receiving an accounting request, if an account is a hotspot account, judging the hotspot accounttype of the account; entering account keeping of a hotspot account entry account or account keeping of a hotspot account exit account according to the type of the hotspot account; and if the total balance in the hotspot account is insufficient, recharging each sub-account according to the balance of each sub-account of the hotspot account. The invention at least aims to effectively improve the concurrent processing capability of the hotspot account in the transaction system and ensure the real-time performance and accuracy of bookkeeping at the same time.

Description

technical field [0001] The present application relates to a method for detecting billing of a hotspot account. Background technique [0002] Usually, in the transaction system of a bank or a third-party payment institution, when a large-scale capital change occurs in a single account (such as a service fee account) at a certain moment, it is necessary to control the account to ensure the accuracy of the account balance change . Under normal circumstances, most of the accounting processing methods for such accounts (subsequently referred to as hot accounts) are controlled by pessimistic locks or optimistic locks of the database. However, due to the frequent addition and subtraction of the balance of the hotspot account, the database will perform frequent I / O operations, thereby reducing the I / O read and write speed of the database, which will eventually affect the slowdown of hotspot account bookkeeping, and even cause the entire transaction system link to be suspended. ser...

AI Technical Summary

Problems solved by technology

[0005] 2). Memory balance

[0009] 1). The performance limitation of a single machine (no matter how powerful the machine is, it has its performance bottleneck)

[0010] 2). Sudden downtime of the server, power outage, and sudden crash of the application (various unexpected events that cannot be resisted)

[0011] 3). Data delay caused by high concurrency (high concurrency can easily lead to resource exhaustion and slow system operation)

[0012] 4). The sub-account balance is exhausted, resulting in sufficient account balance, resulting in the failure of a large number of transactions in an instant, and how to allocate the balance when recharging hot accounts

[0013] 5). When the hot account becomes a non-hot account, the billing delay leads to a decrease in user satisfaction

[0014] Since the above-mentioned various problems exist in the process of hot account transactions, in the actual implementation process, when all the above factors must be considered together, the processing of hot accounts becomes extremely complicated

Images