RocksDB vs ToroDB: What are the differences?
RocksDB: Embeddable persistent key-value store for fast storage, developed and maintained by Facebook Database Engineering Team. RocksDB is an embeddable persistent key-value store for fast storage. RocksDB can also be the foundation for a client-server database but our current focus is on embedded workloads. RocksDB builds on LevelDB to be scalable to run on servers with many CPU cores, to efficiently use fast storage, to support IO-bound, in-memory and write-once workloads, and to be flexible to allow for innovation; ToroDB: Open source, document-oriented, JSON database that runs on top of PostgreSQL. ToroDB is an open source, document-oriented, JSON database that runs on top of PostgreSQL, providing storage and I/O savings and ACID semantics. ToroDB is MongoDB-compatible, so you can use Mongo clients to connect to it.
RocksDB and ToroDB belong to "Databases" category of the tech stack.
Some of the features offered by RocksDB are:
- Designed for application servers wanting to store up to a few terabytes of data on locally attached Flash drives or in RAM
- Optimized for storing small to medium size key-values on fast storage -- flash devices or in-memory
- Scales linearly with number of CPUs so that it works well on ARM processors
On the other hand, ToroDB provides the following key features:
- Document-oriented (JSON)
- Store data reliabily and durably with PostgreSQL
- Use MongoDB clients to connect to it
RocksDB and ToroDB are both open source tools. RocksDB with 14.3K GitHub stars and 3.12K forks on GitHub appears to be more popular than ToroDB with 10 GitHub stars and 2 GitHub forks.