Parallel access method for same account in database

Abstract

The invention relates to a parallel access method for the same account in a database. The method comprises: receiving a plurality of access requests for the same account in the database; and distributing the plurality of access requests to a plurality of different sub-accounts of the account, wherein the plurality of access requests at least comprise a first sub-account and a second sub-account, the first sub-account is configured to generate an operation instruction for a database based on a plurality of access requests, and the database is configured to respond to the operation instruction to execute the following steps: newly setting or cancelling the sub-account, and / or changing the information of the sub-accounts. A large number of external access requests can be effectively dealt with, accumulation of the access requests is avoided, and the processing performance of a database and a transaction processing system is improved.

Description

Technical field [0001] The invention relates to the technical field of databases, and more specifically, to a method for parallel access to the same account in the database. Background technique [0002] In the prior art, the management of user accounts is usually performed through a database. That is, a single piece of account information is stored in the database. When the database receives a request to modify the account, it first locks the account record, then modifies it, and releases the lock after the modification is completed. However, if another access request for this account is received after the lock is locked, the new access request will be temporarily blocked until the previous modification operation is completed and the lock is released before the new access request can be processed. [0003] Although the performance of the database is improving day by day, according to the above solution, if the access to the same account continues to rise above a certain threshold...

AI Technical Summary

Problems solved by technology

However, if other access requests from this account are received after locking, the new access request will be temporarily blocked until the previous modification operation is completed and the lock is released before the new access request can continue to be processed

[0003] Although the performance of the database is improving day by day, according to the above solution, if the number of visits to the same account continues to rise above a certain threshold, the access requests for the hot account will accumulate, resulting in a significant delay in processing transactions by the application system Elevated, even affecting normal transaction processing involving other accounts

Images