CAP THEOREM NOSQL

All databases should ideally provide the following features:

CONSISTENCY

Consistency is when an end user must be able to see the latest data at all times.

AVAILABILITY

Availability is when every database request must be responded by the server.

PARTITION TOLERANCE 

When two systems cannot talk to each other in a network, it is called network partition. Our DB system should continue to function even if there is a network partition.

 Consistency, Availability and Partition Tolerance is usually abbreviated as CAP.

CAP THEOREM'S DEFINITION

This theorem is stated by Eric Brewer. According to this theorem it is impossible for a distributed system to guarantee all three (Consistency, Availability and Partition Tolerance).

NoSQL databases are partition tolerant. In case of a network partition, there is a tradeoff between consistency and availability – some NoSQL systems give importance to Consistency while others give importance to Availability.
CAP THEOREM
Oracle (it is SQL database) offers Consistency and Availability.

 Cassandra (a NoSQL database) offers Availability and Partition Tolerance.

 MongoDB, Neo4 (a NoSQL database) offers Consistency and Partition Tolerance

 Thanks for reading.

 Comment your views guys!!!

Comments

Post a Comment

Popular posts from this blog

TYPES OF NOSQL DATABASE

Mainly, NoSQL database are of four types namely Key-Value Stores. (e.g. Riak, Redis, MemcacheDB) Column-family Stores .(e.g. HBase, Cassandra) Document-Oriented Database . (e.g. MongoDB, CouchDB) Graph Database . (e.g. Neo4J, HyperGraphDB, InfoGrid) We will discuss each type one by one. 1. KEY-VALUE STORES Key-Value Store is the simplest form of NoSQL database. It stores information as key  and its value. These are similar to a dictionary or a hashtable. Fig 1.a. Example of Key-Value Stores Each key is unique and note that we can search only by using keys, not by values. They are inefficient when you need to query or update only a part of the value. Key-Value Store are used to implement shopping carts, user sessions, customer preferences etc. 2. COLUMN- FAMILY STORES Since key-value stores do not allow updating only a part of value and we cannot fetch data by using values rather than key. Column family databases store each column separa
Read more