EDAPATstill growing

Event-driven patterns

Choose between thin and fat events, coordinate a workflow across services with a saga, and decide when CQRS, event sourcing or event-driven design is worth its cost.

For Developers who know how events and messages travel and want to design with them.

PrerequisitesEDAREL Reliable messaging

7 notes, in order. Each one assumes the one before it. Still growing: more notes may be added.

Notes in this trail

Start the trail
  1. I · What an event carries
    Event notification vs state transfer, not yet read
  2. Asking another service for data, not yet read
  3. II · Workflows across services
    Choreography vs orchestration, not yet read
  4. Sagas, not yet read
  5. III · Reading and storing
    CQRS, not yet read
  6. Event sourcing, not yet read
  7. IV · Judgement
    When to use event-driven design, not yet read