Consistency (commit rollback while controlling multiple things through a message mechanism or directly use JTA), that is to say, any consistency is a two-phase implementation of only distributed things (not a retransmission problem)
message consistency
It means that the business action that generates the message is consistent with the message sending, that is, if the business operation is successful, the corresponding message must be sent, otherwise the message will be lost.
On the other hand, if the business action does not occur or fails, then the message should not be sent.
Consistency is divided into: strong consistency, weak consistency, and eventual consistency according to the real-time nature of modification synchronization