Design disk-backed HNSW graph traversal over Linux io_uring, tune Raft shard consensus rebalancing, and write hand-vectorized distance functions.
RocksDB in Production Rust: Architecture & Open Roles
Embedded key-value storage engine & Rust FFI state persistence
1. Why Teams Deploy RocksDB
Backed by Meta's C++ LSM engine via the `rust-rocksdb` FFI wrapper, RocksDB serves as the local persistent state store for TiKV, SurrealDB, Mysten Labs' Sui validators, and dozens of distributed storage nodes. While pure-Rust alternatives are growing, production engineers still spend significant time tuning RocksDB column families and block caches.
2. RocksDB Kernel & Memory Internals
Crossing the C++ FFI boundary carelessly can copy megabytes of values unnecessarily. Experienced Rust storage engineers use `DBPinnableSlice` (`get_pinned_cf`) to read zero-copy slices directly from RocksDB's uncompressed block cache, batch writes atomically with `WriteBatch`, and configure custom Merge Operators and Prefix Seek extractors for MVCC timestamped keys.
3. RocksDB Interview & Hiring Bar
Database and blockchain core teams look for engineers who have diagnosed RocksDB write stalls (L0 file accumulation), tuned `max_background_jobs`, and managed jemalloc memory fragmentation.
Open RocksDB Engineering Positions (4)
Optimize QUIC stake-weighted QoS packet ingest, eliminate lock contention in AccountsDB, and build high-throughput gRPC streaming indexers.
Benchmark QUIC validator-to-validator block dissemination, tune RocksDB state pruning, and fuzz the Move VM bytecode interpreter.