Please enable JavaScript.
Coggle requires JavaScript to display documents.
Acid vs Base Diagram - Coggle Diagram
Acid vs Base Diagram
ACID properties
Consistency: The transaction satisfies the integrity constraints. In consequence if the initial state is consistent then the final state is also consistent.
Isolation: A transaction is not affected by the behavior of other concurrent transactions. In consequence its intermediate states are not exposed
-
Durability: The effect of a successfully committed transaction will last “forever”. Regardless of any system failure
What is a transaction?
A transaction is a unit of work that has the properties of Atomicity, Coherence, Isolation and Durability (ACID).
CAP Theorem
It is impossible for a distributed computer system to simultaneously provide all three of the following guarantees:
-
Availability: failures of one node do not prevent other survivors from continuing to function (guarantee that each request receives a response as to whether it succeeded or failed).
Partition tolerance: the system continues to operate despite arbitrary partitioning due to network failures.
BASE (Basically Available, Condition Soft, Eventually Consistent)
-
Eventual Consistency: At some point in the future, data will converge to a consistent state; delayed consistency, as opposed to immediate consistency of the ACID properties.
Basic Availability: fulfill request, even in partial consistency.
BASE (Basically Available, Condition Soft, Eventually Consistent)
Given the poor consistency of BASE, developers need to be more knowledgeable and rigorous about data consistency if they choose a BASE warehouse for their application.
Planning around the limitations of BASE can sometimes be a major disadvantage when compared to the simplicity of ACID transactions.
A fully ACID database is perfect for use cases where reliability and data consistency are essential.
-