0

I'm looking to implement a tiered storage solution with RocksDB, where hot data resides on fast storage (like SSDs) and cold data is moved to slower, more cost-effective storage (like HDDs).

I'm aware that RocksDB has some built-in, experimental features for tiered storage. Is this functionality considered stable and ready for production environments at this time?

If it's not yet recommended for production use, what are the common, industry-standard methods or best practices for achieving this kind of hot/cold data separation with RocksDB?

jonrsharpe
123k31 gold badges278 silver badges489 bronze badges
asked Sep 12, 2025 at 5:04

0

Know someone who can answer? Share a link to this question via email, Twitter, or Facebook.

Your Answer

Draft saved
Draft discarded

Sign up or log in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

Post as a guest

Required, but never shown

By clicking "Post Your Answer", you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.