This comprehensive guide walks you through RabbitMQ's core features, typical use cases, step‑by‑step local installation, cluster architecture, HA configuration, admin console, monitoring scripts, capacity planning, and automation, enabling reliable, high‑performance messaging in production environments.
This article explains Kafka’s high‑performance distributed streaming architecture, key components such as topics, partitions, producers, consumers, brokers, offsets, and ZooKeeper, and provides step‑by‑step workflows for producers and consumers along with performance‑testing tips and Maven setup.
This article examines the severe row‑lock competition in MySQL during hot‑SKU inventory positioning, analyzes its causes and risks, and presents a comprehensive set of mitigation strategies—including DB account isolation, flow‑control, request merging, and message‑queue optimizations—validated by extensive performance testing and successful rollout across multiple clusters.
This article deeply explores Apache RocketMQ's retry mechanisms, detailing producer and consumer retry strategies, flow control handling, dead‑letter queue management, advanced configurations, best practices, and comparisons with Kafka and RabbitMQ, providing practical code examples and monitoring recommendations for building highly reliable distributed systems.
This article examines frequent RocketMQ problems such as duplicate sending, flow‑control throttling, message retries, duplicate consumption, backlog, and loss, and provides practical configuration tweaks, scaling strategies, batch sending, idempotent handling, and retry mechanisms to ensure reliable message delivery.
This article systematically breaks down RocketMQ's core mechanisms—covering message roles, disk storage, push/pull delivery, expiration handling, retry queues, and cluster failover—so developers can understand every stage a message undergoes from creation to cleanup and ensure reliable, high‑performance messaging.
This article presents a comprehensive set of RocketMQ usage guidelines—including topic and tag conventions, producer and consumer group naming, key handling, logging, retry mechanisms, and cluster deployment recommendations—to help engineers build stable, high‑performance, and observable messaging systems in production environments.
This article walks you through installing and using the RocketMQ Dashboard to monitor topics, brokers, producers, consumers, and message details, explains common pitfalls such as client‑ID conflicts in Docker, and demonstrates how to troubleshoot consumption issues, TPS metrics, and dead‑letter handling.
Idempotency ensures that repeated service calls or user actions produce the same effect without unintended side effects, a critical concern in distributed and microservice architectures; this article explains its principles, SQL examples, HTTP semantics, token strategies, lock handling, and message‑queue solutions.
This article explains the composition of RocketMQ's SendResult object returned after a successful synchronous send, detailing each field such as sendStatus, msgId, offsetMsgId, messageQueue, and queueOffset, and provides practical examples and a full field‑by‑field breakdown for Java developers.
This article introduces the high‑performance Disruptor library, explains its core concepts such as Ring Buffer, Sequencer and Wait Strategies, and provides a step‑by‑step Java demo showing how to build a producer‑consumer queue without external brokers.
This tutorial walks through integrating Alibaba's RocketMQ into a Spring Boot application, covering Maven dependencies, producer and consumer configurations, and detailed examples of synchronous, asynchronous, one‑way, delayed, ordered, transactional, request‑response, batch, and pull messaging APIs, along with best‑practice recommendations.
The article explains how message backlog arises when producers outpace consumers in systems like Kafka or RocketMQ, outlines primary causes such as unexpected production spikes, broker failures, and consumer bottlenecks, and provides step‑by‑step mitigation strategies including capacity scaling, temporary queues, and optimization techniques for producers, brokers, and consumers.
This article explains RocketMQ’s architecture, the roles of NameServer, Broker, Producer, Consumer, and how each component ensures reliable message delivery—covering synchronous, asynchronous, and one‑way sending, storage mechanisms, consumer retries, dead‑letter queues, installation steps, and Java client integration with code examples.
This article revisits RocketMQ's Name Server, detailing its core components, how it registers brokers, maintains routing information, handles client queries, and uses heartbeat mechanisms to ensure high availability and dynamic scaling in distributed messaging systems.
The article explains why RPC should be used when callers need immediate results, while MQ is preferable for fire‑and‑forget notifications, illustrating the trade‑offs with code examples, common pitfalls of misusing each method, and practical steps to achieve physical and logical decoupling in backend systems.
This article explains the three message delivery semantics, the common causes of duplicate messages in queue systems, and presents concrete producer‑side, broker‑side, and consumer‑side deduplication techniques for Kafka and Pulsar, including code samples and best‑practice recommendations.
This article shares practical Kafka production insights, covering architecture overview, producer throughput tuning, message loss prevention, broker and consumer configurations, duplicate consumption avoidance, backlog mitigation, ordering guarantees, and the mechanics of consumer group rebalancing, helping engineers build stable, high‑performance streaming pipelines.
RocketMQ, an Apache‑licensed distributed message queue from Alibaba, offers low latency, high reliability, and high throughput through features like distributed architecture, synchronous disk flushing, master‑slave replication, and flexible messaging models, and it compares favorably against Kafka, RabbitMQ, and ActiveMQ in various scenarios.
This tutorial walks through downloading, extracting, configuring, starting, creating topics, producing and consuming messages, and finally stopping Apache Kafka 3.8.1 on a Linux system, including all necessary command‑line instructions.
This article examines four techniques for automatically closing overdue orders—database polling, Redis key‑expiration listeners, Redis sorted‑set delay queues, and message‑queue delayed messages—detailing their implementations, advantages, drawbacks, and practical recommendations for reliable backend systems.
This article explains synchronous versus asynchronous processing through a parcel‑delivery example, outlines core async concepts, presents common async techniques such as message queues, event‑driven design and non‑blocking I/O, and demonstrates practical implementations with Spring Cloud Gateway, Netty, ELK‑Kafka pipelines, and CompletableFuture batch processing.
This article explains why orders that remain unpaid for 30 minutes should be automatically cancelled and compares five technical approaches—database polling, JDK Timer, message‑queue delayed queues, distributed schedulers like Quartz, and Redis expiration listeners—detailing their implementation steps, code samples, pros, cons, and suitable scenarios.
The article examines how e‑commerce platforms implement order auto‑closure using delayed tasks, compares methods such as message‑queue delayed delivery, Redisson delay queue, Redis expiration listening, RabbitMQ dead‑letter queues and time wheels, and recommends reliable approaches while warning against unsafe practices.
This article explains how RocketMQ implements long‑polling for message consumption, detailing the pull‑based model, the broker and consumer timeout settings, the internal suspension of pull requests, and the processing loop that resumes suspended requests to improve efficiency.
This article explains why RabbitMQ is often selected as a message middleware, covering its reliability features, flexibility in routing, performance advantages, ecosystem support, and a concise comparison with Kafka and RocketMQ to help developers make an informed choice.
This article explains the motivation, design choices, and implementation details of a custom distributed job scheduling framework, covering its architecture, load‑balancing strategy, message‑queue handling, persistence mechanisms, and key code snippets, while comparing it to existing solutions like Quartz, XXL‑Job, and PowerJob.
This article introduces the high‑performance LMAX Disruptor library, explains its core concepts such as Ring Buffer, Sequence, Sequencer, and Wait Strategy, and provides a step‑by‑step Java demo with complete code to build a producer‑consumer message queue.
This article examines the three major reliability challenges of message queues—loss, duplicate consumption, and backlog—and provides detailed RocketMQ‑specific strategies, including producer acknowledgment, broker replication, idempotent consumer design, monitoring, scaling, and parameter tuning to ensure high‑availability distributed systems.
This article explains RocketMQ's transactional message mechanism, covering half‑message storage, three transaction states, status‑check procedures, key APIs, storage reliability, and the two‑phase commit process that guarantees eventual consistency in distributed systems.
This article compares several ways to implement order‑closing delayed tasks—message‑queue delayed delivery, Redisson DelayQueue, Redis expiration listening, RabbitMQ dead‑letter queues, and time wheels—explaining their mechanisms, drawbacks, and recommending the most reliable solutions for production systems.
This article explains TDMQ RocketMQ's distributed rate‑limiting mechanism, covering conversion rules, fast‑fail behavior, token‑based implementation, counting periods, client best practices, elastic TPS options, code examples for different SDK versions, monitoring tips, and answers to common throttling questions.
Using a local message table, developers can break down distributed transactions into local database operations and asynchronous MQ messages, ensuring eventual consistency, simplifying implementation, and handling retries, while balancing advantages like simplicity and compatibility against drawbacks such as added maintenance and potential queue dependencies.
This article explains the concepts of RabbitMQ dead‑letter exchanges and queues, outlines why messages become dead letters, and provides complete Java code examples for configuring exchanges, publishing messages with TTL, and consuming both normal and dead‑letter queues.
The article explains how RocketMQ implements distributed transaction messages using a two‑phase commit model to ensure data consistency across micro‑service subsystems, detailing the workflow from half‑message production, broker handling, local transaction execution, commit/rollback decisions, and periodic status checks.
This article explains why AIGC services need queueing systems and rate‑limiting, describes the user‑facing behaviors of both mechanisms, outlines design goals, compares queue and limiter implementations, and provides practical guidance on selecting middleware, monitoring, and integrating them into a production workflow.
This article explains common causes of duplicate message consumption in high‑traffic systems and presents a three‑layer defense—producer idempotence, broker de‑duplication, and consumer idempotent design—plus monitoring and reconciliation strategies to achieve reliable exactly‑once processing.
This article explains the fundamentals of distributed transactions, covering ACID properties, the CAP theorem, two‑phase commit, TCC compensation, and a message‑queue based eventual consistency approach, while highlighting their advantages, drawbacks, and practical application scenarios.
RabbitMQ uses exchanges to route messages from producers to queues, and this guide details the four main exchange types—Direct, Topic, Fanout, and Headers—explaining their routing rules, suitable scenarios, and practical examples to help developers choose the right pattern for reliable messaging.
This article explains various approaches to delayed task handling—such as database polling, JDK DelayQueue, Redis expiration listeners, Redisson delay queues, RocketMQ delayed messages, and RabbitMQ dead‑letter queues—evaluating their advantages, drawbacks, and best‑practice recommendations for reliable order‑expiration workflows.
This article explains how RocketMQ, a Chinese‑origin message queue, simplifies Kafka’s architecture while adding powerful features such as tag‑based filtering, transactional messaging, delayed and dead‑letter queues, and a unified commit‑log storage model, making delayed processing and high‑throughput scenarios easier to implement.
This article provides a comprehensive overview of RabbitMQ, an open-source AMQP-based message broker, detailing its core components—producers, exchanges, queues, consumers, and broker—along with auxiliary elements like bindings, connections, channels, virtual hosts, and key architectural features such as decoupling, flexible routing, reliability, and scalability.
This article explains why high‑throughput producers and consumers can saturate CPU, memory, network and disk I/O in TDMQ Pulsar clusters, describes the built‑in cluster‑level distributed and topic‑partition rate‑limiting mechanisms, and provides practical guidance for configuration, monitoring, and troubleshooting.
This article explains why messages can be lost in RabbitMQ at the producer, broker, or consumer stages and provides concrete techniques—including confirm mode, transaction handling, persistence settings, manual acknowledgments, and retry mechanisms with dead‑letter queues—to ensure reliable delivery.
This article explains how to combine PHP web applications with modern cloud-native AI services—via REST APIs, SDKs, and message queues—to build efficient real-time decision systems, covering integration methods, sample code, use-case implementations such as recommendation, dynamic pricing, fraud detection, and performance optimization best practices.
The article explains why using Redis expiration or RabbitMQ dead‑letter queues for delayed order‑cancellation tasks is unreliable, compares several approaches such as message‑queue delayed delivery, Redisson delay queues, and time wheels, and recommends robust solutions like RocketMQ or Pulsar for accurate timing.
This article compares Kafka and RabbitMQ across design philosophy, performance, data model, delivery semantics, ecosystem, and typical use cases, helping readers choose the right messaging middleware for high‑throughput or reliable delivery scenarios.
This article explains CKafka's cluster‑level and topic‑level throttling mechanisms, the soft‑limit token‑bucket algorithm, practical configuration tips, monitoring methods, and common troubleshooting scenarios to help users maintain stable and high‑performance message‑queue services.
This article provides a comprehensive overview of Apache Kafka, covering its core concepts, architecture, common use cases, installation steps, and essential command-line operations for managing topics and brokers in production environments and ensuring reliability.
This article explores industry‑proven techniques for handling massive flash‑sale traffic, covering pressure‑distribution, Redis + MQ combos, Lua‑based stock deduction, RocketMQ transactional messages, and Alibaba Cloud's Inventory Hint to ensure consistency and performance under extreme concurrency.
RocketMQ’s message tracing feature records each message’s full lifecycle—including producer, broker, and consumer details such as timestamps, latency, and success flags—by enabling traceTopicEnable, creating an internal RMQ_SYS_TRACE_TOPIC, and allowing custom trace topics for fast diagnostics, end‑to‑end tracking, monitoring, and audit compliance.
This article explores eight common scenarios for using message queues in backend development, covering asynchronous processing, service decoupling, traffic shaping, delayed tasks, log aggregation, distributed transactions, remote calls, and broadcast notifications, each illustrated with Java, RocketMQ, and Kafka code examples.
Message queues can deliver duplicates under at‑least‑once semantics, so to protect idempotent business logic such as orders and payments you should combine producer‑side idempotence (e.g., Kafka’s enable.idempotence), broker‑side deduplication (e.g., Pulsar), and a consumer‑side guard using unique IDs stored in a database or Redis.
This article explores eight practical scenarios for using message queues—such as asynchronous processing, service decoupling, traffic shaping, delayed tasks, log collection, distributed transactions, remote calls, and broadcast notifications—providing code examples with RabbitMQ, RocketMQ, and Kafka to illustrate each pattern.
This guide explains the key port configurations of Apache RocketMQ brokers, details essential mqadmin commands for managing topics, checking status, and monitoring consumer progress, and provides practical examples to help administrators efficiently operate and troubleshoot RocketMQ clusters.
This article presents fifteen practical Redis usage scenarios—including caching, distributed locks, leaderboards, counters, message queues, session management, bitmap sign‑ins, geolocation, rate limiting, pub/sub, delayed tasks, global IDs, recommendation models, user follow relationships, and timeline feeds—each illustrated with concise code snippets.
This article examines common industry approaches for handling massive flash‑sale traffic, detailing pressure‑distribution sharding, Redis + MQ integration, the Inventory Hint optimization, and provides concrete Lua script examples and transactional‑message workflows for reliable stock deduction.
This comprehensive guide covers RabbitMQ fundamentals, installation on Windows, Linux, and Docker, configuration for durability and monitoring, Java integration examples, high‑availability architectures, clustering, and practical troubleshooting tips for building reliable distributed systems.
This article explains Kafka's push/pull consumption models, the impact of enable.auto.commit and auto.commit.interval.ms on offset handling, and presents practical configurations and code patterns plus MySQL and Redis based deduplication techniques to prevent both duplicate and missing message processing.
This article explores practical HTTP retry solutions for offline store applications, covering a basic loop retry, the built‑in retry mechanism of Apache HttpClient with custom handlers, and an asynchronous retry approach using message queues to achieve higher reliability and eventual consistency.
This article provides an in‑depth comparison of Aeron Queue and Chronicle Queue, examining their architectures, ideal use cases, performance characteristics, scalability, and persistence features to help engineers decide which low‑latency messaging system best fits distributed or single‑process applications.
This article examines the rise of microservice architecture and compares major communication mechanisms—RESTful APIs, gRPC, and message queues—guiding developers on selecting the most suitable approach based on business requirements, system scale, and team expertise.
This guide explains Apache RocketMQ’s ordinary message concept, its full lifecycle, how to create topics, Java code for sending and receiving messages, key configuration tips, and real‑world scenarios such as asynchronous decoupling and traffic‑shaping for micro‑service architectures.
The article explains why distributed transactions are inevitable in microservice architectures, outlines the challenges of data consistency, fault handling, and performance, and presents practical solutions such as message‑queue eventual consistency, two‑phase commit, Saga patterns, and tooling like Spring Cloud, Atomikos, and Narayana.
In RocketMQ, adding consumers speeds consumption only when they are fewer than MessageQueues, while pull delays arise from ProcessQueue thresholds or ordered‑lock timeouts; slow processing often stems from heavy business logic or external calls, and load can be balanced using average, round‑robin, custom, machine‑room, nearby‑room, or consistent‑hash allocation strategies.
Message queues act as asynchronous communication bridges in distributed systems, and this article examines three leading solutions—Kafka, RabbitMQ, and RocketMQ—detailing their performance, scalability, reliability, strengths, drawbacks, and suitable use‑cases to guide developers in selecting the right technology.
This guide explains how to install the workerman/rabbitmq package, set up producer and consumer scripts for both Workerman and PHP‑FPM environments, and run asynchronous RabbitMQ messaging using detailed PHP code examples and configuration options.
This article explores eight practical use cases for message queues—including asynchronous processing, service decoupling, traffic shaping, delayed tasks, log collection, distributed transactions, remote calls, and broadcast notifications—providing code examples and architectural guidance for building robust backend systems.
This article explains eight typical scenarios for using message queues—including asynchronous processing, service decoupling, traffic shaping, delayed tasks, log collection, distributed transactions, remote invocation, and broadcast notifications—providing clear explanations and Java code snippets for each case.
This article explains common data‑migration strategies such as hash‑modulo, time‑range and ID‑range sharding, and compares practical migration solutions including downtime migration, dual‑write, and an MQ + Redis approach, with detailed workflow diagrams and implementation tips.
This article explains the architectural changes introduced in RocketMQ 5.0, including the new stateless Proxy layer, the POP consumption model, message‑level load balancing, and the Controller mode for automatic master‑slave failover, providing detailed diagrams and resource links.
This article introduces the motivation, architecture, technology choices, and key implementation details of a lightweight, highly extensible distributed job scheduling framework built on gRPC, Protobuf, a custom name‑server, and a bespoke message‑queue, addressing limitations of existing solutions like Quartz, XXL‑Job, and PowerJob.
This article explains RocketMQ’s fundamental architecture, detailing the definitions, roles, and interactions of topics, message queues, messages, producers, consumers, consumer groups, and subscription relationships, and highlights how these components work together to achieve high performance, availability, and scalability.
This article explains what a feed stream is, why it exists, how it evolved from RSS to modern social feeds, classifies different feed models, outlines the challenges of real‑time delivery, and provides a detailed backend architecture, data structures, storage design, pagination strategy, and core publish‑read workflows to help engineers build reliable, high‑performance feed systems.
This article explains how the traffic team replaced a costly MQ system with Redis Stream, covering its concepts, design, implementation details such as load balancing and cross‑region deployment, monitoring metrics, performance benchmarks, practical lessons learned, and the scenarios where Redis Stream is most suitable.
This article details the design, architecture, and evolution of a self‑developed customer instant‑messaging system, covering its user‑centred philosophy, layered backend structure, technology choices such as WebSocket and Spring WebFlux, and how it solved challenges in gateway design, session storage, message ACK, and queue management to achieve high availability, security, and future‑ready scalability.
This article examines the root causes of message queue disorder in distributed systems, illustrates real‑world impacts such as data loss during migration, and presents concrete mitigation strategies including ordered messaging, pre‑processing checks, state‑machine handling, and monitoring to improve system reliability.
This article examines the causes of message queue disorder in distributed systems and presents practical solutions such as ordered messaging, pre‑consumption checks, state machines, and monitoring to improve system stability and data consistency.
This article explains Apache RocketMQ's core components—including producers, topics, queues, and consumer groups—covers synchronous RPC versus asynchronous messaging, compares point‑to‑point and publish‑subscribe transmission models, and highlights their suitable scenarios and trade‑offs.
This article provides a comprehensive overview of Kafka, covering its overall structure, key components such as brokers, producers, consumers, topics, partitions, replicas, leader‑follower mechanics, logical and physical storage models, producer and consumer workflows, configuration parameters, partition assignment strategies, rebalancing, log retention and compaction, indexing, zero‑copy transmission, and the reliability concepts that ensure data durability.
The article explains how Kafka’s use of sendfile zero‑copy gives it higher throughput than RocketMQ, which relies on mmap, and discusses the trade‑offs between performance and feature richness when choosing between the two message‑queue systems.
This comprehensive guide introduces RocketMQ's architecture, compares it with RabbitMQ and Kafka, outlines typical use cases, explains key concepts such as producers, brokers, consumers, topics, tags, and offsets, and provides complete Java code examples for building producers and consumers.
This article details how a rapidly growing on‑demand logistics service designed and implemented a high‑performance, extensible message fusion platform that handles massive, diverse user messages through distributed processing, visual configuration, and self‑healing mechanisms, enabling real‑time, personalized communication at scale.
This article explains why syncing Redis with MySQL is essential for performance and consistency, and details three implementation methods—database triggers, application-level double writes, and message queues—providing code examples, practical tips, and key considerations for reliable data synchronization.
The article surveys feed‑stream systems—from their RSS roots to modern social‑media timelines—explaining classifications, core terminology, and a high‑performance architecture that uses Redis ZSET inboxes, write‑ and read‑diffusion, soft‑delete consistency, and last‑id pagination to handle massive real‑time writes, big‑V fan‑out, and efficient publishing and reading.
This article explains the motivation, design choices, architecture, and core technical details of implementing the AMQP protocol on top of RocketMQ, including model mapping, proxy layer, LMQ queues, message flow, binary protocol handling, feature comparison, performance tuning, and future plans.
The article compares Kafka and RocketMQ, explaining how Kafka’s use of sendfile zero‑copy reduces system calls and data copies, while RocketMQ relies on mmap, leading to lower throughput but richer features, and offers guidance on choosing between them based on scenario.
Ten practical techniques—early validation, batch queries, asynchronous processing, parallel execution, caching, connection pooling, response compression, message‑queue decoupling, security best practices, and reusable design patterns—collectively reduce latency, boost throughput, and improve scalability of high‑concurrency interfaces.
This tutorial walks you through installing Erlang, downloading the RabbitMQ server, starting it in detached mode, verifying its status, and troubleshooting common TCP‑listener errors on CentOS systems, providing all necessary commands and configuration details.
This article compares Kafka and RabbitMQ across design philosophy, performance, data models, delivery semantics, ecosystem, and typical use cases, helping developers choose the right messaging middleware for high‑throughput streaming or reliable task queues.
This article thoroughly examines Apache Kafka’s architecture, covering its macro components, ack strategies, replication mechanisms, high‑watermark handling, leader election, and performance optimizations such as batch sending, compression, PageCache, zero‑copy, mmap and sendfile, while also explaining common pitfalls like data loss and log corruption.
This article introduces tldb's distributed lock mechanism, explains lock, trylock, and unlock methods, and provides step‑by‑step Go and Java client examples—including code snippets—for acquiring and releasing locks in a multi‑language environment.
Xiaohongshu replaced its RocketMQ‑based online messaging platform with Apache Pulsar, achieving up to 48% total cost reduction, 43% higher CPU utilization, 30% resource savings, and a latency drop from 20.2 ms to 5.7 ms through cloud‑native, elastic scaling and a phased migration strategy.
This article details Tencent Cloud engineers' technical solutions for large‑scale Apache Pulsar deployments, covering multi‑network access challenges, a routing‑addressing redesign, product deployment models, a four‑step cluster migration process with subscription‑progress compensation, and high‑availability best practices such as rack‑aware and cross‑AZ replica distribution.
This article provides practical Python code examples for various messaging and serialization tools—including Celery, RQ, Huey, ZeroMQ, kafka‑python, Pika, stomp.py, nats‑py, gRPC, Thrift, Protobuf, Avro, msgpack, and Flatbuffers—demonstrating how to set up producers, consumers, and services for asynchronous processing and data exchange.
The talk outlines ApsaraMQ’s journey to a fully serverless, cloud‑native messaging platform, detailing its compute‑storage separation, stateless proxy functions, RDMA‑enhanced performance, elastic scaling mechanisms, and how its event‑driven architecture empowers real‑time AI applications through seamless data vectorization.
This article provides a comprehensive overview of RocketMQ, covering its architecture, key features such as high reliability, low latency and high throughput, comparisons with Kafka, RabbitMQ and ActiveMQ, and detailed mechanisms that ensure message durability, performance, and ordered consumption.
This article introduces RabbitMQ, explains its core features and messaging model, discusses why to use it for asynchronous, decoupled, and throttled processing, and provides step‑by‑step installation instructions for macOS, Windows, and CentOS along with Java code examples for configuring and using delayed messages via the rabbitmq_delayed_message_exchange plugin.
This guide walks you through installing Erlang, downloading and building RabbitMQ 3.0.4 from source on a Linux system, verifying the installations, starting the server in detached mode, checking its status, and troubleshooting common port‑conflict issues on CentOS 6.
This guide walks you through installing Erlang, downloading and extracting RabbitMQ 3.0.4, starting the server in detached mode, verifying its status, and troubleshooting common port‑conflict errors on CentOS 6, with complete command‑line examples.
