Keep RocketMQ Messages Consistent with MySQL Transactions in Spring
· One min read
Writing business data to MySQL and publishing a message are two separate operations. A crash between them can leave the database and message system inconsistent.
Writing business data to MySQL and publishing a message are two separate operations. A crash between them can leave the database and message system inconsistent.
A RocketMQ cluster normally uses multiple independent NameServers and one or more broker groups. Each broker group has a stable brokerName; broker ID 0 is the primary and nonzero IDs are replicas in older master/slave terminology.
RocketMQ is a distributed messaging platform built around NameServer discovery, brokers that store messages, producers, consumers, topics, and message queues.