Pattern 53 / CONSISTENCY
Use this when Coordinating local state changes with external messages.
Transactional Messaging fits when Coordinating local state changes with external messages. Mechanism: Wrap state transition and message intent in a durable unit, then deliver asynchronously with retries. Use it for Microservice workflows where distributed transactions are too expensive. The toll: Eventual consistency and operational repair paths must be explicit.
Microservice workflows where distributed transactions are too expensive.
Use transactional messaging when microservice workflows where distributed transactions are too expensive..
Describe the pressure first, then the mechanism, then the cost. That keeps the design grounded.
Same pressure family