Back to docsTransactions
Transactional messaging
TCC-based transactions that keep sending and scheduling consistent.
Site summary · Summary
Outline
Message sending and scheduling stay consistent under the same transaction boundary.
TCC coordinates the try, confirm and cancel phases across services.
Related module
broker/ · common/
Transaction flow and the shared message model.
Start here in the repository.
Related docs
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/
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/
ArchitectureRepository doc
Architecture overview
How the modules are split, what runs where, and where this fork differs from RocketMQ.
docs/ · broker/