From 01f77cb192d763a6041f79c645a7463941984ead Mon Sep 17 00:00:00 2001 From: sdong Date: Mon, 20 Jun 2016 18:01:03 -0700 Subject: [PATCH] Update USER.md to include more services at Facebook. Test Plan: Not needed. Reviewers: igor, lgalanis, andrewkr Reviewed By: andrewkr Subscribers: leveldb, andrewkr, dhruba Differential Revision: https://reviews.facebook.net/D60417 --- USERS.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/USERS.md b/USERS.md index 1dad674a9..890f3399b 100644 --- a/USERS.md +++ b/USERS.md @@ -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: