basho/riak

Riak is a decentralized datastore from Basho Technologies.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 11 minutes ago
Type:Server / PlatformCategory(s):NoSQL, Key-Value & CachesDatabases & Storage
Added to GitGenius on September 17th, 2026
Created on April 16th, 2010
Open Issues & Pull Requests: 150 (+0)
GitHub issues: Enabled
Number of forks: 522
Total Stargazers: 4,026 (+0)
Total Subscribers: 247 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Riak is a decentralized datastore designed for distributed systems that require high availability and fault tolerance across multiple nodes.

Riak addresses the challenge of building reliable data systems in environments where node failures are inevitable. It uses a masterless, peer-to-peer architecture where every node is equal, eliminating single points of failure. Data is replicated across multiple nodes automatically, and the system can continue operating even when some nodes become unavailable. Riak employs consistent hashing to distribute data across the cluster and uses vector clocks to track causality and resolve concurrent updates.

Riak suits teams building applications that prioritize availability and partition tolerance over immediate consistency. It works well for use cases where eventual consistency is acceptable, such as session storage, user profiles, or other scenarios where temporary divergence between replicas can be tolerated and resolved. Organizations should evaluate whether their application requirements align with this trade-off before adoption. The system is particularly valuable for geographically distributed deployments where network partitions between data centers are a real concern.

The project maintains active development with regular updates to core functionality and operational tooling. The codebase shows ongoing work on cluster management and data replication mechanisms. Documentation is actively maintained to reflect current capabilities and deployment practices. The project demonstrates sustained engineering effort across multiple areas of the system rather than focusing narrowly on a single component.