ACID of database transactions

ACID refers to the abbreviation of the four basic elements for correct execution of database transactions. Includes: Atomicity, Consistency, Isolation, and Durability ). A database system that supports transactions must have these four features. Otherwise

ACID refers to the abbreviation of the four basic elements for correct execution of database transactions. Includes: Atomicity, Consistency, Isolation, and Durability ). A database system that supports transactions must have these four features. Otherwise

ACID refers to the abbreviation of the four basic elements for correct execution of database transactions. Includes: Atomicity, Consistency, Isolation, and Durability ). A database system that supports transactions must have these four features. Otherwise, data correctness cannot be ensured in the Transaction process (Transaction processing), and the Transaction process cannot meet the requirements of the Transaction party.

1. Atomicity)

Atomicity indicates that a transaction is a whole. The execution is either complete or not executed. Half of the execution will not occur. The atomicity of transactions is designed based on the security of database threads. On the other hand, when half of the execution fails, the database rolls back to ensure the correctness of the data content.

2. Consistency)

The integrity constraints of the database are not damaged before and after the transaction starts. The so-called database integrity refers to the correctness, validity, and compatibility of the data in the database. That is, the transaction changes the content that the firm wants to change without affecting other content.

3. Isolation)

That is, serialization, which is similar to message queue. When multiple transactions are to be executed at the same time point, they are forcibly queued so that multiple transactions can perform database operations in an orderly manner. That is, to allow only one transaction to run at the same time point.

4. Durability)

After the transaction is completed, the database will be changed permanently without rollback. This is why the database processing model in the project architecture is called the persistence layer. This is what the firm wants to do.