Cloud Storage: Key-value Stores/NoSQL
Key-Value Stores provide a flexible, schema-less architecture designed for high scalability and availability, essential for cloud applications. Apache Cassandra and HBase serve as two prominent examples of Key-Value Stores, each with distinctive architectures and operational approaches to data management. The distinction between the eventual consistency of Cassandra and the strong consistency of HBase highlights different strategies in handling distributed data in cloud environments.
Sections
Navigate through the learning materials and practice exercises.
What we have learnt
- Key-Value Stores are designed for massive horizontal scalability and high availability.
- Apache Cassandra operates with a distributed architecture providing eventual consistency, while HBase offers strong consistency on single-row operations.
- Distributed systems must balance consistency, availability, and partition tolerance as defined by the CAP theorem.
Key Concepts
- -- KeyValue Store
- A type of NoSQL database that stores data as a collection of key-value pairs, allowing for flexible data modeling.
- -- Eventual Consistency
- A consistency model where updates to a data item will eventually propagate such that all replicas reflect the same value over time.
- -- Strong Consistency
- A consistency model that ensures clients read the most recent write; used in some NoSQL databases like HBase for single-row operations.
- -- CAP Theorem
- A principle that states it is impossible for a distributed data store to simultaneously provide all three guarantees: Consistency, Availability, and Partition tolerance.
Additional Learning Materials
Supplementary resources to enhance your learning experience.