basho/riak
Riak
Riak is a decentralized NoSQL key-value store designed for high availability and fault tolerance. It is a Dynamo-style distributed database that utilizes consistent hashing and eventual consistency to scale data across a cluster of nodes.
The system functions as a geo-replicated datastore, synchronizing data across multiple physical locations to provide disaster recovery and maintain availability during regional outages. It employs a multi-master replication model, allowing writes to any node in the cluster.
The platform covers broad capability areas including decentralized cluster coordination, high availability data management, and large-scale data expiry. It manages data durability through quorum-based consistency and write verification, while utilizing specialized data structures to merge concurrent updates automatically.
Features
- Dynamo-Style Distributed Databases - Implements a partitioned data store based on the Dynamo architecture using consistent hashing and eventual consistency for massive scalability.
- Decentralized NoSQL Stores - Provides a non-relational storage system that operates across a peer-to-peer network for high availability.
- Cross-Location Data Replication - Synchronizes data across multiple physical locations to ensure disaster recovery and low-latency access through geographic distribution.
- Distributed Storage - Employs a decentralized storage architecture that distributes data across multiple nodes to eliminate single points of failure.
- Geographic Data Replication - Synchronizes data across geographically dispersed data centers to ensure disaster recovery and high availability.
- Multi-Master Replication - Supports a multi-master replication model allowing write operations to any node in the cluster.
- Quorum-Based Consistency - Ensures data durability and consistency by requiring a minimum number of node acknowledgments for operations.
- Gossip-Based Cluster Membership - Propagates node health and cluster membership information using a gossip-based peer-to-peer protocol.
- Decentralized Cluster Coordination - Coordinates application state and node availability across a distributed network without a central control plane.
- Database High Availability - Ensures continuous database availability by distributing replicas and verifying write durability across nodes.
- Consistent Hashing Distribution - Uses a consistent hashing ring to distribute data across nodes and maintain balance during cluster changes.
- Data Synchronization and Consistency - Provides a decentralized system that ensures data replicas eventually converge to the same state across a distributed network.
- Conflict-Free Replicated Data Types - Provides conflict-free replicated data types to automatically merge concurrent updates without central coordination.
- Large Scale Data Expiry - Handles the lifecycle of objects at scale by purging expired data and tombstones to maintain storage efficiency.
- Data Expiry Management - Manages the lifecycle of stored objects by deleting expired data and removing tombstones to reclaim storage.
- Anti-Entropy Replication - Implements background reconciliation of data replicas using Merkle trees to repair inconsistencies across the cluster.
- Write Acknowledgement Strategies - Verifies write durability by requiring a minimum number of physical nodes to acknowledge a write.
- Cluster State Synchronization - Provides a coordination system that reconciles cluster state through a combination of full-sync and real-time replication.
- Database Engines - Decentralized key-value datastore for high availability.
- Key-Value Stores - Decentralized, fault-tolerant key-value datastore.
Star history
How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.
