CN116644075A - Information processing method, information processing apparatus, electronic device, and medium - Google Patents
Information processing method, information processing apparatus, electronic device, and medium Download PDFInfo
- Publication number
- CN116644075A CN116644075A CN202310574258.1A CN202310574258A CN116644075A CN 116644075 A CN116644075 A CN 116644075A CN 202310574258 A CN202310574258 A CN 202310574258A CN 116644075 A CN116644075 A CN 116644075A
- Authority
- CN
- China
- Prior art keywords
- account
- transaction
- type database
- resource data
- data corresponding
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000010365 information processing Effects 0.000 title claims abstract description 44
- 238000003672 processing method Methods 0.000 title claims abstract description 31
- 238000003780 insertion Methods 0.000 claims abstract description 33
- 230000037431 insertion Effects 0.000 claims abstract description 33
- 238000000034 method Methods 0.000 claims abstract description 29
- 238000012795 verification Methods 0.000 claims description 37
- 238000012545 processing Methods 0.000 claims description 18
- 230000008569 process Effects 0.000 claims description 8
- 230000009467 reduction Effects 0.000 claims description 5
- 238000005516 engineering process Methods 0.000 abstract description 3
- 238000004364 calculation method Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 8
- 238000004590 computer program Methods 0.000 description 7
- 238000013523 data management Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 3
- 238000013500 data storage Methods 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 238000013524 data verification Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2379—Updates performed during online database operations; commit processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/466—Transaction processing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present disclosure relates to the field of computer technologies, and in particular, to an information processing method, an information processing apparatus, an electronic device, and a medium, where the method includes: receiving a transaction insertion request, and inserting a transaction in a first type database; updating data in the second type database according to the transaction when the transaction is successfully inserted in the first type database; when the data is successfully updated in the second type of database, the transaction is committed in the first type of database. By the technical scheme of the embodiment of the disclosure, the problem that errors or time delay occur when the resource data of the hot spot account are operated in the related technology can be solved.
Description
Technical Field
The present disclosure relates to the field of computer technology, and in particular, to an information processing method, an information processing apparatus, an electronic device, a computer-readable storage medium, and a computer program product.
Background
With the advent of the large data age, data storage has become important. A database is a repository that organizes, stores and manages data according to a data structure, and is a collection of large amounts of data stored in a computer for a long period of time, organized, sharable, and uniformly managed. Databases play an increasingly important role as an effective technique for data management.
In the prior art, the same database is adopted to realize data management, and in some scenes, the problems of data abnormality and the like can occur. For example, a hot spot account needs to be operated for a plurality of times in a short time for the resource data related to the account, so that the performance bottleneck of the system is easily achieved, and further the problems of operation failure or delay for the resource data related to the account, error of the resource data related to the account and the like are caused.
Disclosure of Invention
The disclosure provides an information processing method, an information processing device, an electronic apparatus, a computer readable storage medium and a computer program product, so as to at least solve the problem of error or delay in operating on resource data of a hot spot account in the related art. The technical scheme of the present disclosure is as follows:
according to a first aspect of an embodiment of the present disclosure, there is provided an information processing method including: receiving a transaction insertion request, and inserting a transaction in a first type database; wherein the first type database is used for maintaining transactions; updating data in the second type database according to the transaction when the transaction is successfully inserted in the first type database; the second type database is used for caching data corresponding to the transaction; when the data is successfully updated in the second type of database, the transaction is committed in the first type of database.
Optionally, the method further comprises: when the data fails to be updated in the second type database, rollback processing is carried out on the transaction; wherein the rollback process is to revert to a state prior to updating in the second type of database.
Optionally, the transaction is to reduce resource data corresponding to the account, the transaction has a reduced value, and the update of the data in the second type database fails, including: and when the resource data corresponding to the account is smaller than the reduction value, the data fails to be updated in the second type database.
Optionally, the method further comprises: searching resource data corresponding to the account in the second type database and transaction identification corresponding to the account; acquiring the transaction corresponding to the account from the first type database according to the transaction identifier corresponding to the account, and calculating verification resource data corresponding to the account according to the transaction corresponding to the account; comparing the resource data corresponding to the account with the verification resource data corresponding to the account; and when the resource data corresponding to the account is the same as the verification resource data corresponding to the account, updating the resource data table in the first type database by adopting the resource data corresponding to the account.
Optionally, the method further comprises: deleting the resource data corresponding to the account in the second type database when the resource data corresponding to the account is different from the verification resource data corresponding to the account; and loading the verification resource data corresponding to the account into a second type database.
Optionally, the method further comprises: receiving a resource query request, and querying resource data corresponding to the account in a second type database; and when the resource data corresponding to the account exists in the second type database, returning the resource data corresponding to the account.
Optionally, the method further comprises: when the resource data corresponding to the account does not exist in the second type database, acquiring a distributed lock for calculating the resource data corresponding to the account; when the distributed lock for calculating the resource data corresponding to the account is obtained, the transaction corresponding to the account is obtained in the first type database, the resource data corresponding to the account is calculated according to the transaction corresponding to the account, and the resource data corresponding to the account is returned.
According to a second aspect of the embodiments of the present disclosure, there is provided an information processing apparatus including: a transaction insertion unit configured to perform receiving a transaction insertion request, inserting a transaction in a first type database; wherein the first type database is used for maintaining transactions; a data updating unit configured to perform updating of data in the second type database according to the transaction when the insertion of the transaction in the first type database is successful; the second type database is used for caching data corresponding to the transaction; and a transaction commit unit configured to execute commit of the transaction in the first type database when the update of the data in the second type database is successful.
Optionally, the apparatus further comprises: a rollback processing unit configured to perform rollback processing on the transaction when the update of the data in the second type database fails; wherein the rollback process is to revert to a state prior to updating in the second type of database.
Optionally, the transaction is to reduce resource data corresponding to the account, the transaction has a reduced value, the data fails to be updated in the second type database, and the apparatus further includes: and the updating failure unit is configured to execute the failure of updating the data in the second type database when the resource data corresponding to the account is smaller than the reduction value.
Optionally, the apparatus further comprises: the transaction identifier acquisition unit is configured to perform searching of resource data corresponding to the account and transaction identifiers corresponding to the account in the second type database; the verification resource data calculation unit is configured to execute the transaction corresponding to the account in the first type database according to the transaction identifier corresponding to the account, and calculate the verification resource data corresponding to the account according to the transaction corresponding to the account; a resource data comparison unit configured to perform comparison of the resource data corresponding to the account with the verification resource data corresponding to the account; and the resource data table updating unit is configured to update the resource data table in the first type database by adopting the resource data corresponding to the account when the resource data corresponding to the account is the same as the verification resource data corresponding to the account.
Optionally, the apparatus further comprises: a resource data deleting unit configured to execute deleting the resource data corresponding to the account in the second type database when the resource data corresponding to the account is different from the check resource data corresponding to the account; and the resource data loading unit is configured to load the verification resource data corresponding to the account into the second type database.
Optionally, the apparatus further comprises: the resource data query unit is configured to execute the received resource query request and query the resource data corresponding to the account in the second type database; and the resource data returning unit is configured to return the resource data corresponding to the account when the resource data corresponding to the account exists in the second type database.
Optionally, the apparatus further comprises: the distributed lock acquisition unit is configured to acquire the distributed lock of the resource data corresponding to the computing account when the resource data corresponding to the account does not exist in the second type database; and the resource data calculation unit is configured to acquire the transaction corresponding to the account in the first type database when acquiring the distributed lock of the resource data corresponding to the calculation account, calculate the resource data corresponding to the account according to the transaction corresponding to the account, and return the resource data corresponding to the account.
According to a third aspect of embodiments of the present disclosure, there is provided an electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to execute executable instructions to implement an information processing method as described above.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium, which when executed by a processor of an electronic device, enables the electronic device to perform the above-described information processing method.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product, a computer program/instruction, characterized in that the computer program/instruction implements the above-mentioned information processing method when being executed by a processor.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
in the information processing method provided by the embodiment of the disclosure, a transaction insertion request can be received, a transaction is inserted into a first type database, when the transaction is successfully inserted into the first type database, data is updated in a second type database according to the transaction, and when the data is successfully updated in the second type database, the transaction is submitted in the first type database. According to the embodiment of the disclosure, the two databases can be combined to process the transaction, the transaction is maintained in one database, the data corresponding to the transaction is cached in the other database, the transaction and the data corresponding to the transaction are separated, the stability of data management is improved, high concurrency operation can be supported, operation failure or delay aiming at a hot spot account is avoided, and the accuracy of data related to the account is further ensured.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
FIG. 1 schematically illustrates a schematic diagram of an exemplary system architecture for implementing an information processing method in an exemplary embodiment of the present disclosure;
FIG. 2 is a flowchart illustrating a method of information processing according to an exemplary embodiment;
FIG. 3 is a flowchart illustrating another information processing method according to an exemplary embodiment;
FIG. 4 is a flowchart illustrating updating a resource data table in a first type database with account-corresponding resource data when the account-corresponding resource data is the same as the account-corresponding check resource data, according to an example embodiment;
FIG. 5 is a flowchart illustrating the deletion of account-corresponding resource data in a second type of database and the loading of account-corresponding check resource data into the second type of database, according to an exemplary embodiment;
FIG. 6 is a diagram illustrating whether one corresponding resource data is the same as the corresponding check resource data of the account, according to an example embodiment;
FIG. 7 is a flowchart illustrating returning resource data corresponding to an account when the resource data corresponding to the account exists in a second type database, according to an exemplary embodiment;
FIG. 8 is a flowchart illustrating the calculation of account-corresponding resource data based on account-corresponding transactions and the return of account-corresponding resource data in accordance with an exemplary embodiment;
FIG. 9 is a diagram illustrating a query of a second type of database for resource data corresponding to an account, according to an example embodiment;
fig. 10 is a schematic diagram showing the composition of an information processing apparatus according to an exemplary embodiment;
fig. 11 is a schematic diagram illustrating a structure of an electronic device suitable for use in implementing an exemplary embodiment of the present disclosure, according to an exemplary embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, or in one or more software-hardened modules, or in different networks and/or processor devices and/or microcontroller devices.
Fig. 1 shows a schematic diagram of an exemplary system architecture to which the information processing method of the embodiments of the present disclosure may be applied.
As shown in fig. 1, system architecture 1000 may include one or more of terminal devices 1001, 1002, 1003, a network 1004, and a server 1005. The network 1004 serves as a medium for providing a communication link between the terminal apparatuses 1001, 1002, 1003 and the server 1005. The network 1004 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. For example, the server 1005 may be a server cluster formed by a plurality of servers.
A user can interact with a server 1005 via a network 1004 using terminal apparatuses 1001, 1002, 1003 to receive or transmit messages or the like. The terminal devices 1001, 1002, 1003 may be various electronic devices having a display screen including, but not limited to, smartphones, tablet computers, portable computers, desktop computers, and the like. In addition, the server 1005 may be a server providing various services.
In one embodiment, the execution subject of the information processing method of the present disclosure may be a server 1005, and the server 1005 may acquire a transaction insertion request transmitted by the terminal device 1001, 1002, 1003 and insert a transaction in the first type database, update data in the second type database according to the transaction when the transaction is successfully inserted in the first type database, and commit the transaction in the first type database when the data is successfully updated in the second type database.
In addition, the information processing method of the present disclosure may also be performed by the terminal device 1001, 1002, 1003, etc. to implement receiving a transaction insertion request, inserting a transaction in a first type database, updating data in a second type database according to the transaction when the transaction is successfully inserted in the first type database, and submitting the transaction in the first type database when the data is successfully updated in the second type database.
Further, the implementation procedure of the information processing method of the present disclosure may also be implemented by the terminal apparatuses 1001, 1002, 1003 and the server 1005 in common. For example, the terminal device 1001, 1002, 1003 may receive a transaction insertion request, insert a transaction in a first type database, update data in a second type database according to the transaction when the transaction is successfully inserted in the first type database, and commit the transaction in the first type database when the data is successfully updated in the second type database. And returns the processing result to the server 1005.
With the advent of the large data age, data storage has become important. A database is a repository that organizes, stores and manages data according to a data structure, and is a collection of large amounts of data stored in a computer for a long period of time, organized, sharable, and uniformly managed. Databases play an increasingly important role as an effective technique for data management.
In the prior art, the same database is adopted to realize data management, and in some scenes, the problems of data abnormality and the like can occur. For example, a hot spot account needs to be operated for a plurality of times in a short time for the resource data related to the account, so that the performance bottleneck of the system is easily achieved, and further the problems of operation failure or delay for the resource data related to the account, error of the resource data related to the account and the like are caused.
Fig. 2 is a flowchart of an information processing method according to an exemplary embodiment, and as shown in fig. 2, the information processing method may include the following steps.
In step S210, a transaction insertion request is received, and a transaction is inserted in a first type database; wherein the first type database is used for maintaining transactions;
in step S220, when the transaction is successfully inserted in the first type database, updating data in the second type database according to the transaction; the second type database is used for caching data corresponding to the transaction;
in step S230, when the data is updated successfully in the second type database, the transaction is committed in the first type database.
In the information processing method provided by the embodiment of the disclosure, a transaction insertion request can be received, a transaction is inserted into a first type database, when the transaction is successfully inserted into the first type database, data is updated in a second type database according to the transaction, and when the data is successfully updated in the second type database, the transaction is submitted in the first type database. According to the embodiment of the disclosure, the two databases can be combined to process the transaction, the transaction is maintained in one database, the data corresponding to the transaction is cached in the other database, the transaction and the data corresponding to the transaction are separated, the stability of data management is improved, high concurrency operation can be supported, operation failure or delay aiming at a hot spot account is avoided, and the accuracy of data related to the account is further ensured.
Next, steps S210 to S240 of the information processing method in the present exemplary embodiment will be described in more detail with reference to fig. 2 and the embodiment.
Step S210, receiving a transaction insertion request, and inserting a transaction in a first type database;
in one example embodiment of the present disclosure, a transaction insertion request may be received, inserting a transaction in a first type database. Wherein the first type of database is used to maintain transactions. In particular, a transaction insertion request may be used to insert a transaction in a first type of database. For example, the transaction insertion request may be an insert operation (insert operation) in a first type of database.
The present disclosure is not limited to a specific form of the transaction insertion request.
In one example embodiment of the present disclosure, a transaction may be inserted in a first type database after a transaction insertion request is received. Specifically, the transaction may include adding data corresponding to the transaction, deleting data corresponding to the transaction, modifying data corresponding to the transaction, and so on.
For example, a transaction may be deleting a portion of the resource data of an account.
It should be noted that, the present disclosure is not limited in particular to a specific manner of inserting a transaction in the first type database.
In one example embodiment of the present disclosure, the first type of database may be a database that employs a relational model to organize data, such as a relational database that stores data in rows and columns, the series of rows and columns being referred to as tables, a group of tables making up the database. The user retrieves the data in the database by querying, which is an executable code that defines certain areas in the database. A relational model can be understood simply as a two-dimensional tabular model, and a first type of database is a data organization consisting of two-dimensional tables and relationships between them. For example, an account list may be maintained in a first type database.
In one example embodiment of the present disclosure, the first type database may employ an OceanBase database (distributed first type database).
It should be noted that the present disclosure is not limited to the specific type of the first type database.
In an example embodiment of the present disclosure, the second type database refers to a database storing data in the form of key values, so as to implement caching of the data, improve the response speed of the application, and greatly relieve the pressure of the back-end database. The data can be stored in a temporary way, a permanent way and a two-way.
In one example embodiment of the present disclosure, the second type database may employ a Redis (Remote Dictionary Server, remote dictionary service) database.
It should be noted that the present disclosure is not limited to the specific type of the second type database.
Step S220, when the transaction is successfully inserted into the first type database, updating data in the second type database according to the transaction;
in one example embodiment of the present disclosure, after inserting a transaction in a first type database through the above steps, it may be determined whether the transaction was inserted successfully, and when the transaction was inserted successfully in the first type database, data is updated in a second type database according to the transaction. The second type database is used for caching data corresponding to the transaction. Specifically, the transaction is successfully inserted into the first type database, which means that the data corresponding to the transaction needs to be updated in the second type database.
For example, a transaction is to delete part of the resource data of an account, and when the transaction is inserted into the first type database and succeeds, the account may be searched in the second type database, and the part of the resource data of the account may be deleted.
It should be noted that the present disclosure is not limited in particular to a specific manner of updating data in the second type database according to the transaction.
In one example embodiment of the present disclosure, a transaction may return an operation failure message when it fails to insert in the first type of database. Specifically, failure of the transaction to insert in the first type of database may indicate that the transaction was not successfully inserted in the first type of database, at which point an operation failure message may be returned.
For example, when a transaction is inserted into the first type database, if the response time is greater than the preset time, it may indicate that the transaction fails to be inserted into the first type database, and at this time, an operation failure message may be returned.
In one example embodiment of the present disclosure, the second database may be a cached database.
It should be noted that the present disclosure is not limited in particular to the specific type of insertion failure of a transaction in the first type database.
In one example embodiment of the present disclosure, an operation failure message may be returned to the upstream account.
In step S230, when the data is successfully updated in the second type database, the transaction is committed in the first type database.
In one example embodiment of the present disclosure, after updating data in the second type database according to the transaction through the above steps, it may be determined whether the update is successful, and when the update of data in the second type database is successful, the transaction is committed in the first type database. Specifically, when the data is updated successfully in the second type database, it indicates that the data has been updated in the second type database for the transaction, at this time, the transaction may be submitted in the first type database, which indicates that the transaction has been processed. Specifically, commit refers to all operations that commit the transaction, i.e., all updates to the database in the transaction are written to disk, and the transaction ends normally.
It should be noted that the present disclosure is not limited in particular to the specific manner in which the transaction is committed in the first type database.
In one example embodiment of the present disclosure, a rollback process is performed on a transaction when data fails to update in a second type of database. Wherein the rollback process is to revert to a state prior to updating in the second type of database. Specifically, failure to update the data in the second type database may indicate that the data fails to be successfully updated in the second type database, i.e., the transaction is not executed in the second type database, and at this time, rollback processing may be performed on the transaction. Specifically, rollback refers to the act of a program or data processing error, restoring the program or data to the last correct state. Rollback includes program rollback and data rollback types.
In one example embodiment of the present disclosure, updating the data in the second type database fails when the account corresponds to less than the reduced value. Specifically, the transaction is to reduce the resource data corresponding to the account, the transaction has a reduced value, and the reduction operation can be performed only when the resource data corresponding to the account is smaller than the reduced value.
For example, when the transaction is to reduce the resource data corresponding to the account, and the resource data in the account is smaller than the reduced value corresponding to the transaction, the transaction cannot be executed, and the update of the data in the second type database fails, and at this time, the rollback processing needs to be performed on the transaction.
It should be noted that, the present disclosure is not limited in particular to the specific type of data update failure in the second type database.
In an example embodiment of the present disclosure, as shown in fig. 3, a transaction may be performed in multiple lines (thread 1, thread 2, thread 3), a transaction insertion request may be received, a transaction is inserted in a first type database, and whether the insertion is successful (whether the insertion of the transaction is successful in the first type database) is determined, if the insertion is successful, data is updated in a second type database according to the transaction, and if the insertion is failed, an operation failure message is returned; and judging whether the updating is successful (whether the updating of the data in the second type database is successful), if the updating is successful, submitting the transaction in the first type database, and if the updating is failed, carrying out rollback processing on the transaction.
In one example embodiment of the present disclosure, lua script (scripting language) updates may be employed to ensure atomicity of transactions.
In an example embodiment of the present disclosure, resource data corresponding to an account and a transaction identifier corresponding to the account may be searched in a second type database, a transaction corresponding to the account is obtained in a first type database according to the transaction identifier corresponding to the account, check resource data corresponding to the account is calculated according to the transaction corresponding to the account, the resource data corresponding to the account is compared with the check resource data corresponding to the account, and when the resource data corresponding to the account is the same as the check resource data corresponding to the account, the resource data corresponding to the account is used to update a resource data table in the first type database. Referring to fig. 4, when the resource data corresponding to the account is the same as the check resource data corresponding to the account, updating the resource data table in the first type database by using the resource data corresponding to the account may include the following steps S410 to S440:
step S410, searching resource data corresponding to the account and transaction identification corresponding to the account in a second type database;
in one example embodiment of the present disclosure, resource data corresponding to an account and a transaction identifier corresponding to the account may be looked up in a second type database. Specifically, the second type database may store resource data corresponding to the account and a transaction identifier corresponding to the account. Specifically, the transaction identifier corresponding to the account may be used to search the first type database for a transaction related to the transaction identifier corresponding to the account.
For example, the transaction identification corresponding to the account may be a primary key ID of a list maintained in the first type database.
It should be noted that, the specific form of the transaction identifier corresponding to the account is not particularly limited in this disclosure.
Further, resource data corresponding to the account and transaction identification corresponding to the account can be searched in the second type database according to the identification corresponding to the account.
For example, the identification corresponding to the account may be an account ID.
It should be noted that the specific form of the identification of the account is not particularly limited in this disclosure.
Step S420, acquiring the transaction corresponding to the account from the first type database according to the transaction identifier corresponding to the account, and calculating verification resource data corresponding to the account according to the transaction corresponding to the account;
in an example embodiment of the present disclosure, after obtaining the resource data corresponding to the account and the transaction identifier corresponding to the account through the above steps, the transaction corresponding to the account may be obtained in the first type database according to the transaction identifier corresponding to the account. Specifically, the transaction identifier corresponding to the account may be used to search the transaction related to the transaction identifier corresponding to the account in the first type database, so that the transaction corresponding to the account may be searched in the first type database through the transaction identifier corresponding to the account, and the transaction corresponding to the account may be used to indicate all operations performed by the account.
It should be noted that, the specific manner of acquiring the transaction corresponding to the account in the first type database according to the transaction identifier corresponding to the account is not particularly limited in this disclosure.
In an example embodiment of the present disclosure, after the transaction corresponding to the account is obtained through the above steps, the verification resource data corresponding to the account may be calculated according to the transaction corresponding to the account. Specifically, the transaction corresponding to the account can be summarized, and the verification resource data corresponding to the account is obtained.
It should be noted that, the specific manner of calculating the verification resource data corresponding to the account according to the transaction corresponding to the account is not particularly limited in this disclosure.
Step S430, comparing the resource data corresponding to the account with the verification resource data corresponding to the account;
step S440, when the resource data corresponding to the account is the same as the verification resource data corresponding to the account, the resource data corresponding to the account is adopted to update the resource data table in the first type database.
In an example embodiment of the present disclosure, after the resource data corresponding to the account and the check resource data corresponding to the account are obtained through the above steps, whether the resource data corresponding to the account is identical to the check resource data corresponding to the account may be compared, and if the resource data corresponding to the account is identical to the check resource data corresponding to the account, it indicates that the check resource data corresponding to the account stored in the second type database is correct, and at this time, the resource data corresponding to the account may be used to update the resource data table in the first type database.
It should be noted that, the specific manner of updating the resource data table in the first type database by using the resource data corresponding to the account is not particularly limited in the present disclosure.
Specifically, the resource data table in the first type database is a table maintained by the first type database, and the resource data table may be used to record resource data of a plurality of accounts.
It should be noted that, the present disclosure is not limited to a specific form of the resource data table in the first type database.
According to the scheme disclosed by the invention, consistency verification can be performed on the first type of database and the second type of database.
Further, the scheme of the present embodiment may be executed every preset time period. For example, the scheme of the present embodiment is executed every 5 minutes.
Through the steps S410 to S440, the resource data corresponding to the account and the transaction identifier corresponding to the account may be searched in the second type database, the transaction corresponding to the account may be obtained in the first type database according to the transaction identifier corresponding to the account, the check resource data corresponding to the account may be calculated according to the transaction corresponding to the account, the resource data corresponding to the account may be compared with the check resource data corresponding to the account, and when the resource data corresponding to the account is the same as the check resource data corresponding to the account, the resource data corresponding to the account may be used to update the resource data table in the first type database. By the embodiment of the invention, the data in the second type database and the first type database can be verified, and the accuracy of the system in a high concurrency scene is ensured.
In an example embodiment of the present disclosure, when the resource data corresponding to the account is different from the check resource data corresponding to the account, deleting the resource data corresponding to the account in the second type database, and loading the check resource data corresponding to the account into the second type database. Referring to fig. 5, deleting the resource data corresponding to the account in the second type database, and loading the verification resource data corresponding to the account into the second type database may include the following steps S510 to S520:
step S510, deleting the resource data corresponding to the account in the second type database when the resource data corresponding to the account is different from the verification resource data corresponding to the account;
in an example embodiment of the present disclosure, after determining whether the resource data corresponding to the account is the same as the check resource data corresponding to the account through the above steps, if the resource data corresponding to the account is different from the check resource data corresponding to the account, it indicates that the resource data corresponding to the account stored in the second type database is wrong, that is, dirty data exists in the second type database, and at this time, the resource data corresponding to the account may be deleted in the second type database.
Step S520, loading the verification resource data corresponding to the account into a second type database.
In an example embodiment of the present disclosure, after deleting the resource data corresponding to the account in the second type database through the above steps, the verification resource data corresponding to the account may be loaded to the second type database. Specifically, after deleting the resource data corresponding to the account in the second type database, the verification resource data corresponding to the account obtained through the calculation in the above steps may be stored as the resource data corresponding to the account, for example, in the second type database.
It should be noted that, the specific manner of loading the verification resource data corresponding to the account into the second type database is not particularly limited in this disclosure.
In an example embodiment of the present disclosure, as shown in fig. 6, a verification task may be executed at regular time, after a preset time is reached, a data verification task is started to be executed, resource data corresponding to an account and a transaction identifier corresponding to the account are searched in a second type database, a transaction corresponding to the account is obtained in a first type database according to the transaction identifier corresponding to the account, verification resource data corresponding to the account is calculated according to the transaction corresponding to the account, the resource data corresponding to the account is compared with the verification resource data corresponding to the account, whether the resource data corresponding to the account is identical to the verification resource data corresponding to the account is determined, if so, the resource data corresponding to the account is updated by adopting the resource data corresponding to the account, and if not, the resource data corresponding to the account is deleted in the second type database.
Through the steps S510 to S520, when the resource data corresponding to the account is different from the check resource data corresponding to the account, deleting the resource data corresponding to the account from the second type database, and loading the check resource data corresponding to the account to the second type database. By the embodiment of the disclosure, the data in the second type database and the first type database can be verified, the problem of inconsistent data caused by factors such as hardware or network when the system operates is corrected, and the accuracy of the system in a high concurrency scene is ensured.
In an example embodiment of the present disclosure, a resource query request may be received, resource data corresponding to an account may be queried in a second type database, and when resource data corresponding to an account exists in the second type database, resource data corresponding to an account may be returned. Referring to fig. 7, when resource data corresponding to an account exists in the second type database, returning the resource data corresponding to the account may include the following steps S710 to S720:
step S710, receiving a resource query request, and querying resource data corresponding to the account in a second type database;
step S720, when the resource data corresponding to the account exists in the second type database, returning the resource data corresponding to the account.
In one example embodiment of the present disclosure, a resource query request may be received, and resource data corresponding to an account may be queried in a second type of database. Specifically, the resource query request may be used to query the second type database for resource data corresponding to an account, and if the second type database has resource data corresponding to an account, the resource data corresponding to the account may be directly returned. Specifically, the resource query request includes an identifier corresponding to the account, and resource data corresponding to the account can be queried in the second type database through the identifier corresponding to the account.
It should be noted that, the specific manner of querying the resource data corresponding to the account in the second type database is not particularly limited in this disclosure.
Through the steps S710 to S720, a resource query request may be received, the resource data corresponding to the account may be queried in the second type database, and when the resource data corresponding to the account exists in the second type database, the resource data corresponding to the account may be returned.
In an example embodiment of the present disclosure, when there is no resource data corresponding to an account in the second type database, a distributed lock for calculating the resource data corresponding to the account is obtained, and when the distributed lock for calculating the resource data corresponding to the account is obtained, a transaction corresponding to the account is obtained in the first type database, the resource data corresponding to the account is calculated according to the transaction corresponding to the account, and the resource data corresponding to the account is returned. Referring to fig. 8, calculating the resource data corresponding to the account according to the transaction corresponding to the account, and returning the resource data corresponding to the account may include the following steps S810 to S820:
Step S810, when the resource data corresponding to the account does not exist in the second type database, acquiring a distributed lock for calculating the resource data corresponding to the account;
in an example embodiment of the present disclosure, after the resource data corresponding to the account is queried in the second type database through the above steps, if the resource data corresponding to the account does not exist in the second type database, the resource data corresponding to the account needs to be calculated according to the first type database, and at this time, a distributed lock for calculating the resource data corresponding to the account may be acquired first. Specifically, the distributed lock refers to a lock in a distributed system, and the problem of controlling access of shared resources in the distributed system can be solved through the distributed lock. In particular, a distributed lock has the following characteristics: in the distributed system environment, one method can only be executed by one thread of one machine at the same time, the high-availability acquisition lock and release lock are realized, the high-performance acquisition lock and release lock have the reentrant characteristic and the lock failure mechanism, namely automatic unlocking is realized, deadlock is prevented, and the non-blocking lock characteristic is realized, namely the acquisition lock failure is returned directly after the acquisition lock is not acquired.
It should be noted that the present disclosure is not limited to a specific implementation of the distributed lock.
Step S820, when obtaining the distributed lock of the resource data corresponding to the calculation account, obtaining the transaction corresponding to the account in the first type database, calculating the resource data corresponding to the account according to the transaction corresponding to the account, and returning the resource data corresponding to the account;
in an example embodiment of the present disclosure, when the distributed lock for calculating the resource data corresponding to the account is obtained through the above steps, a transaction corresponding to the account may be obtained in the first type database, the resource data corresponding to the account is calculated according to the transaction corresponding to the account, and the resource data corresponding to the account is returned. Specifically, the transaction identifier corresponding to the account can be searched in the second type database, the transaction corresponding to the account is obtained in the first type database according to the transaction identifier corresponding to the account, then the resource data corresponding to the account is calculated according to the transaction corresponding to the account, and finally the resource data corresponding to the account obtained through calculation is returned.
It should be noted that, the specific manner of calculating the resource data corresponding to the account according to the transaction corresponding to the account is not particularly limited in this disclosure.
Further, when the distributed lock of the resource data corresponding to the computing account is not obtained through the above steps, it may indicate that other threads currently have already obtained the resource data corresponding to the computing account according to the transaction corresponding to the account, and at this time, the thread may end, that is, the task of calculating the resource data corresponding to the account may end.
In an example embodiment of the present disclosure, as shown in fig. 9, a resource query request may be received, resource data corresponding to an account may be queried in a second type database, whether the resource data corresponding to the account exists in the second type database is determined, if yes, the resource data corresponding to the account is returned, if no, a distributed lock of the resource data corresponding to the computing account is obtained, when no distributed lock of the resource data corresponding to the computing account is obtained, the thread is ended, when the distributed lock of the resource data corresponding to the computing account is obtained, resource data corresponding to the account may be calculated according to transactions corresponding to the account, a resource data table in the first type database is updated according to the resource data corresponding to the account, and resource data corresponding to the account is updated in the second type database.
Through the steps S810 to S820, when the resource data corresponding to the account does not exist in the second type database, the distributed lock of the resource data corresponding to the computing account is obtained, and when the distributed lock of the resource data corresponding to the computing account is obtained, the transaction corresponding to the account is obtained in the first type database, the resource data corresponding to the account is computed according to the transaction corresponding to the account, and the resource data corresponding to the account is returned. By means of the scheme, when resource data query is conducted, data access can be controlled by adopting the distributed lock, and the problem of data error caused by accessing the resource data in a high concurrency scene is avoided.
In the information processing method provided by an embodiment of the present disclosure, a transaction insertion request may be received, a transaction is inserted into a first type database, when the transaction is successfully inserted into the first type database, data is updated in a second type database according to the transaction, and when the data is successfully updated in the second type database, the transaction is submitted in the first type database. According to the embodiment of the disclosure, the transaction is processed through the first type database and the second type database, so that high concurrency operation can be supported, operation failure or delay aiming at a hot spot account is avoided, and accuracy of data related to the account is further ensured.
Fig. 10 is a block diagram of an information processing apparatus according to an exemplary embodiment. Referring to fig. 10, the information processing apparatus 1000 includes a transaction insertion unit 1010, a data update unit 1020, and a transaction commit unit 1030.
Wherein the transaction insertion unit is configured to perform receiving a transaction insertion request and insert a transaction in the first type database; wherein the first type database is used for maintaining transactions; a data updating unit configured to perform updating of data in the second type database according to the transaction when the insertion of the transaction in the first type database is successful; the second type database is used for caching data corresponding to the transaction; and a transaction commit unit configured to execute commit of the transaction in the first type database when the update of the data in the second type database is successful.
Optionally, the apparatus further comprises: a rollback processing unit configured to perform rollback processing on the transaction when the update of the data in the second type database fails; wherein the rollback process is to revert to a state prior to updating in the second type of database.
Optionally, the transaction is to reduce resource data corresponding to the account, the transaction has a reduced value, the data fails to be updated in the second type database, and the apparatus further includes: and the updating failure unit is configured to execute the failure of updating the data in the second type database when the resource data corresponding to the account is smaller than the reduction value.
Optionally, the apparatus further comprises: the transaction identifier acquisition unit is configured to perform searching of resource data corresponding to the account and transaction identifiers corresponding to the account in the second type database; the verification resource data calculation unit is configured to execute the transaction corresponding to the account in the first type database according to the transaction identifier corresponding to the account, and calculate the verification resource data corresponding to the account according to the transaction corresponding to the account; a resource data comparison unit configured to perform comparison of the resource data corresponding to the account with the verification resource data corresponding to the account; and the resource data table updating unit is configured to update the resource data table in the first type database by adopting the resource data corresponding to the account when the resource data corresponding to the account is the same as the verification resource data corresponding to the account.
Optionally, the apparatus further comprises: a resource data deleting unit configured to execute deleting the resource data corresponding to the account in the second type database when the resource data corresponding to the account is different from the check resource data corresponding to the account; and the resource data loading unit is configured to load the verification resource data corresponding to the account into the second type database.
Optionally, the apparatus further comprises: the resource data query unit is configured to execute the received resource query request and query the resource data corresponding to the account in the second type database; and the resource data returning unit is configured to return the resource data corresponding to the account when the resource data corresponding to the account exists in the second type database.
Optionally, the apparatus further comprises: the distributed lock acquisition unit is configured to acquire the distributed lock of the resource data corresponding to the computing account when the resource data corresponding to the account does not exist in the second type database; and the resource data calculation unit is configured to acquire the transaction corresponding to the account in the first type database when acquiring the distributed lock of the resource data corresponding to the calculation account, calculate the resource data corresponding to the account according to the transaction corresponding to the account, and return the resource data corresponding to the account.
An information processing apparatus provided by an embodiment of the present disclosure may receive a transaction insertion request, insert a transaction in a first type database, update data in a second type database according to the transaction when the transaction is successfully inserted in the first type database, and commit the transaction in the first type database when the data is successfully updated in the second type database. According to the embodiment of the disclosure, the transaction is processed through the first type database and the second type database, so that high concurrency operation can be supported, operation failure or delay aiming at a hot spot account is avoided, and accuracy of data related to the account is further ensured.
With respect to the information processing apparatus in the above-described embodiments, the specific manner in which the respective modules perform operations has been described in detail in the embodiments concerning the method, and will not be described in detail here.
An electronic device 1100 according to such an embodiment of the present disclosure is described below with reference to fig. 11. The electronic device 1100 shown in fig. 11 is merely an example and should not be construed as limiting the functionality and scope of use of the disclosed embodiments.
As shown in fig. 11, the electronic device 1100 is embodied in the form of a general purpose computing device. Components of electronic device 1100 may include, but are not limited to: the at least one processing unit 1110, the at least one memory unit 1120, a bus 1130 connecting the different system components (including the memory unit 1120 and the processing unit 1110), and a display unit 1140.
Wherein the storage unit stores program code that is executable by the processing unit 1110 such that the processing unit 1110 performs steps according to various exemplary embodiments of the present disclosure described in the above-described "exemplary methods" section of the present specification. For example, the processing unit 1110 may perform step S210 as shown in fig. 2, receive a transaction insertion request, insert a transaction in a first type database; wherein the first type database is used for maintaining transactions; step S220, when the transaction is successfully inserted into the first type database, updating data in the second type database according to the transaction; the second type database is used for caching data corresponding to the transaction; in step S230, when the data is successfully updated in the second type database, the transaction is committed in the first type database.
The storage unit 1120 may include a readable medium in the form of a volatile storage unit, such as a Random Access Memory (RAM) 1121 and/or a cache memory 1122, and may further include a Read Only Memory (ROM) 1123.
Storage unit 1120 may also include a program/utility 1124 having a set (at least one) of program modules 1125, such program modules 1125 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
The bus 1130 may be a local bus representing one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a bus using any of a variety of bus architectures.
The electronic device 1100 may also communicate with one or more external devices 1170 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 1100, and/or any device (e.g., router, modem, etc.) that enables the electronic device 1100 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 1150. Also, electronic device 1100 can communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 1160. As shown, network adapter 1160 communicates with other modules of electronic device 1100 via bus 1130. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 1100, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.
In an exemplary embodiment, a computer readable storage medium is also provided, e.g., a memory, comprising instructions executable by a processor of an apparatus to perform the above method. Alternatively, the computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
In an exemplary embodiment, a computer program product is also provided, comprising a computer program/instruction which, when executed by a processor, implements the information processing method in the above-described embodiment.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. An information processing method, characterized by comprising:
receiving a transaction insertion request, and inserting a transaction in a first type database; wherein the first type database is used to maintain the transaction;
updating data in a second type database according to the transaction when the transaction is successfully inserted in the first type database; the second type database is used for caching data corresponding to the transaction;
And submitting the transaction in the first type database when the data is successfully updated in the second type database.
2. The information processing method according to claim 1, characterized in that the method further comprises:
when the data fails to be updated in the second type database, rollback processing is carried out on the transaction; wherein the rollback process is to revert to a state prior to updating in the second type database.
3. The information processing method according to claim 2, wherein the transaction is to reduce resource data corresponding to an account, the transaction corresponds to a reduced value, and the data fails to update in the second type database, comprising:
and when the resource data corresponding to the account is smaller than the reduction value, the data fails to be updated in the second type database.
4. The information processing method according to claim 1, characterized in that the method further comprises:
searching resource data corresponding to an account and a transaction identifier corresponding to the account in the second type database;
acquiring the transaction corresponding to the account from the first type database according to the transaction identifier corresponding to the account, and calculating the verification resource data corresponding to the account according to the transaction corresponding to the account;
Comparing the resource data corresponding to the account with the verification resource data corresponding to the account;
and when the resource data corresponding to the account is the same as the verification resource data corresponding to the account, updating a resource data table in the first type database by adopting the resource data corresponding to the account.
5. The information processing method according to claim 4, characterized in that the method further comprises:
deleting the resource data corresponding to the account in the second type database when the resource data corresponding to the account is different from the verification resource data corresponding to the account;
and loading the verification resource data corresponding to the account into the second type database.
6. The information processing method according to claim 1, characterized in that the method further comprises:
receiving a resource query request, and querying resource data corresponding to the account in the second type database;
and returning the resource data corresponding to the account when the resource data corresponding to the account exists in the second type database.
7. The information processing method according to claim 6, characterized in that the method further comprises:
When the resource data corresponding to the account does not exist in the second type database, acquiring a distributed lock for calculating the resource data corresponding to the account;
when the distributed lock for calculating the resource data corresponding to the account is obtained, a transaction corresponding to the account is obtained in the first type database, the resource data corresponding to the account is calculated according to the transaction corresponding to the account, and the resource data corresponding to the account is returned.
8. An information processing apparatus, characterized by comprising:
a transaction insertion unit configured to perform receiving a transaction insertion request, inserting a transaction in a first type database; wherein the first type database is used to maintain the transaction;
a data updating unit configured to perform updating of data in a second type database according to the transaction when the transaction is successfully inserted in the first type database; the second type database is used for caching data corresponding to the transaction;
and a transaction commit unit configured to commit the transaction in the first type database when the data is successfully updated in the second type database.
9. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the executable instructions to implement the information processing method of any one of claims 1 to 7.
10. A computer readable storage medium, which when executed by a processor of an electronic device, causes the electronic device to perform the information processing method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310574258.1A CN116644075A (en) | 2023-05-19 | 2023-05-19 | Information processing method, information processing apparatus, electronic device, and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310574258.1A CN116644075A (en) | 2023-05-19 | 2023-05-19 | Information processing method, information processing apparatus, electronic device, and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116644075A true CN116644075A (en) | 2023-08-25 |
Family
ID=87618114
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310574258.1A Pending CN116644075A (en) | 2023-05-19 | 2023-05-19 | Information processing method, information processing apparatus, electronic device, and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116644075A (en) |
-
2023
- 2023-05-19 CN CN202310574258.1A patent/CN116644075A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111427966B (en) | Database transaction processing method and device and server | |
| US9892153B2 (en) | Detecting lost writes | |
| US7702660B2 (en) | I/O free recovery set determination | |
| CN107787490B (en) | Direct connect functionality in a distributed database grid | |
| US8713046B2 (en) | Snapshot isolation support for distributed query processing in a shared disk database cluster | |
| US8990177B2 (en) | Lock-free transactional support for large-scale storage systems | |
| US9697253B2 (en) | Consistent client-side cache | |
| US20090210428A1 (en) | System and method for writing data dependent upon multiple reads in a distributed database database | |
| CN111522631B (en) | Distributed transaction processing method, device, server and medium | |
| US8380702B2 (en) | Loading an index with minimal effect on availability of applications using the corresponding table | |
| CN111259071B (en) | Concurrent access control method in distributed database system | |
| US20180081767A1 (en) | Enhancing consistent read performance for in-memory databases | |
| US12032560B2 (en) | Distributed transaction execution management in distributed databases | |
| US8909677B1 (en) | Providing a distributed balanced tree across plural servers | |
| US20140279960A1 (en) | Row Level Locking For Columnar Data | |
| Ghandeharizadeh et al. | Strong consistency in cache augmented SQL systems | |
| US11423003B2 (en) | Optimistic concurrency control for database transactions | |
| US9304753B2 (en) | Handling data access requests in computer program updates | |
| CN116644075A (en) | Information processing method, information processing apparatus, electronic device, and medium | |
| US11372838B2 (en) | Parallel processing of changes in a distributed system | |
| US10459810B2 (en) | Technique for higher availability in a multi-node system using replicated lock information to determine a set of data blocks for recovery | |
| CN113779052A (en) | Data updating method, device, equipment and storage medium | |
| CN112286992B (en) | Query method, distributed system, device and storage medium | |
| CN114722125A (en) | Database transaction processing method, device, equipment and computer readable medium | |
| CN117112583A (en) | Method for realizing database and cache data synchronization and method for inquiring data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |