Open source · Apache-2.0
Next-Gen RocketMQFastest Transactional Messaging
RocketMQ-compatible. Rebuilt from scratch. 5× the throughput.Clean at the core. Built to evolve.
Schematic of the sharded write path, not a benchmark capture.
A better RocketMQ
Protocol compatible · smooth migration · higher performance · cleaner · easier to evolve
High throughput
- 5x+ RocketMQ throughput
- 25x+ RabbitMQ throughput
- 200+ performance test cases
Distributed transactions
- Transactional messages
- Transactional delay
- Transactional exchange
- Transactional event graph
Clean architecture
- DDD-based domain modelling
- Infrastructure and network services layered apart
- Storage separated from compute
- Cloud-native capabilities, continuously improved
Multi-protocol support
- RocketMQ gRPC
- RocketMQ remoting
- RabbitMQ AMQP 0.91
- RabbitMQ AMQP 1.0
Clean code
- Clear naming and naming conventions
- Controlled object size, sensible packaging
- Lightweight micro-framework
- Containerised and componentised
Continuous evolution
- Principle-driven development
- Open-source driven, transparent collaboration
- Knowledge captured as books
- Source and theory evolving together
Projects in numbers
1,800+ days of RocketMQ study 600+ days of from-scratch rewrite.
< 50K
lines of core code
RocketMQ is the simplest message queue
> 100K
lines of refactor
RocketMQ-wolf, 4 years of production env practice.
> 5K
lines of comments
Rocketmq-comment, For study, Also for our books.
> 5
times Throughput gain
Clean-RocketMQ, rewritten from scratch, 120K+ lines.
> 5
RocketMQ books
Systematic accumulation: cycle of theory and practice
Three commands to a local build
Clone, build with Maven, then read the module that matters to you. No hosted service, no account.
- 1
Clone
Get the repository with its full commit history.
- 2
Build
A single Maven build produces the modules: broker, store, registry, rpc, common.
- 3
Read the module you need
Start from the docs index and open the module behind it.
git clone https://github.com/wolforest/clean-rocketmq.git
cd clean-rocketmq
mvn -DskipTests packageModule boundaries double as the reading path: start with how broker accepts a message, then follow it into store.
Progress and roadmap
What works today, what is partly there, and what is still open.
- Available
Core messaging (pub/sub, ordered, delay, transactions, registry, RPC)
Available and used as the base for everything below.
- Available
CommitLog sharding
Sharded write path is in place; the reported throughput gain comes from it.
- Partially done
Master-slave and storage-compute separation
Replication works; separation is partly complete and still moving.
- In progress
Richer scheduling and transaction features
More scheduling types and stronger transactional guarantees are being added.
- Planned
Raft and cloud native
Planned. No production-ready implementation today.
Docs and source analysis
Architecture notes written for reading, plus two source-analysis books that follow the code module by module.
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.
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).
Architecture overview
How the modules are split, what runs where, and where this fork differs from RocketMQ.
Build it with the maintainers
Issues, code and study groups — pick the channel that fits your question.
See all channels