fork of https://github.com/oxigraph/rocksdb and https://github.com/facebook/rocksdb for nextgraph and oxigraph
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
31 lines
1.5 KiB
31 lines
1.5 KiB
This document lists users of RocksDB and their use cases. If you are using RocksDB, please open a pull request and add yourself to the list.
|
|
|
|
## Facebook
|
|
At Facebook, we use RocksDB as a backend for many different stateful services. We're also experimenting with running RocksDB as a storage engine for two databases:
|
|
|
|
1. MyRocks -- https://github.com/MySQLOnRocksDB/mysql-5.6
|
|
2. MongoRocks -- https://github.com/mongodb-partners/mongo-rocks
|
|
|
|
## LinkedIn
|
|
Two different use cases at Linkedin are using RocksDB as a storage engine:
|
|
|
|
1. LinkedIn's follow feed for storing user's activities
|
|
2. Apache Samza, open source framework for stream processing
|
|
|
|
Learn more about those use cases in a Tech Talk by Ankit Gupta and Naveen Somasundaram: http://www.youtube.com/watch?v=plqVp_OnSzg
|
|
|
|
## Yahoo
|
|
Yahoo is using RocksDB as a storage engine for their biggest distributed data store Sherpa.
|
|
|
|
## CockroachDB
|
|
CockroachDB is an open-source geo-replicated transactional database (still in development). They are using RocksDB as their storage engine. Check out their github: https://github.com/cockroachdb/cockroach
|
|
|
|
## DNANexus
|
|
DNANexus is using RocksDB to speed up processing of genomics data.
|
|
You can learn more from this great blog post by Mike Lin: http://devblog.dnanexus.com/faster-bam-sorting-with-samtools-and-rocksdb/
|
|
|
|
## Iron.io
|
|
Iron.io is using RocksDB as a storage engine for their distributed queueing system.
|
|
Learn more from Tech Talk by Reed Allman: http://www.youtube.com/watch?v=HTjt6oj-RL4
|
|
|
|
|
|
|