rosedblabs/rosedb

Lightweight, fast and reliable key/value storage engine based on Bitcask.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 51 minutes ago
Type:Library / SDKCategory(s):NoSQL, Key-Value & CachesDatabases & Storage
Added to GitGenius on September 14th, 2026
Created on December 6th, 2020
Open Issues & Pull Requests: 8 (+0)
GitHub issues: Enabled
Number of forks: 643
Total Stargazers: 4,885 (+0)
Total Subscribers: 43 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.6 days
Mean response time: 8.2 days
90th percentile: 8.2 days
Tracked items: 11

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 732 days
Stale 30+ days: 2
Stale 90+ days: 2

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

RoseDB is a key-value storage engine written in Go that implements the Bitcask storage model.

RoseDB addresses the need for fast, predictable key-value storage by adopting Bitcask's log-structured, append-only design. Data is written sequentially to WAL (Write Ahead Log) files, eliminating random disk seeks during writes and enabling high throughput. An in-memory index maps keys to their disk locations, allowing any value to be retrieved with at most a single disk seek. This architecture delivers low latency, predictable performance for both reads and writes, and handles datasets larger than available RAM without degradation.

RoseDB suits embedded systems and applications requiring reliable, high-throughput key-value storage where predictable latency matters. It is production-ready with existing deployments in use. The tool's append-only format simplifies crash recovery and backup operations compared to traditional databases. The README does not name alternative implementations for direct comparison.

The project maintains active development with developers responding to feature requests through issues and pull requests. Crash recovery is designed to be fast and bounded, reviewing only partially written records at file tails and verifying CRC data for consistency.