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 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.
This article provides a comprehensive overview of Apache RocketMQ, covering its core concepts, message models, reliability mechanisms, ordered message challenges and solutions, as well as detailed explanations of transactional messages, including implementation principles, producer and broker workflows, and practical considerations for ensuring consistency in distributed systems.
This article examines the challenges of maintaining data consistency across micro‑service boundaries, walks through real‑world payment and gifting scenarios, compares classic solutions such as 2PC, saga, TCC, local‑message tables and transaction messages, and finally recommends a pragmatic approach for building reliable distributed transaction mechanisms.
This article analyzes why ZuanZuan built its own RocketMQ transaction‑message solution, compares the custom implementation with the community edition’s two‑phase commit approach, explains the underlying principles, sending flow, failure handling, and unknown‑state processing, and summarizes the trade‑offs of each design.
This article explains how to achieve strong consistency for high‑traffic flash‑sale (seckill) scenarios by using distributed transaction principles, flexible transaction models, and Alibaba Cloud RocketMQ transactional messages, providing detailed architectural guidance, implementation steps, code examples, and operational best practices.
This article explains why Kuaishou needed a dedicated online messaging system, how RocketMQ was chosen and integrated, the deployment strategies, client SDK design, load‑balancing and disaster‑recovery mechanisms, diverse message features, distributed reconciliation monitoring, and performance‑tuning parameters.
This article explains how to achieve eventual consistency for cross‑service transactions in a distributed environment by using RocketMQ's transactional messages, detailing the underlying principles, message flow, implementation steps for producers and consumers, and important usage limitations.
This article explains the internal workflow of RocketMQ transactional messages, covering how producers send half messages, how brokers process commit or rollback requests, the storage mechanisms for transaction state, the periodic transaction check logic, and the differences between file‑system and database implementations.
