<aside> 💡 Notes Last Reviewed : 16 Sept, 7pm

</aside>

• NoSQL Landscape

• link for blog post:

• From the point of view of data intensive applications

Consistency:

• All clients have same view of data at same time
• Note actually ACID transactions in db

Partition-tolerance:

• System continues to operate despite network partitions.
• No single point of failure
• Infinite scale out

Availability:

• Each client can always read and write
• Total redundancy
• What does a traditional CAP theorem says?

BUT !!

Can we really compromise the partition tolerance?

The future of databases is primarily based on distribution. (Big Data trends ..)

A proper understanding of CAP theorem is essential to making decisions about the future of distributed database design. Misunderstanding can lead to inappropriate design choices.

Though the ACID (atomicity, Consistency, Isolation, Durability) properties of Relation Databases are powerful and we would like to have them in our database. But its unfortunately impossible to have availability , consistency & partition tolerance all in at once. .... Well really? 🤔

Popular misconception is 2 or of 3.

An important observation is that in larger distributed-scale systems, network partitions are a given; therefore, consistency and availability cannot be achieved at the same time

• 12 Years later: Prof Eric - father of CAP theorem