Scribd
Upload
23 views5 pages

Base Properties

Uploaded by

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

Base Properties

Uploaded by

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

 What are BASE Properties?

 BASE Properties is an acronym that stands for Basically Available, Soft


state, Eventual consistency.
 It is a set of principles that guide the design and implementation of distributed
databases and data storage systems.
 Unlike traditional ACID (Atomicity, Consistency, Isolation, Durability)
properties, which prioritize strong consistency and durability, BASE Properties
prioritize availability and high performance.
How do BASE Properties work?
BASE Properties aim to handle large volumes of data and enable scalability and flexibility
in distributed systems. Here is a breakdown of what each property means:
•Basically Available: BASE systems prioritize availability over strong consistency. This means
that even in the face of failures or concurrent updates, the system remains operational and
accessible to users.
•Soft state: BASE systems allow for temporary inconsistency or partial updates. The state of the
system can be transiently inconsistent during concurrent updates, but the system is eventually
brought back to a consistent state.
•Eventual consistency: BASE systems guarantee that updates will eventually propagate and
reach a consistent state across all replicas or nodes. However, immediate consistency is not a
requirement, and there may be a delay in achieving consistency.
Why are BASE Properties important?
BASE Properties are important for businesses and organizations dealing with big data and real-
time analytics. They offer several benefits:
•Scalability: BASE systems can handle large volumes of data and scale horizontally by adding
more nodes or servers to the system.
•High Availability: BASE systems prioritize availability, ensuring that the system remains
accessible to users even during failures or updates.
•Performance: By relaxing strict consistency requirements, BASE systems can achieve higher
performance and throughput compared to ACID systems.
•Flexibility: BASE systems allow for flexible data models and schema evolution, making it
easier to adapt to changing business needs and accommodate evolving data structures.
 CAP theorem
 It is very important to understand the limitations of the NoSQL database. NoSQL can not
provide consistency and high availability together. This was first expressed by Eric Brewer in
CAP Theorem.
 CAP theorem or Eric Brewers theorem states that we can only achieve at most two out of three
guarantees for a database: Consistency, Availability, and Partition Tolerance.
 Consistency means that all nodes in the network see the same data at the same time.

 Availability is a guarantee that every request receives a response about whether it was
successful or failed. However, it does not guarantee that a read request returns the most recent
write.
 Partition Tolerance is a guarantee that the system continues to operate despite arbitrary
message loss or failure of part of the system.
 In other words, even if there is a network outage in the data center and some of the computers
are unreachable, still the system continues to perform.
 Out of these three guarantees, no system can provide more than 2 guarantees.
 Since in the case of distributed systems, the partitioning of the network is a must, the tradeoff
is always between consistency and availability.

You might also like