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.
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.
This article explains how to use RocketMQ's transactional messages and an atomic‑level wrapper to achieve sub‑second final consistency for million‑scale transaction systems, detailing the two‑phase commit workflow, annotation‑driven implementation, performance optimizations, failure handling, monitoring, and suitable use cases.
Discover the three stages where MQ messages can be lost and explore five practical solutions—including producer confirmations, message persistence, consumer acknowledgments, transactional messaging, and retry with dead‑letter queues—complete with code examples and guidance on selecting the right approach for different scenarios.
This article explains why messages can be lost in Kafka, analyzes the production, storage, and consumption stages, and provides concrete configurations, detection methods, coding practices, and transactional patterns to ensure end‑to‑end reliability, especially for interview scenarios.
This article dissects Kafka’s storage architecture, identifies loss points in production, storage, and consumption phases, and presents interview‑ready strategies—including acks settings, flush tuning, consumer batch commits, detection via sequence numbers, and transactional messaging—to guarantee virtually 100 % message durability.
This article explores ten practical use cases for message queues, from system decoupling and asynchronous processing to traffic shaping, data synchronization, log collection, broadcasting, ordered and delayed messages, retry mechanisms, and transactional messaging, providing code examples and best‑practice recommendations for robust backend design.
This article examines the limitations of the CAP theorem in modern microservice architectures, introduces the BASE model for eventual consistency, and evaluates practical solutions such as write RPC retries, synchronous and transactional messaging, and local message tables to achieve reliable data consistency across distributed services.
This article explains how TDMQ RocketMQ's transactional messaging works, covering the underlying concepts, three‑phase processing flow, key terminology, source‑code details, practical Java examples, and important considerations for building reliable distributed transactions.
This article explores why message queues can lose consistency, presents concrete solutions such as transactional two‑phase commits, persistence settings, replica configurations, unique IDs, idempotent designs, and dead‑letter queues, and shares ten practical lessons drawn from real‑world incidents.
This article explains RocketMQ's transactional message mechanism, covering half‑message concepts, back‑check processes, implementation steps with code examples, and how to achieve reliable event handling and distributed transaction consistency in a microservice architecture.
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 article explains the practical problems encountered when using Kafka directly, introduces SFMQ—a Kafka‑based HTTP proxy that unifies client access, simplifies upgrades, provides delay and transaction capabilities via Redis, and demonstrates how its architecture resolves producer, consumer, and operational challenges.
This article compares four distributed transaction solutions—local message tables, RocketMQ transactional messages, Seata AT mode, and Seata TCC mode—detailing their advantages, limitations, workflow phases, and common exception‑handling techniques for ensuring data consistency across services.
This article explains the principles of distributed transaction messages, comparing 2PC, TCC, and transactional messaging, and provides detailed walkthroughs of RocketMQ and Kafka implementations, including their two‑phase processes, broker handling, and source‑code insights for ensuring data consistency in asynchronous systems.
This article explains the three core benefits of message queues, compares major MQ products, details RocketMQ's advantages, internal models, reliability mechanisms, load‑balancing, storage design, and practical code examples, guiding engineers to make informed architectural decisions.
This article explains RocketMQ's advanced features—transactional messaging, ordered messaging, SQL‑based filtering, delayed messaging, and global high‑availability—detailing their principles, implementation steps, practical demos, and how they solve consistency challenges in large‑scale e‑commerce systems.
This guide explains how to achieve reliable message consistency in a Spring Boot 2.3.9 application using RocketMQ 4.8.0 by outlining the transactional message flow, broker handling, project structure, code implementation, and testing procedures.
This article provides an in‑depth tutorial on RocketMQ, covering normal, ordered, delayed, transactional, and batch messages, their production and consumption patterns, retry mechanisms, message filtering, and dead‑letter handling, complete with Java code examples for each scenario.
This article explains how RocketMQ implements distributed transaction messages using a two‑phase commit model, detailing the problems with RPC and ordinary MQ, the step‑by‑step workflow, relevant code snippets, and how consistency is ensured across microservice subsystems.
This article explains the challenges of maintaining atomicity across multiple downstream services in distributed systems and details how RocketMQ's transactional message feature provides a two‑phase commit mechanism, lifecycle, implementation details, and practical usage to achieve eventual consistency.
This article explains the challenges of distributed transactions, reviews common solutions such as 2PC, 3PC, TCC, Saga, local message tables, and MQ‑based approaches, and discusses how RocketMQ, Kafka, and RabbitMQ handle transactional messaging, message loss prevention, and duplicate processing.
This article provides a comprehensive guide to RocketMQ, covering Windows installation, environment configuration, startup commands, visual monitoring integration, SpringBoot dependency setup, core components, message models, reliability strategies, idempotent processing, transactional messaging, and ordering guarantees for distributed systems.
This article explains the principles and implementation of RocketMQ's transactional messages, batch messages, and delayed messages, describing the message flow, compensation mechanisms, broker and producer handling, and providing detailed source code snippets to illustrate each process.
The article outlines essential practices for migrating to microservices, covering service dependency rules to avoid circular dependencies, interface version compatibility strategies, isolation techniques for data, deployment and business logic, and methods to ensure eventual data consistency using scheduled retries and transactional messaging.
The article analyzes three typical RocketMQ message‑loss scenarios—network glitches during production, incomplete disk persistence, and premature consumer acknowledgments—and presents concrete solutions such as transactional messaging, synchronous flush with replication, and proper consumer‑ack handling, while discussing their performance impact.
This guide explains the principle and step‑by‑step implementation of reliable transactional messaging using Spring Boot 2.3.9 and RocketMQ 4.8.0, covering execution flow, broker handling, project structure, code examples for entities, repositories, services, listeners, and testing.
The article compares how RocketMQ, Apache Kafka, and Apache Pulsar implement transactional messaging—each using a two‑phase commit with half‑messages or transaction buffers, distinct coordinators, and idempotent producers—to provide atomicity and either strong consistency (RocketMQ) or exactly‑once delivery for high‑throughput stream processing (Kafka and Pulsar).
This article examines the common situations where messages can be lost in RocketMQ—such as network glitches during production, asynchronous disk flushing, and premature consumer acknowledgments—and presents practical strategies like transactional messaging, synchronous flushing, broker replication, and proper consumer listener handling to achieve zero loss.
This article explains why message middleware guarantees at‑least‑once delivery, the challenges of duplicate consumption, and presents both simple and advanced deduplication strategies—including transactional and non‑transactional approaches using relational databases or Redis—to achieve effectively exactly‑once semantics in RocketMQ.
The article explains how to guarantee data consistency across distributed systems by using local transactions, two‑phase commit protocols, message‑queue based eventual consistency, deduplication techniques, and practical RocketMQ transactional messaging code examples in Java.
The article examines how to prevent data inconsistency during cross‑service money transfers by using local transactions, two‑phase commit, and message‑queue based eventual consistency, providing detailed code examples, performance considerations, and practical solutions for large‑scale backend systems.
This article explains how to guarantee data consistency when updating multiple tables or services by using local transactions for single‑node systems, two‑phase commit for distributed databases, and reliable message‑queue patterns—including RocketMQ transactional messages—to achieve eventual consistency and handle duplicate delivery.
This article examines the challenges of distributed transactions in microservice architectures and compares five practical solutions—Seata (2PC), TCC, transactional messaging, local message tables, and a custom Kola approach—highlighting their principles, implementations, advantages, and prerequisites.
This article provides a comprehensive guide to using Apache RocketMQ with Spring Boot, covering core components, basic concepts, key features, step‑by‑step configuration, producer and consumer code examples, advanced message types, transaction handling, and common interview questions for distributed messaging systems.
The article explains how to detect and prevent message loss, guarantee reliable delivery, handle duplicate consumption, manage message backlog, and implement distributed transaction messages in systems like Kafka, RocketMQ, and RabbitMQ, providing practical code examples and best‑practice guidelines.
This guide walks through integrating RocketMQ 4.8.0 with Spring Boot 2.3.9, covering dependencies, configuration, code examples for normal, ordered, cluster/broadcast, and transactional messages, and demonstrates testing results with detailed explanations of each messaging mode.
This article explains the advantages and disadvantages of using message middleware in microservice architectures and details practical solutions for handling concurrency, ordered processing, duplicate messages, and transactional messaging using patterns like partitioning, outbox tables, CDC, and RocketMQ's two‑phase commit.
This article provides a comprehensive overview of RocketMQ, covering its evolution from early Alibaba messaging engines, the detailed architecture of NameServer, brokers, producers and consumers, the internal source‑code structure, startup process, storage mechanisms, flushing strategies, high‑availability replication, and the implementation of transactional messages.
This article analyzes the possible message loss scenarios in RocketMQ—including producer network issues, broker persistence failures, and consumer acknowledgment problems—and presents practical solutions such as transactional messaging, synchronous disk flushing, and proper consumer handling to achieve zero message loss.
This article explains the three common scenarios where messages can be lost in RocketMQ, analyzes their root causes, and presents concrete solutions—including transactional messaging, synchronous disk flushing with replication, and proper consumer acknowledgment—to achieve zero‑message loss while noting the performance trade‑offs.
This article explains the design and implementation of RocketMQ transactional messages, covering a complete order‑creation example, the producer’s transaction listener, the broker’s handling of half messages, transaction checks, and the final commit or rollback process.
This article examines common RocketMQ message loss scenarios—including network glitches, asynchronous disk flushing, and consumer acknowledgment failures—and presents practical solutions such as transactional messaging, synchronous flush configuration, and proper consumer handling to achieve zero message loss.
This article provides a comprehensive guide to Kafka's producer API, covering core concepts, client‑side workflow, essential configurations, idempotent and transactional producers, and practical Java code examples to help developers avoid common pitfalls and optimize message publishing.
This article explains a lightweight transactional message solution for microservices that leverages RabbitMQ, MySQL, and Spring Boot to achieve eventual consistency, detailing design principles, compensation mechanisms, table schemas, and deployment considerations for high‑throughput asynchronous processing.
This article explains a lightweight, low‑intrusive transactional message solution for microservices using Spring Boot, RabbitMQ, and MySQL, covering design principles, table schemas, transaction synchronization, compensation mechanisms, code implementation, and deployment considerations to achieve eventual consistency without sacrificing performance.
This article details a lightweight transactional message solution for microservices that stores pending messages in a local MySQL table, defers RabbitMQ publishing until after transaction commit, and includes compensation logic with exponential back‑off to ensure reliable asynchronous communication.
This article explains how Kafka implements idempotent producers and transactional messaging to achieve exactly‑once semantics, detailing the producer session identifiers, sequence numbers, broker checks, two‑phase commit workflow, consumer isolation levels, and the limitations of atomic reads.
This article explains how to detect and prevent message loss, guarantee reliable delivery across production, storage, and consumption stages, handle duplicate messages with idempotent designs, resolve message backlogs, and implement distributed transactions using transactional messages in systems like Kafka, RocketMQ, and RabbitMQ.
This article provides a comprehensive guide to using Spring‑Kafka, covering simple integration, embedded Kafka for testing, creating topics programmatically, advanced KafkaTemplate usage, transactional messaging, ReplyingKafkaTemplate for request‑reply, listener configurations, manual acknowledgments, lifecycle control, message forwarding, and retry with dead‑letter queues.
This article introduces QMQ, Qunar's internal distributed message queue, covering its background, design motivations, core concepts, code examples for producing and consuming both real‑time and delayed messages, transactional messaging support, and the overall architecture of its metaserver, broker, and delay components.
This article provides a comprehensive overview of Kafka's architecture, covering topics, partitions, producer and consumer workflows, replication and leader election, offset management, consumer group coordination, rebalance processes, delivery semantics (at‑most‑once, at‑least‑once, exactly‑once), transactional messaging, and underlying file and configuration details.
This article explains how RocketMQ’s transactional message feature enables distributed transaction final consistency by using half messages, message check‑back, and defined transaction states, and provides complete Java code samples for producers, listeners, and consumer idempotency handling.
This article explains why transactions are essential, traces their origin from early XA specifications, examines the CAP and BASE theories that expose challenges in distributed systems, and reviews practical solutions such as two‑phase commit, three‑phase commit, TCC, asynchronous messaging, Saga and Gossip protocols, highlighting their trade‑offs and when to apply each.
This article explains the challenges of achieving consistency in distributed systems and presents practical solutions such as two‑phase commit, asynchronous assurance, compensating transactions, message retry mechanisms, idempotent designs, and a custom Redis‑based delayed queue (DelayQ) with a transactional proxy (TMQProxy) to provide reliable transactional messaging.
