0 views collected around this technical thread.
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 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 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.