Common thing in DB which supports ACID principle

I was just undergoing training on Neo4j db. It is basically a graph database which supports ACID principle.

I see it uses transaction logs similar to Microsoft SQL server. Whenever the server crashes it will roll back all transactions, and go back to a stable state.

First thing to support ACID is you need to keep track of transactions in some manner to roll back in case of failure. And that means there should be a transaction log supported. Point is if we hear ACID then there should be a transaction log.

 I will keep updating this blog to generalize design pattern around ACID systems. You are welcome to share your thoughts 🙂