CQRS in Go series: Part 1: the aggregate, Transition() and Clone() Part 2: command handlers without side effects Part 3: sagas and event choreography Part 4: PostgreSQL as an event store The problem — two aggregates need to cooperate Concrete scenario: a payment is validated. The Payment aggregate emits a PaymentConfirmed event. In response, a shipment needs to be created in the Shippin
CQRS in Go — Part 3: sagas and event choreography
Odilon HUGONNOT·Dev.to··1 min read
D
Continue reading on Dev.to
This article was sourced from Dev.to's RSS feed. Visit the original for the complete story.