This article comprehensively explains message queue fundamentals including decoupling, async communication, reliability, and buffering; details architecture roles, queue types, persistence, acknowledgment, and protocols; compares ActiveMQ, RabbitMQ, Kafka, RocketMQ, and Pulsar with performance metrics; and provides selection guidance for e-commerce, finance, and big data scenarios.
This weekly report covers November 9–16, 2026 updates across eight cloud-native open-source projects: HiRoute v0.6 adds Omarchy desktop support and agent onboarding guides; Higress 2.2.6 isolates MCP access and AI cache per consumer; AgentTeams 1.2.7 unifies harness images and adds team/task tracing; LoongSuite Pilot 1.17 links sub-agent traces to parent tasks; AgentScope Java 2.0.5 hardens command approval and memory isolation; Nacos advances cross-namespace Skill sharing; RocketMQ optimizes transaction batch threads; and AI Agent Handbook launches an interactive AgentLoop game map.
A comprehensive guide covering message queue reliability patterns using SpringBoot with RabbitMQ and RocketMQ, including a real production incident analysis, core concepts, complete code implementation for reliable delivery, idempotent consumption with Redis SET NX, ordered processing, dead letter queues, and production-ready configurations.
Dead Letter QueueIdempotent ConsumptionMessage Queue
This article details a production-grade Spring Boot 3 online exam system covering domain modeling, constraint-based paper assembly algorithms, anti-cheating measures with behavior logging and risk scoring, auto-grading strategies for objective and subjective questions, high-concurrency handling for exam start/submit, and score analysis with streaming exports.
This comprehensive guide dissects Spring Boot's @Transactional annotation, covering seven propagation behaviors, eight failure scenarios with root causes, core source code analysis, and distributed transaction patterns including local message tables and RocketMQ transaction messages, with practical order-inventory-points examples.
This article explains how RocketMQ LiteTopic solves the task state persistence problem for stateless MCP services by assigning each task a dedicated message channel that acts as an ordered, durable ledger, enabling reliable task tracking, automatic retries, and seamless replica failover without violating the protocol's stateless requirement.
This article details production-ready Go distributed transaction patterns including Outbox for reliable event publishing, RocketMQ transaction messages, SAGA orchestration with compensation, TCC resource reservation, payment unknown-state handling, capacity planning, fault validation matrices, and operational recovery loops with concrete PostgreSQL schemas and Go code examples.
This article explains that Exactly Once semantics in message queues like Kafka only guarantee exactly-once processing within the messaging system's transaction boundary, not for external side effects like payment APIs, and provides practical patterns using database unique constraints, idempotency keys, and timeout handling to achieve true end-to-end exactly-once behavior.
This comprehensive guide covers the five critical MQ production failures — message loss, duplicate consumption, massive backlog, consumer hangs, and dead letter queue blocking — with root cause analysis, emergency mitigation steps, and long-term architectural fixes for RocketMQ, Kafka, and RabbitMQ.
The article explains why message ordering alone fails to prevent business state regressions, detailing how version gaps and unordered consumption cause issues, and presents solutions using event versioning, state machines, and proper Kafka/RocketMQ configuration to ensure correct order processing per order ID while allowing parallelism across orders.
The article analyzes priority messaging in message middleware, comparing implementations across RocketMQ, RabbitMQ, Kafka, and Pulsar, and details techniques like weighted round-robin scheduling, resource reservation, and wait aging to ensure urgent tasks get priority without starving ordinary tasks, including practical code patterns for fair task scheduling.
This comprehensive guide covers Kafka architecture, ISR mechanism, message loss prevention, duplicate consumption solutions, Rebalance protocols, zero-copy/Page Cache performance internals, and a decision tree for choosing between Kafka, RocketMQ, and RabbitMQ.
This comprehensive guide covers RocketMQ production operations including cluster deployment with NameServer and Broker configurations, message retry mechanisms with backoff strategies, dead letter queue handling and reprocessing, monitoring with Prometheus alerts, and troubleshooting procedures for common issues like message accumulation, disk full, and broker failures.
This article details 10 practical message queue scenarios for Spring Boot microservices, covering system decoupling, asynchronous processing, traffic shaping for flash sales, data synchronization, centralized logging, broadcast configuration updates, ordered message processing, delayed messages for timeouts, retry mechanisms with dead-letter queues, and transactional messaging for distributed consistency, with code examples for RabbitMQ, Kafka, and RocketMQ.
This article introduces a production-ready Go Gin DDD scaffold featuring four-layer architecture, RocketMQ event-driven messaging, dual MySQL/PostgreSQL databases, unified responses, and step-by-step guides for setup and new module development.
The article explains how RocketMQ 5.5.0 introduces the LiteTopic model to support AI workloads, detailing its lightweight two‑layer topic design, automatic creation, RocksDB indexing, event‑driven consumption, precise flow control, and provides step‑by‑step setup and code examples.
A late‑night logistics alert revealed that out‑of‑order RocketMQ events caused order and shipment statuses to diverge, prompting a root‑cause analysis that uncovered a gift‑giving feature’s simultaneous event publishing and led to two mitigation strategies: delayed sending and ordered messages.
This article shares real-world RocketMQ production lessons from an e-commerce platform, covering message sending reliability, idempotent consumption, backlog handling, dead letter queues, and configuration best practices with code examples.
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.
The article explains how RocketMQ’s transactional message mechanism guarantees consistency between order creation and inventory deduction by using half‑messages, a local transaction callback, a second‑phase confirmation, and broker‑side timeout checks, while highlighting common pitfalls and best‑practice recommendations.
The article analyzes the engineering challenges of large‑scale multi‑agent AI systems—such as connection loss, synchronous blocking, and traffic spikes—and explains how Huawei Cloud AI Queue, built on RocketMQ with Lite Topic, Session Log, and priority topics, provides an event‑driven, elastic, and observable communication backbone for stable, scalable agent collaboration.
This article provides a comprehensive comparison of RabbitMQ, Kafka, and RocketMQ across core features, performance, and use cases, with production-ready code for transactional messaging, idempotent consumption, and zero-loss configurations, plus solutions for seven common production pitfalls and interview answer templates.
The article explains why messages can be lost in RocketMQ at the producer, broker, or consumer level and provides concrete strategies—including synchronous sending, async retries, synchronous disk flush, synchronous replication, and manual consumer acknowledgment with dead‑letter monitoring—to ensure reliable delivery.
This article explains how to guarantee message ordering in message queues by comparing RocketMQ, Kafka, and RabbitMQ implementations, detailing partial ordering via business key hashing, providing production-ready code for producers and consumers, and covering business-level safeguards like state machines and idempotency to handle queue rebalancing and head-of-line blocking.
The article explains a reliable, idempotent solution for automatically cancelling orders that remain unpaid after a configured deadline, covering data modeling, state transitions, trigger mechanisms using delayed messages or scans, handling race conditions with payment, and essential monitoring and pitfalls.
This article presents a three-phase framework for handling MQ message backlogs in production: immediate mitigation via consumer scaling, business degradation, and message dumping; systematic root cause analysis across producer, broker, and consumer layers; and long-term prevention through traffic control, async processing, monitoring, and automated dead-letter handling, with RocketMQ code examples.
This article walks through the step‑by‑step design of a production‑ready AIOps platform that tackles massive alert storms in a large e‑commerce environment by unifying signal ingestion, deduplication, RBAC, outbox‑driven event publishing, and sub‑second WebSocket push, all backed by Spring Boot 3.x, MySQL, Redis and RocketMQ.
The ACM FSE‑2026 industry paper introduces a replication‑free failover mechanism for cloud‑native stateful services like Apache RocketMQ, using protocol‑level write isolation and multi‑attach storage to achieve second‑level recovery without extra data copies, while maintaining low cost and near‑native throughput.
This white‑paper dissects why a monolithic MySQL‑based order service collapses under peak traffic and presents a layered, asynchronous architecture—using Redis for stock pre‑allocation, RocketMQ for transactional messaging, sharding, idempotency, and comprehensive observability—to reliably handle tens of millions of queries per second.
The article explains why order‑status updates can become out‑of‑order in high‑traffic systems, how RocketMQ’s ordered‑message feature guarantees per‑key sequencing while highlighting its trade‑offs, and provides concrete producer and consumer implementations, failure handling, scaling, and deployment guidelines to ensure reliable, idempotent order processing.
The article dissects a multi‑Agent workflow that stalls for minutes, exposing why traditional message queues cannot handle AI‑driven long‑running, stateful sessions and how RocketMQ’s 5.x LiteTopic, event‑driven pull, and Suspend consumption model redesign the communication paradigm for AI workloads.
This article dissects TDMQ RocketMQ's Lite Topic, explaining its two‑level topic model, automatic lifecycle, storage reuse, client‑level subscription management with Ready Event Sets, and the exclusive "latest‑connection‑wins" consumption mode that together enable millions of lightweight channels for AI‑native applications.
During a traffic peak the order service saw 30‑second consumer latency and a backlog of over 20 000 messages; by adjusting five RocketMQ consumer parameters—pullBatchSize, consumeThreadMin/Max, adjustThreadPoolNumsThreshold, pullTimeoutMillis, socketTimeoutMillis, and consumeMessageBatchMaxSize—the team reduced end‑to‑end latency to 500 ms, raised TPS to over 2500, and cleared the backlog.
The article explains why traditional synchronous calls block AI agents, introduces RocketMQ 5.5.0's LiteTopic designed for AI workloads, and demonstrates with Java code how to build a non‑blocking multi‑agent system, manage distributed session state, and intelligently schedule GPU resources.
This article introduces a runnable microservices learning project built with three independent Spring Boot applications (gateway, order, stock) and middleware such as Nacos, MySQL, Redis, RocketMQ, and Seata, guiding readers through cloning the repository, starting the environment with Docker Compose, and verifying the end‑to‑end product‑order‑stock flow.
The article analyzes the communication challenges of AI‑native applications—async coordination, per‑session isolation, and millions of independent channels—and shows how RocketMQ Lite Topic solves them with lightweight, auto‑reclaimed topics that guarantee strict ordering, fault‑tolerant streaming, and seamless break‑resume handling.
This article compares Kafka, RocketMQ, RabbitMQ, and ActiveMQ, explaining their architectures, core concepts, strengths and weaknesses, and provides practical guidance on selecting the most suitable queue based on throughput, reliability, scalability, and use‑case requirements.
When a high‑traffic system processes billions of messages per day, stale “zombie” messages can corrupt business state; this article walks through the evolution from never‑expiring queues to uniform TTL, then per‑topic and per‑message TTL, and finally to smart, context‑aware expiration, detailing the engineering trade‑offs, implementation patterns, and operational checklist needed for reliable 10 M‑QPS message pipelines.
The article analyzes the pitfalls of synchronous calls in a payroll microservice, defines domain events and their naming conventions, compares them with message‑queue messages, and presents two concrete implementations—Spring ApplicationEvent for intra‑process decoupling and RocketMQ with a transactional outbox for cross‑process communication—while also clarifying when event sourcing is appropriate.
The article analyses why sending a message is easy but guaranteeing end‑to‑end consistency across databases, brokers, networks and services is hard, explains the exact problems RocketMQ transactional messages solve, compares them with Outbox and CDC, and provides a complete production‑grade design, implementation, monitoring and tuning guide.
This article analyses why delayed messaging is a critical system bottleneck, compares RabbitMQ and RocketMQ implementations—including TTL+DLX, delayed‑plugin, fixed‑level and timestamp‑based approaches—provides detailed architectural diagrams, code samples, scaling strategies, operational checklists, and guidance on choosing the right solution for production workloads.
This article walks through setting up the foundational environment for a real‑time data visualization pipeline using RocketMQ, Flink, Elasticsearch and Kibana, covering code configuration, index verification, Kibana dashboard creation, and practical production tips.
This article walks through setting up a real‑time dashboard stack using RocketMQ, Flink, Elasticsearch and Kibana, covering environment preparation, order data simulation, Flink job creation with source, transformation and Elasticsearch upsert sink, and visualisation considerations.
This article analyzes RocketMQ’s storage high‑availability, detailing the CommitLog, ConsumeQueue, flushing and replication mechanisms, comparing traditional master‑slave, DLedger and Controller modes, and provides engineering configurations, code examples, capacity planning, Kubernetes deployment, monitoring and recovery practices for production‑grade fault tolerance.
The article explains why RocketMQ inevitably delivers duplicate messages under at‑least‑once semantics, analyzes root causes in producer, broker and consumer stages, and presents a production‑grade idempotent solution that combines business keys, Redis caching, Redisson locks, a MySQL idempotent table, AOP interception, and comprehensive monitoring to guarantee exactly‑once business outcomes even under high concurrency and Kubernetes graceful shutdown.
The Agentic AICon event gathered over 180 technical professionals to dissect enterprise‑scale agent engineering, presenting the full lifecycle of Agent Infra—including construction, deployment, observability, and intelligent operations—through detailed sessions on HiClaw, AgentRun, AgentLoop, STAROps, and a RocketMQ‑based asynchronous architecture.
The article explains a structured business‑trace logging pattern that records each critical step of a workflow as a node, stores logs in a dedicated MySQL database, aggregates them by a business number, and presents them in a sortable, color‑coded front‑end for both developers and business users.
This tutorial walks through deploying a highly available RocketMQ cluster with Docker Compose, configuring master‑slave brokers, enabling message tracing, integrating Prometheus‑Grafana monitoring, setting up Spring Boot HA properties, applying performance tweaks, validating failover, and troubleshooting common issues.
This article explains why a RocketMQ producer is more than a simple send API, detailing its role in system throughput, consistency and fault isolation, and walks through sending principles, thread models, high‑concurrency design, retry strategies, back‑pressure mechanisms, outbox integration and production‑grade monitoring.
This article explains why message ordering is critical for order‑state flows, demonstrates how to use RocketMQ's ordered messaging and dead‑letter queue features in a Spring Cloud project, shows the full project structure, provides runnable code, testing steps, performance numbers, and common pitfalls.
This article demonstrates how Spring Cloud Stream provides a unified programming model that decouples business logic from the underlying message broker, allowing a single codebase to work with RocketMQ, Kafka, or RabbitMQ by only changing configuration, and walks through project structure, implementation, conditional routing, MQ switching, testing, and common pitfalls.
In systems handling ten‑million QPS, generic message queues like Kafka hit scalability and latency limits, so the article breaks down a three‑question framework—loss tolerance, latency sensitivity, and ordering needs—to match five specialized queue types and guide a transition from a single‑queue approach to a queue matrix.
This tutorial explains why microservices need a message queue, outlines RocketMQ’s core concepts, shows how to set up RocketMQ with Docker Compose, integrates it into Spring Boot projects with detailed producer and consumer code, provides testing steps, and lists common pitfalls and solutions.
At billion‑level request rates, the traditional cache‑aside pattern fails, so the article proposes a three‑layer architecture—Canal captures MySQL binlog, an MQ (RocketMQ/Kafka) buffers changes, and a coordinated local cache service updates L1 caches with short TTL, achieving high performance and eventual consistency.
The article analyzes a real-world sports‑venue management platform, detailing how multi‑level caching, asynchronous processing with RocketMQ, database sharding, service splitting, and Kubernetes auto‑scaling together reduced average response time from 1200 ms to 150 ms, increased throughput eightfold, and achieved 99.95% availability under tens of thousands of QPS.
This guide walks you through the entire lifecycle of a RocketMQ message, identifies where loss can occur, provides step‑by‑step diagnostics using TrackType and timestamps, and offers concrete configuration, command‑line and recovery strategies for producers, brokers and consumers.
In distributed systems, message‑queue backlogs can cripple core services; this article breaks down a six‑step emergency workflow—from alert detection and throttling to temporary scaling, root‑cause analysis, targeted fixes, and final validation—plus long‑term architectural and monitoring strategies, illustrated with real‑world cases and Java code samples.
This article walks through the interview question of designing a message queue that handles billions of messages daily and peaks at millions of QPS, covering traffic calculations, core roles, storage and throughput techniques, scalability, high availability, observability, framework comparisons, a real‑world case study, and key follow‑up interview topics.
The article breaks down RocketMQ’s end‑to‑end reliability design into three checkpoints—producer to broker, broker persistence, and consumer acknowledgment—explaining each mechanism, configuration options, common pitfalls, and practical recommendations for production deployments.
The article explains RocketMQ's ordered messaging model, detailing why disorder occurs during production and consumption, and describing the three-phase mechanism—using MessageQueueSelector, sequential storage, and single‑threaded ordered consumption—to ensure that messages are processed in the exact order they were produced.
This article compares RabbitMQ, RocketMQ, and Kafka on throughput, latency, scalability, and reliability, outlining each system's core features and recommending suitable scenarios such as reliable messaging, high‑performance streaming, and large‑scale real‑time data processing.
RocketMQ 5.0 replaces the monolithic Broker with a stateless Proxy layer that decouples compute from storage, solves scalability, multi‑protocol and cloud‑native adaptation challenges, and is demonstrated through detailed architecture comparisons, Java code samples, and two real‑world IoT and finance case studies showing significant performance and cost benefits.
This article explains how SpringBoot handles transactional messaging to achieve distributed data consistency, covering the concept of transaction messages, CAP theory, final consistency, and three practical implementations using a local message table, Kafka transactions, and RocketMQ, plus idempotency and compensation strategies.
This article examines why message ordering is critical in distributed systems, explains how partition mechanisms in Kafka, RocketMQ, and RabbitMQ enable ordered consumption, and provides detailed SpringBoot implementations, best‑practice guidelines, partition‑key design principles, concurrency settings, idempotency, and real‑world case studies to ensure reliable sequential processing.
This article explains how to use dead‑letter queues (DLX) to isolate failed messages in distributed SpringBoot applications, compares RabbitMQ and RocketMQ support, and presents a complete compensation framework with design principles, code examples, best‑practice guidelines, and a real‑world case study showing a 96% reduction in dead‑letter traffic.
This tutorial explains why RocketMQ is chosen for high‑throughput messaging, outlines its core components and typical scenarios, guides environment setup via Docker or local installation, shows Maven integration, provides Spring Boot configuration, and presents complete producer and consumer code with testing steps, extensions for sync/async messages, and common troubleshooting tips.
During a Meituan second-round interview, the candidate explains how to diagnose and resolve high RocketMQ consumption latency in production, outlining a three‑step approach—stop the bleeding, recover service, and cure the root cause—through consumer scaling, message forwarding, logic optimization, concurrency tuning, queue expansion, and monitoring.
This article breaks down the interview focus points for messaging middleware, explains RocketMQ's "Three High and One Rich" advantages—high throughput, reliability, consistency, and rich features—compares it with Kafka and RabbitMQ, presents six detailed reasons with code samples, a selection decision tree, common interview variants, memory mnemonics, and a concise conclusion for Java developers.
This article walks through why modern systems need a message broker, presents a four‑layer architectural view, compares Kafka, RabbitMQ and RocketMQ across design, performance, routing and transactional capabilities, and offers concrete scenario recommendations, engineering best‑practices, code samples and monitoring guidelines.
This article explains why traditional distributed transactions fail, then details the core principles, state flow, and practical Java/Spring Boot implementation of an atomic‑level RocketMQ transactional message wrapper, covering schema design, idempotency, high‑concurrency handling, monitoring, and deployment for production‑grade microservices.
This guide walks through setting up a two‑node RocketMQ cluster with dual master‑slave asynchronous replication, covering host role assignment, configuration file edits, binary deployment, memory tuning, and the exact commands to start NameServers, master brokers, and slave brokers.
This article analyzes the bottlenecks of real‑time AI voice agents in high‑concurrency scenarios and presents a cloud‑native messaging architecture built on Alibaba Cloud RocketMQ LiteTopic that ensures session stickiness, low latency, automatic channel management, and observable operations for scalable, reliable voice interactions.
AgentScope Java, released by Alibaba's Tongyi Lab, tackles the integration, security, and operational challenges of deploying AI agents in Spring Cloud‑based enterprise systems by introducing a production‑grade ReAct paradigm, real‑time interruption, sandboxing, A2A communication via RocketMQ, and visual debugging tools, all demonstrated with concrete code examples and a detailed feature comparison.
The article analyses why message queues are not a cure‑all, using real e‑commerce and finance incidents to dissect the three core benefits—decoupling, asynchronous processing, and peak‑shaving—while exposing production challenges such as loss, duplication, ordering, dead‑letter handling, and end‑to‑end consistency, and offering concrete Java code, benchmark tables and a practical MQ selection guide.
Facing explosive growth, the game‑service platform 悠悠有品 rebuilt its architecture on Alibaba Cloud, using RocketMQ for core transaction messaging and Kafka for data synchronization, achieving elastic scaling, high availability, cost reduction, and reliable high‑concurrency processing across its trading and analytics pipelines.
This article explains why traditional message‑queue throttling fails in AI inference workloads, introduces Apache RocketMQ 5.x LiteTopic’s lightweight topic model, and details its four core features—physical isolation, elastic scaling, precise flow control, and consumption suspension—that together provide millisecond‑level real‑time throttling and minute‑level busy‑idle scheduling for personalized traffic management.
This article introduces AgentScope Java 1.0, an enterprise‑grade AI agent framework for Java that solves stack fragmentation, security, operations, and multi‑agent collaboration challenges by adopting the ReAct paradigm, offering real‑time interruption, sandbox isolation, RocketMQ‑based A2A communication, visual debugging, and deep Spring Cloud integration.
This article explains the unique challenges of using message queues for AI inference workloads, why traditional throttling methods fall short, and how Apache RocketMQ 5.x's LiteTopic introduces lightweight topics, fine‑grained flow control, physical isolation, and consumption suspension to achieve millisecond‑level real‑time throttling and minute‑level busy‑idle scheduling.
AgentScope Java 1.0, open‑sourced by Alibaba, provides a production‑ready AI agent framework built for Java ecosystems, addressing stack fragmentation, security, operations, and multi‑agent collaboration through ReAct reasoning, real‑time interruption, sandboxing, RocketMQ‑based A2A communication, and visual debugging, with detailed integration guides and comparison to LangChain4j and Spring AI.
The article details how the "Qinbao" parenting app, serving over ten million daily active users and massive photo/video uploads, tackled high‑concurrency writes, instant cross‑device notifications, and distributed transaction consistency by migrating to Alibaba Cloud RocketMQ 5.x Serverless, achieving millisecond latency, elastic scaling, and near‑perfect reliability.
The article outlines the motivation, phased planning, architecture, task breakdown, implementation, and testing of a compact reminder platform built with Java 17/SpringBoot 3, Vue 3, Uniapp, MyBatisPlus, Redis, and RocketMQ, detailing each functional module and UI screen.
This article explains the interview focus points for RocketMQ ordered messages, details the partition‑ordered model and its two‑step guarantee mechanism, provides in‑depth analysis of producer and consumer processes, includes full Java code examples, and outlines best practices, pitfalls, and common misconceptions.
This article breaks down the interview focus points, core answer, deep analysis, code examples, and common pitfalls for ensuring RocketMQ messages never get lost, covering producer, broker, and consumer configurations, trade‑offs, and practical troubleshooting steps.
This article breaks down the interview focus points, core solution framework, underlying RocketMQ mechanisms, step‑by‑step remediation actions, common pitfalls, and a concluding strategy for handling message backlog through emergency scaling, consumer optimization, degradation, dead‑letter handling, and proactive capacity planning.
This article explains how RocketMQ’s consumer model is fundamentally pull‑based with a long‑polling optimization that provides a push‑like experience, covering interview focus points, detailed mechanism, code examples, best practices, and common misconceptions.
This article examines the common data‑consistency challenges when writing to both a database and a Redis cache, evaluates four write‑order strategies, and presents the most reliable approach—writing to the database first then deleting the cache—along with retry mechanisms using scheduled jobs, message queues, and binlog listeners.
This tutorial walks through configuring Canal in cluster mode, enabling MySQL binlog, creating an Elasticsearch index, setting up RocketMQ topics, adjusting Canal properties and instance files, launching services, and implementing a consumer to reliably synchronize MySQL changes into Elasticsearch.
This article compares the storage models, data organization, indexing, read/write processes, and performance trade‑offs of three major message queues—Kafka, RocketMQ, and JMQ—providing detailed technical insights for architects and engineers making storage‑related design decisions.
This article dissects a common interview question about Kafka's higher throughput versus RocketMQ's richer features, explains the underlying design philosophies, storage models, I/O paths, scaling limits, real‑world use cases such as transaction, delayed and ordered messages, and provides concrete optimization steps and code samples to help engineers make an informed messaging platform choice.
This article explains RocketMQ's transactional message mechanism, detailing its three‑phase workflow, half‑message handling, transaction checks, key implementation tips, and production‑grade best practices for achieving reliable eventual consistency in distributed systems.
This guide explains why delayed messages are essential for distributed system stability, compares RabbitMQ's TTL+DLX and delayed‑message plugin, details RocketMQ's precise timing and delay‑level features, and offers custom Redis and time‑wheel solutions with practical Java code examples and deployment tips.
RocketMQ ensures durable, consistent, and highly available message storage through fixed‑length append‑only files, efficient index rebuilding, checkpoint tracking, and configurable master‑slave replication, offering both synchronous and asynchronous HA modes, detailed recovery steps, performance trade‑offs, and practical operational guidelines for robust fault tolerance.
To reliably handle RocketMQ's at-least-once delivery semantics, this guide explains why duplicate consumption is inevitable, outlines three defensive layers—Redis‑based idempotency, database unique constraints, and state‑machine checks—provides production‑grade Java code, and details ACK/retry strategies and monitoring practices for robust systems.
This guide explains the two main steps for expanding a RocketMQ cluster—scaling brokers and scaling name servers—detailing when to add resources, configuration changes, and command examples for a smooth horizontal expansion.
This article dissects the interview question “Should thread pools be shared or exclusive?” by exposing common pitfalls, presenting a systematic analysis of isolation versus reuse, and illustrating best‑practice designs with concrete RocketMQ examples, code snippets, and decision‑making guidelines.
An in‑depth guide to Apache RocketMQ 4.x producer SDK covers essential and optional configurations, internal startup and sending workflows, transaction and ordered messaging, failure handling, performance tuning, monitoring, and practical code examples to help you build a reliable, high‑throughput messaging system.