0 views collected around this technical thread.
This article breaks down RocketMQ’s storage architecture, explaining how its commitlog, consumequeue, and index files work together to ensure reliable persistence, quick offset-based lookups, and efficient message consumption in a publish‑subscribe model.
This article explains RocketMQ's broker storage architecture, detailing the roles of CommitLog, ConsumeQueue, and IndexFile, and describes how messages are formatted, indexed, and written to disk using memory‑mapped files to achieve high throughput and reliability.
This article explains the core storage design of RocketMQ, covering the CommitLog, ConsumeQueue, and Index files, their organization, sequential write strategy, memory‑mapped I/O, and flexible flushing policies that together provide high‑throughput, low‑latency messaging for backend systems.