Skip to content

Commit

Permalink
Update USER.md to include more services at Facebook.
Browse files Browse the repository at this point in the history
Test Plan: Not needed.

Reviewers: igor, lgalanis, andrewkr

Reviewed By: andrewkr

Subscribers: leveldb, andrewkr, dhruba

Differential Revision: https://reviews.facebook.net/D60417
  • Loading branch information
siying committed Jul 6, 2016
1 parent eb53c05 commit 01f77cb
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion USERS.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,16 @@
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:
At Facebook, we use RocksDB as storage engines in multiple data management services and a backend for many different stateful services, including:

1. MyRocks -- https://github.com/MySQLOnRocksDB/mysql-5.6
2. MongoRocks -- https://github.com/mongodb-partners/mongo-rocks
3. ZippyDB -- Facebook's distributed key-value store with Paxos-style replication, built on top of RocksDB.[*] https://www.youtube.com/watch?v=DfiN7pG0D0khtt
4. Laser -- Laser is a high query throughput, low (millisecond) latency, key-value storage service built on top of RocksDB.[*]
4. Dragan -- a distributed graph query engine. https://code.facebook.com/posts/1737605303120405/dragon-a-distributed-graph-query-engine/
5. Stylus -- a low-level stream processing framework writtenin C++.[*]

[*] https://research.facebook.com/publications/realtime-data-processing-at-facebook/

## LinkedIn
Two different use cases at Linkedin are using RocksDB as a storage engine:
Expand Down

0 comments on commit 01f77cb

Please sign in to comment.