Scribd
Upload
124 views

CAP & Business Drivers

The document discusses NoSQL business drivers of volume, velocity, and variability as well as agility. It then explains the CAP theorem and how NoSQL databases prioritize availability and eventual consistency over strong consistency. It also discusses how NoSQL ensures high uptime, continuous access, and can handle network failures and scale horizontally while preserving data integrity.

Uploaded by

Akshay
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
124 views

CAP & Business Drivers

The document discusses NoSQL business drivers of volume, velocity, and variability as well as agility. It then explains the CAP theorem and how NoSQL databases prioritize availability and eventual consistency over strong consistency. It also discusses how NoSQL ensures high uptime, continuous access, and can handle network failures and scale horizontally while preserving data integrity.

Uploaded by

Akshay
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

NoSQL Business Drivers

- Volume
NoSQL Business Drivers
- Velocity
NoSQL Business Drivers
- Variability
NoSQL Business Drivers
- Agility
CAP Theorem Explained
Consistency Availability
The CAP Theorem states that it is While traditional databases prioritize
impossible for a distributed data strong consistency, NoSQL
store to simultaneously provide databases often focus on availability,
more than two out of the following ensuring that every request receives
three guarantees: Consistency, a response about whether it
Availability, and Partition tolerance. succeeded or failed.

Partition Tolerance
NoSQL databases are designed to remain operational even in the presence of
network partitions, ensuring that the system can continue to function despite
network failures and communication breakdowns.
Consistency in CAP Theorem
Strong Consistency
1 Traditional databases typically prioritize strong consistency, ensuring
that all nodes in the system have the same data at the same time.

Eventual Consistency
NoSQL databases, on the other hand, often embrace eventual
2
consistency, where data changes are propagated to all nodes over
time, allowing temporary inconsistencies to exist.
Availability in CAP Theorem

99.999% 24/7
High Uptime Continuous Access
NoSQL databases are designed to provide NoSQL databases enable continuous access
extremely high availability, often aiming for at to data and services, ensuring that
least 99.999% uptime to minimize service applications can operate without interruption.
disruptions.
Partition Tolerance in CAP
Theorem
1 Network Failures
NoSQL databases are designed to handle network failures and
communication breakdowns by preserving data availability within the
system.

2 Scalable Architectures
Partition tolerance ensures that NoSQL databases can be scaled
horizontally across multiple nodes without sacrificing data integrity or
availability.
Trade-Offs and Considerations When
Choosing a NoSQL Database
Consistency Model NoSQL databases offer various consistency
models ranging from strong to eventual
consistency, each with its benefits and
trade-offs.

Performance Requirements Considering the specific performance


needs of the application is crucial when
selecting a NoSQL database, as different
databases excel in different performance
areas.

Data Structure The data structure and schema flexibility


provided by NoSQL databases should align
with the requirements for data storage
and access patterns.

You might also like