This article surveys common delayed‑message implementations—including external storage, RocksDB, Redis, and open‑source MQs like RocketMQ, Pulsar, and QMQ—detailing their architectures, advantages, disadvantages, and practical considerations for distributed asynchronous messaging systems.
This article surveys common delayed message implementations—including external storage, RocksDB, Redis, and open‑source MQs like RocketMQ, Pulsar, and QMQ—analyzing their architectures, advantages, drawbacks, and practical considerations for building reliable distributed asynchronous messaging systems.
This article surveys common delayed‑message solutions in distributed messaging, compares implementations based on external storage (MySQL, RocksDB, Redis) and built‑in MQ features (RocketMQ, Pulsar, QMQ), and analyzes their advantages, disadvantages, and design considerations.
The article analyzes real‑world network and disk I/O issues encountered in Qunar Message Queue (QMQ), explains root causes such as Netty OOM, file‑handle exhaustion, TCP timeout handling, and large‑traffic bursts, and presents practical mitigation strategies for backend systems.
This article introduces QMQ, Qunar's internal distributed message queue, covering its background, design motivations, core concepts, code examples for producing and consuming both real‑time and delayed messages, transactional messaging support, and the overall architecture of its metaserver, broker, and delay components.
