RocketMQ bookshelf

Two project volumes that read the code with you, plus three published RocketMQ books the community keeps coming back to.

Publication details follow the publishers' own records. Project volumes are online documents, not print books.

Project volumes

Written alongside the rewrite and kept in the repository.

Online
Clean-RocketMQRocketMQ 源码解析与优化(上)Vol. 1 · source analysis

RocketMQ 源码解析与优化(上)

Module-by-module reading notes on the RocketMQ core: name server, storage, message flow and the paths worth optimising.

SourceArchitecture
Read on GitHub
Clean-RocketMQRocketMQ 源码解析与优化(下)Vol. 2 · refactor and optimisation

RocketMQ 源码解析与优化(下)

How the analysis turns into a rewrite: boundaries, sharding and the trade-offs behind Clean-RocketMQ.

RefactorPerformance
Read on GitHub

Published books

Independent authors' work on RocketMQ, chosen for different reading goals.

RocketMQRocketMQ 技术内幕:RocketMQ 架构设计与实现原理2nd edition

RocketMQ 技术内幕:RocketMQ 架构设计与实现原理

Ding Wei, Zhang Deng, Zhou Jifeng

China Machine Press · 2021

Walks through RocketMQ internals module by module: name service, storage, replication and the communication layer.

InternalsArchitectureISBN 9787111690924
RocketMQRocketMQ 实战与原理解析2018

RocketMQ 实战与原理解析

Yang Kaiyuan

China Machine Press · 2018

First half covers production setup, high availability and Spring Boot integration; second half reads the source behind name service, replication and Netty communication.

PracticeSourceISBN 9787111600251
RocketMQRocketMQ 实战2022

RocketMQ 实战

Ding Wei, Liang Yong

Posts & Telecom Press · 2022

Engineering-oriented: sending and consuming, Spring integration, cluster deployment, monitoring and typical failure cases.

PracticeOperationsISBN 9787115596857

How to read them in order

  1. 1

    Get the model first

    Start with a practice-oriented book if you have not run a cluster yet.

  2. 2

    Then read the internals

    Move to the internals book once the message flow feels familiar.

  3. 3

    Finally follow the rewrite

    Use the project volumes to see where this project diverges, and why.