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.
The article outlines practical solutions for RocketMQ message backlog—including scaling consumers, optimizing logic, batch consumption, producer throttling, broker tuning, monitoring, and emergency plans—then explains why Kafka delivers higher performance through sendfile zero‑copy, simple log storage, efficient memory use, and batch sending, and finally compares the two systems on reliability, retry, transactions, filtering, ordering, and suitable use cases.
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.
This article explains how RocketMQ guarantees message reliability across the production, storage, and consumption stages, covering synchronous, asynchronous, and transactional sending, disk persistence and replication strategies, consumption models (at-least-once, at-most-once, exactly-once), and handling consumer crashes without message loss.
This article walks through a zero‑to‑one charging‑station system built with Spring Cloud microservices, Vue front‑end, and a suite of enterprise features such as distributed locks, idempotency, multi‑level caching, and custom starters, providing concrete design documents and module breakdowns to help candidates showcase real project experience in interviews.
The article describes how a senior architect restructured a company's activity middle‑platform task system by standardizing message formats, introducing a rule engine (QLExpress) for configurable task completion conditions, and automating integration, while also interspersing promotional content for AI tools and community services.
This comprehensive guide compares five popular message queue systems—Kafka, Pulsar, RabbitMQ, RocketMQ, and NSQ—covering their architectures, core concepts, selection criteria, feature differences such as ordering, latency, durability, scaling, and operational considerations, to help engineers select the most suitable solution for their use cases.
This article explains how a legacy task system was redesigned by standardizing incoming messages, introducing a rule engine (QLExpress) for configurable completion conditions, and building a lightweight admin UI, reducing task‑integration time from a week to a few minutes.
This article explains how to enable cross‑server WebSocket communication in a distributed Spring application by using a message queue such as Redis or Kafka, detailing two architectural approaches, concrete code examples, configuration files, and a sample client page.
The paper presents a scalable, message‑queue‑driven reward system for Bilibili Live that unifies diverse reward types and distribution scenarios through standardized APIs, layered fast/slow queues, idempotent processing, multi‑stage retries, and comprehensive monitoring to ensure low latency, no over‑issuance, and reliable delivery.
This article explains how Redisson's DelayedQueue works internally, covering its data structures, the basic workflow for sending and receiving delayed messages, the initialization process, and the scheduling logic that moves expired items from the delay queue to the target queue.
Redis Streams offer a memory‑efficient, easy‑to‑use message queue that matches many Kafka features, making it a practical alternative for projects that cannot afford the overhead of deploying a full‑blown Kafka infrastructure.
This article outlines a comprehensive backend design that abstracts WebSocket into a reusable communication service, details project structure, business processes, reliability mechanisms for RabbitMQ, message classification, API design, and a unified message format to enable plug‑and‑play real‑time messaging across various Java applications.
This article explains how message queues decouple and buffer tasks such as payment processing, inventory updates, and notifications in high‑traffic online stores, improving reliability, scalability, and fault tolerance through asynchronous communication.
This article explains how RocketMQ's transaction messaging can break tight coupling between heterogeneous systems in fund companies, outlines topic/tag classification, compares distributed‑transaction solutions, and details the end‑to‑end workflow and consumption guarantees for financial use cases.
This article explains how to build high‑concurrency systems by decomposing monoliths into micro‑services, employing caching and message queues, separating databases, using read‑write splitting, and applying business‑level traffic shaping to achieve performance and availability.
This article explains RocketMQ's core components, including domain models, message transmission models, reliability mechanisms, the challenges of ordered messaging, practical usage scenarios, and the design and implementation of transactional messages in both open‑source and proprietary versions.
The article explains why adopting a message‑queue improves microservice decoupling and responsibility boundaries, then details the design of a pluggable Base‑MQ component—including @MQEventListener, MQEvent base class, configuration, and MQClient interface—followed by concrete implementations for RocketMQ, Kafka, Redis and RabbitMQ, an example event flow, and guidance for extending the framework.
The article thoroughly explains RocketMQ’s architecture—including stateless NameServers for routing, master‑slave Brokers with sequential CommitLog storage, stateless Producers and pull‑or‑push Consumers, message flow, indexing, and synchronous double‑write reliability—showing how these components deliver high‑throughput, scalable, fault‑tolerant messaging for distributed systems.
This article explains RocketMQ’s batch processing concepts, walks through the early batch model, the index‑build pipeline refactor, the BatchCQ and AutoBatch models, and presents benchmark results that show dramatic throughput gains and lower latency compared to Kafka.
RocketMQ stores messages in a sequential CommitLog while using a ConsumerQueue index for fast random access, and employs two looping threads—RebalanceService for load‑balancing queue assignments and PullMessageService for continuously pulling messages and dispatching them to user callbacks via a thread‑pooled consumer pipeline.
RabbitMQ is a lightweight, open‑source AMQP broker offering reliable, flexible routing, clustering, and multi‑protocol support; it can be installed via Homebrew, Windows installers, or source on CentOS, and, using the rabbitmq_delayed_message_exchange plugin, Spring Boot applications can configure custom exchanges, queues, and send delayed messages with an x‑delay header.
This article outlines the design of an internal WebSocket communication service that abstracts real‑time messaging, reduces code coupling, supports various business scenarios, ensures reliable delivery with RabbitMQ, defines unified APIs and message formats, and demonstrates a DDD‑based project structure for easy integration.
The article explains how RocketMQ’s reliance on mmap‑based zero‑copy leads to more data copies and system‑call overhead compared to Kafka’s sendfile approach, resulting in lower throughput, and discusses when to choose each message‑queue system based on functional needs and performance requirements.
This article explains the core concepts of distributed systems—including the CAP theorem, BASE theory, message‑queue challenges, Redis sentinel issues, sharding strategies, unique ID generation, and distributed transaction patterns—while offering practical guidance to prevent common pitfalls and improve reliability.
This guide explains why Kafka message backlogs occur, how to diagnose bugs, optimize consumer logic, and use temporary topics for emergency scaling, while emphasizing monitoring, alerts, and proper offset handling to keep your streaming system healthy.
To prevent duplicate processing when integrating message queues for rate limiting and decoupling, this article explains idempotency concepts, common pitfalls, and five practical solutions—including query checks, pessimistic and optimistic locking, deduplication tables, and non‑transactional approaches—complete with code snippets and diagrams.
This guide explains what RabbitMQ is, walks through installing Erlang and RabbitMQ on a Linux system, shows how to start and verify the server, and provides troubleshooting tips for common startup errors such as port conflicts.
This article examines the need for reliable HTTP retries in offline store applications, evaluates simple loop retries, explores Apache HttpClient's built‑in retry mechanism, and proposes a hybrid solution that combines customized HttpClient retry handling with asynchronous message‑queue retries to achieve high availability and eventual consistency.
This article describes the background, objectives, core design, reliability mechanisms, message classification, API design, and unified calling approach of a company‑wide WebSocket abstraction layer that replaces polling, supports asynchronous communication, and ensures reliable message delivery using RabbitMQ and confirm mechanisms.
The article analyzes the challenges of keeping MySQL and Redis data consistent under high concurrency, compares four write‑order strategies, explains why they can cause stale cache data, and presents recommended solutions such as Cache‑Aside, distributed locks, message queues, and Canal‑based binlog syncing.
This article provides an in‑depth overview of Apache Kafka, covering its use cases, comparison with other message queues, versioning, performance mechanisms, core concepts such as topics, partitions, offsets, consumer groups, rebalancing, replication, leader election, idempotence, transactions, compression, interceptors, request handling, and practical configuration tips for reliable streaming applications.
This article explains how RocketMQ achieves high throughput by using sequential disk writes, OS page caching, asynchronous flushing, and zero‑copy techniques, detailing each mechanism and providing code examples. It also discusses the impact on disk seek time and data durability.
This article analyzes the root causes of message loss and duplication in modern message queues, explains how synchronous and asynchronous sending affect reliability, compares storage strategies like sync‑flush and broker clustering, and offers concrete idempotent handling techniques using database constraints and Redis.
This article explains why duplicate message consumption occurs in Kafka, outlines the underlying confirmation and consumer failure issues, and presents idempotent design strategies such as deduplication tables and code examples to ensure reliable processing.
This guide walks backend developers through twenty real‑world Redis use cases—from basic caching, lotteries, and like/collect features to ranking, PV/UV counting, Bloom filters, sign‑in, geo‑search, rate limiting, ID generation, distributed locks, messaging, session sharing, and more—providing Spring Boot code samples, limitations, and best‑practice advice.
This article examines the trade‑offs of sending messages before, during, or after database persistence in order‑creation workflows, explores transaction‑message patterns, half‑message checks, and message‑table strategies, and offers practical guidance for building reliable backend messaging systems.
This article explores eleven practical methods for implementing delayed tasks in Java, covering native APIs like DelayQueue and Timer, advanced executors such as ScheduledThreadPoolExecutor, and popular messaging solutions including RocketMQ, RabbitMQ, Redis, Redisson, Netty, Hutool, and Quartz, with code demos and implementation details.
This article examines how the Tencent Cloud TDMQ Pulsar service was selected and integrated to handle the huge, bursty messaging traffic of the mobile game Honor of Kings, detailing its architecture, elastic scaling, pub/sub features, real‑time transaction support, and user feedback.
This article explores seven classic message‑queue use cases—from asynchronous decoupling and traffic‑shaping to delayed tasks, broadcast consumption, distributed transactions, and using Kafka as a data hub—illustrated with real‑world examples and code snippets.
This article shares seven practical scenarios—such as asynchronous processing, traffic smoothing, message bus, delayed tasks, broadcast consumption, distributed transactions, and data hub integration—where message queues like RocketMQ, Kafka, ActiveMQ, and RabbitMQ help solve high‑concurrency challenges in modern backend systems.
This guide walks through preparing three CentOS 7 nodes, installing Erlang and RabbitMQ, configuring users and permissions, setting environment variables, enabling the management plugin, synchronizing erlang.cookie, joining nodes in RAM or disc mode, and verifying cluster status via the web UI.
This article explains RabbitMQ’s architecture, details its core components, walks through the five main messaging patterns with visual diagrams, provides complete Java code examples for each pattern, and discusses reliability mechanisms such as acknowledgments, persistence, and practical use‑case scenarios.
This guide explains RabbitMQ's core concepts, architecture, installation via 1Panel, configuration of the Webman RabbitMQ plugin, and demonstrates how to set up producers and consumers with code examples for reliable message handling.
This article provides a detailed overview of RocketMQ, covering its core concepts, four primary usage scenarios, architectural components such as NameServer, Broker, Producer, and Consumer, as well as message storage, ordering guarantees, high availability, fault tolerance, and transactional messaging.
