Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action and the creator of the original CloudFoundry.com. His latest startup is eventuate.io, a microservices application platform.
Chris offers a comprehensive set of resources for learning about microservices including articles, an O'Reilly training video, and example code. Learn more
Chris offers a comprehensive consulting services, workshops and hands on training classes to help you use microservices effectively. Get advice
Want to see an example? Check out Chris Richardson's example applications. See code
Join the microservices google group
You have applied the Saga pattern. In order to be reliable, services must atomically publish events whenever their state changes. It is not viable to use a distributed transaction that spans the database and the message broker.
How to reliably/atomically publish events whenever state changes?
The application insert events into an
EVENTS table as part of the local transaction.
A separate process polls the
EVENTS table and publishes the events to a message broker.
This pattern has the following benefits:
This pattern has the following drawbacks:
Application architecture patterns
Cross cutting concerns