An embeddable, persistent key-value store optimized for fast flash and RAM storage with LSM-tree design.
RocksDB is an embeddable, persistent key-value store library optimized for fast storage on flash drives and RAM. It provides a high-performance storage engine with an LSM-tree design that allows flexible tradeoffs between write, read, and space amplification. Developed by Facebook, it serves as a core building block for fast key-value servers handling terabytes of data.
Developers building high-performance database systems, storage engines, or applications requiring embedded persistent key-value storage with configurable performance characteristics.
RocksDB offers superior performance for flash and RAM storage with multi-threaded compactions and tunable LSM-tree architecture, making it ideal for applications needing to store massive datasets with low latency and high throughput.
A library that provides an embeddable, persistent key-value store for fast storage.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Specifically designed for flash drives and RAM, reducing latency and improving throughput for large datasets, as highlighted in its focus on storage efficiency.
Enables parallel compaction operations, allowing high ingestion rates and efficient handling of terabytes of data in a single database.
Lightweight and can be integrated directly into applications without a separate server process, making it ideal for building custom storage engines.
Offers configurable tradeoffs between write, read, and space amplification factors, letting developers optimize for specific workload characteristics.
As a key-value store, it lacks built-in support for SQL, joins, or complex queries, requiring additional application logic or layers for such needs.
Achieving optimal performance requires deep tuning of numerous parameters related to LSM-tree mechanics, which can be complex and time-consuming.
The README warns that internal APIs may change without warning, posing risks for integrations that rely on non-public interfaces.