This article breaks down common interview questions about message queue middleware, compares popular options like RabbitMQ, RocketMQ, and Kafka, and explains why introducing a message broker improves system decoupling, enables asynchronous processing, and helps handle traffic spikes efficiently.
This article explains how RocketMQ’s transactional message feature enables distributed transaction final consistency by using half messages, message check‑back, and defined transaction states, and provides complete Java code samples for producers, listeners, and consumer idempotency handling.
This article provides a comprehensive overview of RocketMQ, covering its origins and evolution, core architecture components, message domain model, essential features such as ordered delivery and deduplication, and typical use cases like traffic shaping, asynchronous decoupling, and distributed transaction messaging.
At Didi, the team replaced a chaotic mix of Kafka, Redis, and other queues with a custom, RocketMQ‑based service, using dual‑write and dual‑read migration, extensive performance testing, custom failover, batch extensions, and operational tweaks to achieve stable high‑throughput, low‑latency messaging at massive scale.
This article recounts Didi's journey from a chaotic mix of Kafka, RocketMQ, Redis, and other queues to a unified, high‑performance messaging platform built on Apache RocketMQ, covering the reasons for abandoning Kafka, the architecture evolution, migration strategies, performance benchmarks, and operational enhancements.
This article introduces Apache RocketMQ by covering its origin, core concepts such as topics, producers and consumers, storage architecture with CommitLog and ConsumeQueue, deployment components like brokers and name servers, and practical best‑practice guidance for handling duplicates, ordering, and message replay.
Distributed transactions ensure atomicity across services, and RocketMQ provides a half-message mechanism with a two-phase commit and a rollback check that lets producers and consumers coordinate transaction steps reliably even when confirmations are delayed.
This article reviews the evolution of Alibaba's Aliware message engine, analyzes the latency and availability challenges faced during Double‑11, and describes the low‑latency optimizations, capacity‑guarantee strategies, and multi‑replica high‑availability architecture implemented in RocketMQ to sustain trillion‑level message flows.
This article dissects RocketMQ’s Remoting communication module, covering its architecture, class hierarchy, custom protocol design, message encoding/decoding, synchronous, asynchronous and one‑way communication modes, and the detailed client‑server interaction flow including timeout handling and callback execution.
This article evaluates the server‑side performance of three popular message middleware platforms—Kafka, RabbitMQ, and RocketMQ—by measuring throughput and latency when sending small 124‑byte messages, revealing that Kafka leads, followed by RocketMQ and then RabbitMQ.
This article compares the architectures of Kafka and RocketMQ, examines their availability and reliability mechanisms, evaluates their strengths and weaknesses, and proposes hybrid designs and simplified MQ architectures for building highly available and reliable messaging systems.
This article shares a seasoned developer’s perspective on selecting a message‑queue middleware, outlining typical adoption stages, three key evaluation criteria—coder expertise, current and future requirements, and community/ecosystem health—and offering candid advice on avoiding common pitfalls.
This article explains the internal workflow of RocketMQ transactional messages, covering how producers send half messages, how brokers process commit or rollback requests, the storage mechanisms for transaction state, the periodic transaction check logic, and the differences between file‑system and database implementations.
This tutorial provides a step‑by‑step walkthrough for setting up Apache RocketMQ 4.2 on a 64‑bit Linux system, covering environment prerequisites, downloading source, building binaries, starting NameServer and Broker, sending and receiving messages, and shutting down the services.
Apache RocketMQ, Alibaba's high‑performance distributed messaging middleware, has officially graduated to an Apache Top‑Level Project, highlighting its robust features, broad ecosystem adoption across e‑commerce, IoT, finance and big‑data, and Alibaba's strong commitment to open‑source leadership.
This article details a step‑by‑step transformation of an internet finance platform's online release process, covering application architecture, public component selection, smooth deployment techniques using Dubbo weight adjustment, RocketMQ control, LTS task isolation, verification methods, and a comprehensive gray‑release strategy with practical pitfalls and future improvements.
This article examines the architectures of Kafka and RocketMQ, analyzes their availability and reliability mechanisms, evaluates their strengths and weaknesses, and proposes a hybrid MQ design that combines the benefits of both systems while simplifying dependencies and improving fault tolerance.
This article examines the architectures of Kafka and RocketMQ, analyzes their availability and reliability mechanisms, compares their strengths and weaknesses, and proposes hybrid designs and simplified MQ solutions for building robust message‑queue systems.
This guide walks through installing RocketMQ on a CentOS 6.5 VM, launching NameServer and Broker, provides sample Java consumer and producer code, and outlines best‑practice tips for idempotent consumption, batch processing, message filtering, performance tuning, and reliable message delivery.
RocketMQ is a distributed queue-based middleware offering strict message ordering, diverse pull modes, scalable subscribers, real-time subscription, and massive message accumulation, with detailed network deployment, storage mechanisms, key features, flushing strategies, query methods, server-side filtering, JVM memory utilization, and solutions for message backlog.
This article explains RocketMQ's core features—including ordered and duplicate message handling, transaction messages, producer and consumer mechanisms, storage architecture, indexing, subscription models, and practical best‑practice recommendations—while providing code examples and design insights for building scalable, high‑throughput distributed messaging systems.
This article reviews the evolution of Alibaba's middleware message engine, analyzes the low‑latency and high‑availability challenges faced during Double‑11, and details the optimization techniques, capacity‑guarantee strategies, and HA architecture that enable RocketMQ to handle massive traffic spikes with millisecond‑level latency.
This article recounts Alibaba's RocketMQ journey—from record‑breaking low‑latency performance during Double‑Eleven, through the challenges of open‑source donation, to its successful incubation at Apache and future plans for both community and commercial versions.
Alibaba’s recent donation of its high‑performance distributed messaging platform RocketMQ to the Apache Foundation marks a significant step for open‑source middleware, promising broader adoption, enhanced community collaboration, and new opportunities for developers building scalable, low‑latency systems across cloud and IoT environments.
This article provides a comprehensive overview of RocketMQ, covering its design for high‑throughput distributed messaging, solutions to ordering and duplicate‑message challenges, transaction messaging mechanisms, producer/consumer workflows, storage architecture, subscription models, additional features, and practical best‑practice recommendations.
