The article explains RocketMQ's two‑layer locking mechanism that guarantees ordered consumption by holding a queue‑level lock inside a while loop, clarifies why autoCommit only affects offset reporting, and shows how the client correctly processes multiple messages in a single thread.
This article explores the sequential consumption mechanisms of RocketMQ and its derivative DDMQ, detailing the underlying source‑code implementation, differences in producer ordering, broker handling, consumer locking, and how DDMQ simplifies ordering with a single‑node proxy, complete with code examples and diagrams.
This article deeply explores the sequential consumption mechanisms of RocketMQ and its derivative DDMQ, comparing their source‑code implementations, detailing producer ordering, broker locking, consumer locking, and the architectural differences that allow DDMQ to achieve ordered processing with only proxy‑side locks.
This article deeply explores the ordered consumption mechanisms of RocketMQ and its derivative DDMQ, explaining the implementation differences, source‑code details of sequential sending, broker locking, client‑side processing, and compares the two systems' approaches to guarantee message order.
This article explains RocketMQ's internal workflow for concurrent and ordered message consumption, covering thread‑pool configuration, pull‑message handling, request submission, execution steps, offset management, expired‑message cleanup, and answers common questions about batch retries and offset ordering.
This article explains how to guarantee that insert and update messages belonging to the same data entity are consumed in the correct order across separate Kafka topics by applying fine‑grained (or distributed) locks and a cache‑based detection mechanism, complete with Java/Spring code examples.
This article explains how to guarantee that insert messages are processed before update messages for the same data identifier across different Kafka topics by applying fine‑grained distributed locks and a caching strategy to detect and correct out‑of‑order consumption.
This guide explains how to construct a client library for Youzan's customized NSQ, covering workflow configuration, nsqd discovery via nsqlookupd, connection establishment, message publishing and consumption, ordered consumption, and the implementation of message tracing with concrete command syntax and response handling.
