A method for processing a series of database transactions requested sequentially by a plurality of applications (11, 21, 31) comprising a first application and a second application, the method performed by a computing device, the method comprising: monitoring operations of the first application and the second application by means of at least one recording module (13, 23, 33); recording, by using one of the at least one recording modules (13, 23, 33), a first transaction requested to a first database by the first application, in association with a transaction group identifier, in a shared storage, wherein the request of the first transaction to the first database is associated with access to the first database, wherein the first transaction is a data update transaction or a data deletion transaction; recording, by using one of the at least one recording modules (13, 23, 33), a second transaction requested to a second database by the second application called by the first application, among the plurality of applications, in association with the transaction group ID, in the shared storage, wherein the request of the second transaction to the second database is associated with access to the second database, wherein the second transaction is a data update transaction or a data deletion transaction; determining whether an error has occurred during processing of the second transaction; rolling back, by using a rollback module, the second transaction targeted to the second database in response to a determination that the error has occurred during processing of the second transaction; identifying the first transaction, based on the transaction group ID; and rolling back, by using the rollback module, the first transaction targeted to the first database, wherein, when the first transaction is a data update transaction, the recording of the first transaction comprises recording, in the shared storage, a value of a data entry to be updated, before an update by the first transaction; and the rolling back of the first transaction comprises rolling back the first transaction using the recorded value of the data entry to be updated, and wherein, when the first transaction is a data deletion transaction, the recording of the first transaction comprises recording, in the shared storage, a value of a data entry to be deleted, before deletion by the first transaction; and the rolling back of the first transaction comprises rolling back the first transaction using the recorded value of the data entry to be deleted, wherein the recording the first and second transactions and the rolling back the first and second transactions is performed independently of operations of the first application and the second application. monitoring operations of the first application and the second application by means of at least one recording module (13, 23, 33); recording, by using one of the at least one recording modules (13, 23, 33), a first transaction requested to a first database by the first application, in association with a transaction group identifier, in a shared storage, wherein the request of the first transaction to the first database is associated with access to the first database, wherein the first transaction is a data update transaction or a data deletion transaction; recording, by using one of the at least one recording modules (13, 23, 33), a second transaction requested to a second database by the second application called by the first application, among the plurality of applications, in association with the transaction group ID, in the shared storage, wherein the request of the second transaction to the second database is associated with access to the second database, wherein the second transaction is a data update transaction or a data deletion transaction; determining whether an error has occurred during processing of the second transaction; rolling back, by using a rollback module, the second transaction targeted to the second database in response to a determination that the error has occurred during processing of the second transaction; identifying the first transaction, based on the transaction group ID; and rolling back, by using the rollback module, the first transaction targeted to the first database, wherein, when the first transaction is a data update transaction, the recording of the first transaction comprises recording, in the shared storage, a value of a data entry to be updated, before an update by the first transaction; and the rolling back of the first transaction comprises rolling back the first transaction using the recorded value of the data entry to be updated, and wherein, when the first transaction is a data deletion transaction, the recording of the first transaction comprises recording, in the shared storage, a value of a data entry to be deleted, before deletion by the first transaction; and the rolling back of the first transaction comprises rolling back the first transaction using the recorded value of the data entry to be deleted, wherein the recording the first and second transactions and the rolling back the first and second transactions is performed independently of operations of the first application and the second application.