RocketMQ消息中間件實(shí)戰(zhàn)派（上下冊(cè)）

第1 篇 基礎(chǔ)
第1 章 初識(shí)RocketMQ ·························.2
1.1 認(rèn)識(shí)分布式架構(gòu) ····························.2
1.1.1 什么是分布式 ·······················.2
1.1.2 什么是架構(gòu) ··························.3
1.1.3 分布式架構(gòu)的冰與火 ··············.5
1.2 認(rèn)識(shí)RocketMQ ·····························.7
1.2.1 什么是RocketMQ ··················.7
1.2.2 RocketMQ 與分布式架構(gòu) ·······.12
1.3 搭建RocketMQ 環(huán)境 ····················.13
1.3.1 了解RocketMQ 相關(guān)的安裝包 .13
1.3.2 搭建單Master 的單機(jī)環(huán)境 ·····.15
1.3.3 搭建多Master 的集群環(huán)境 ·····.15
1.3.4 搭建單Master 和單Slave 的集群環(huán)境 ·································.16
1.3.5 【實(shí)例】搭建Raft 集群環(huán)境 ··.18
1.4 RocketMQ 5.0 的新特性 ················.20
第2 章 實(shí)現(xiàn)通信渠道 ··························.22
2.1 認(rèn)識(shí)通信渠道 ·····························.22
2.2 通信渠道的架構(gòu) ··························.25
2.2.1 認(rèn)識(shí)Netty ·························.25
2.2.2 RocketMQ 通信渠道的架構(gòu) ····.29
2.3 使用Netty 實(shí)現(xiàn)通信渠道的原理 ······.33
2.3.1 實(shí)現(xiàn)通信渠道的通信協(xié)議 ······.33
2.3.2 實(shí)現(xiàn)客戶端通信渠道 ············.38
2.3.3 實(shí)現(xiàn)服務(wù)端通信渠道 ············.41
2.4 使用客戶端連接服務(wù)端 ·················.47
2.4.1 分析模塊通信渠道的類型 ······.48
2.4.2 連接服務(wù)端 ························.50
2.5 【實(shí)例】修改通信渠道客戶端和服務(wù)端的線程模型 ·······················.54
第3 章 消息路由信息的無(wú)狀態(tài)存儲(chǔ)和管理 ······································.61
3.1 了解消息路由信息 ·······················.61
3.2 Name Server 的架構(gòu) ·····················.68
3.2.1 認(rèn)識(shí)無(wú)狀態(tài)架構(gòu) ··················.68
3.2.2 認(rèn)識(shí)Name Server 架構(gòu) ·········.69
3.2.3 認(rèn)識(shí)地址服務(wù)架構(gòu) ···············.72
3.2.4 【實(shí)例】用地址服務(wù)動(dòng)態(tài)更新客戶端中的Name Server 節(jié)點(diǎn)的地址信息 ··························.74
3.3 “使用Name Server 存儲(chǔ)和管理消息路由信息”的原理 ·······················.77
3.3.1 Name Server 的啟動(dòng)流程 ·······.77
3.3.2 注冊(cè)Broker Server ···············.84
3.3.3 取消注冊(cè)的業(yè)務(wù)場(chǎng)景和取消注冊(cè)Broker Server ···············.89
3.3.4 存儲(chǔ)和管理消息路由信息 ······.93
3.4 【實(shí)例】啟動(dòng)多個(gè)Name Server 節(jié)點(diǎn)，模擬故障以驗(yàn)證Name Server 節(jié)點(diǎn)的無(wú)狀態(tài)性 ·································.101
第4 章 生產(chǎn)消息和消費(fèi)消息 ···············.104
4.1 生產(chǎn)和消費(fèi)消息的模式 ················.104
4.1.1 生產(chǎn)消息 ··························.104
4.1.2 消費(fèi)消息 ··························.110
4.2 消費(fèi)消息的類型 ·························.116
4.2.1 集群消息 ··························.116
4.2.2 廣播消息 ··························.118
4.2.3 順序消息 ··························.119
4.2.4 并發(fā)消息 ··························.125
4.2.5 延遲消息 ··························.126
4.2.6 事務(wù)消息 ··························.130
4.3 生產(chǎn)消息 ··································.134
4.3.1 生產(chǎn)者SDK 的3 種使用方式 ································.135
4.3.2 采用“同步”模式生產(chǎn)消息 ···.137
4.3.3 采用“異步”模式生產(chǎn)消息 ···.142
4.3.4 采用“最多發(fā)送一次”模式生產(chǎn)消息 ··························.148
4.4 消費(fèi)消息 ··································.152
4.4.1 采用pull 模式消費(fèi)消息 ········.153
4.4.2 采用push 模式消費(fèi)消息 ·······.171
4.4.3 采用pop 模式消費(fèi)消息 ········.183
4.5 采用“請(qǐng)求/應(yīng)答”消息實(shí)現(xiàn)同步調(diào)用 ········································.197
4.5.1 “請(qǐng)求/應(yīng)答”消息的架構(gòu) ····.197
4.5.2 分析“請(qǐng)求/應(yīng)答”消息的過(guò)程 ································.198
4.6 【實(shí)例】生產(chǎn)者發(fā)送消息，消費(fèi)者順序地消費(fèi)消息 ·························.212
4.6.1 驗(yàn)證“普通順序消息” ········.212
4.6.2 驗(yàn)證“嚴(yán)格順序消息” ········.217
第5 章 存儲(chǔ)消息 ······························.219
5.1 認(rèn)識(shí)存儲(chǔ)引擎 ····························.219
5.1.1 什么是存儲(chǔ)引擎 ·················.219
5.1.2 存儲(chǔ)引擎的架構(gòu) ·················.221
5.2 認(rèn)識(shí)存儲(chǔ)模型 ····························.222
5.2.1 消息模型 ··························.222
5.2.2 文件模型 ··························.229
5.2.3 【實(shí)例】利用源碼遠(yuǎn)程調(diào)試存儲(chǔ)模型 ································.236
5.3 啟動(dòng)存儲(chǔ)引擎 ····························.238
5.3.1 初始化Broker Server 和存儲(chǔ)引擎 ································.238
5.3.2 啟動(dòng)Broker Server 和存儲(chǔ)引擎 ································.247
5.3.3 【實(shí)例】動(dòng)態(tài)修改存儲(chǔ)引擎的配置參數(shù) ··························.251
5.4 使用存儲(chǔ)引擎處理“儲(chǔ)存消息”的請(qǐng)求 ········································.253
5.4.1 接收并處理生產(chǎn)消息的請(qǐng)求 ································.254
5.4.2 存儲(chǔ)消息 ··························.257
5.4.3 【實(shí)例】利用存儲(chǔ)引擎實(shí)現(xiàn)批量地存儲(chǔ)消息 ·······················.262
5.5 對(duì)比存儲(chǔ)單條消息和批量消息的性能 ········································.263

第6 章 治理消息 ······························.268
6.1 如何治理消息 ····························.268
6.1.1 治理消息的目標(biāo) ·················.268
6.1.2 使用消息度量提供治理消息的依據(jù) ································.276
6.1.3 使用消息管控實(shí)現(xiàn)治理消息的落地 ································.280
6.2 認(rèn)識(shí)命令控制臺(tái)和UI 控制臺(tái) ········.285
6.2.1 什么是命令控制臺(tái)和UI控制臺(tái) ·····························.285
6.2.2 啟動(dòng)命令控制臺(tái)和UI控制臺(tái) ·····························.289
6.2.3 使用對(duì)象池管理RocketMQDashboard 中通信渠道客戶端的核心類 ·····························.292
6.3 使用命令控制臺(tái)治理消息 ·············.298
6.3.1 執(zhí)行治理消息的命令 ···········.299
6.3.2 【實(shí)例】使用命令控制臺(tái)，完成
RocketMQ 集群的擴(kuò)容 ·········.322
6.3.3 【實(shí)例】使用命令控制臺(tái)，完成
RocketMQ 集群的縮容 ·········.325
6.3.4 【實(shí)例】使用命令控制臺(tái)，動(dòng)態(tài)增加Topic 的讀/寫(xiě)消息隊(duì)列的數(shù)量 ·················.332
6.4 使用UI 控制臺(tái)治理消息 ··············.334
6.4.1 使用UI 控制臺(tái)治理消息的原理 ································.335
6.4.2 【實(shí)例】使用UI 控制臺(tái)手動(dòng)地禁用消費(fèi)者組 ····················.341
6.4.3 【實(shí)例