Sorry the decision to archive Rocksplicator wasn't documented clearly.

In short: we moved Rocksplicator to Pinterest's internal mono repo for better toolings around build (bazel, clang) and CI/CD integration, and faster dev velocity. RocksDB is still heavily used at Pinterest in many services, and the fundamental Rocksplicator architecture hasn't been changed.

Another reason we made this move is because we didn't see active external contribution to this project outside Pinterest, despite we know there are some open-source projects like https://github.com/apache/kvrocks that are inspired by Rocksplicator, and some companies have their internal forked version.

Since then, our internal version Rocksplicator has evolved quite a bit, to name a few major ones:

Admin server and RPC server separation: The current open-source version uses a single thrift server for both which poses reliability and scalability issues
Incremental backup & restore
RocksDB upgrade to V8
fbThrift/folly upgrade to v2024.06.17.00
And lots of code hygiene and quality improvement.

You are still welcome to build solution around Rocksplicator, but we won't be able to provide continuous support for it at the moment. In fact we have received quite a few reach out from peer companies on developing similar RocksDB based storage solution and would benefit from what Rocksplicator can offer.

So sorry folks, Rocksplicator is archived, for now, until maybe Rocksplicator V2 when the timing is right :p

Archiving rocksplicator project #636

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions