ACID

ACID rules to be sure

A database must be very consistent in most cases. A financial database behind banking software, for example, cannot afford to miss a few transfers. Likewise with databases behind ERP or CRM software. Your personnel and stock management must remain consistent and correct, otherwise your accounting, among other things, will go haywire. That's why these types of databases must comply with four rules.

  • Atomic: A CRUD transaction must be consistent OR void. Nothing anything between the two. 
  • Consistent: A CRUD transaction must produce a new "status" or stay with the old status. 
  • Isolated: If 2 CRUD transactions are executed at the same time, they must not affect each other. 
  • Durable: A transaction remains valid. If you make a modification, it remains applicable in the future.
Next page