Back to docsStorage
CommitLog sharding
Why the write path is sharded, what it changes for throughput, and what it does not promise.
Site summary · Summary
Outline
With a single CommitLog, every write lands on the same append path.
Sharding spreads that pressure across write paths instead of scaling one machine.
Related module
store/
CommitLog and the storage layer.
Start here in the repository.
Related docs
StorageSite summary
Inside CommitLog sharding: where 5x throughput comes from
A walk through the write path: the global lock, how shards and offset encoding work, what dispatch decoupling changes, and when the 5x figure applies (project self-test).
store/ · commitlog/
StorageSite summary
Storage-compute separation
Splitting the domain layer from storage, and how much of it is finished today.
store/ · broker/
ArchitectureSite summary
After a from-scratch rewrite, why stay compatible with RocketMQ
A rewrite was about redrawing boundaries, not abandoning the ecosystem. Why compatibility is the migration path, and what it costs inside the code.
docs/ · architecture/