Skip to content
flowss
Start freeChecking your session

13 templates

Event storming templates

Alberto Brandolini's event-storming board in its canonical colours: orange domain events on a timeline, blue commands, yellow actors, purple policies, pink external systems, green read models and lilac aggregates — with hotspots called out in red. Swimlanes group by bounded context, and the engine flags the shapes DDD says are suspect: an event no command produces, a command with no aggregate, an aggregate with no events.

Event storming syntax reference

  • Event Storm — Order Fulfilment

    Retail order fulfilment across ordering, warehouse and delivery contexts, with two cross-context policies and an uncommanded delivery event the storm leaves on the wall.

    Architecture

  • Event Storm — Hotel Booking

    Reservation, payment authorisation and front desk for a hotel group, surfacing a search command that changes nothing and an authorisation expiry no command produces.

    Business & Strategy

  • Event Storm — Motor Insurance Claim

    First notification of loss through assessment to settlement, showing a single validation command that fans out into an accept and a decline event.

    Flow & Process

  • Event Storm — Emergency Admission

    Emergency department arrival through bed management to the ward, with the discharge event nobody commands and two hotspots concentrated on the bed-request boundary.

    Flow & Process

  • Event Storm — Subscription Billing

    Trial, invoicing and dunning for a SaaS product: four policies chain the contexts together and a failed payment routes into collections.

    Business & Strategy

  • Event Storm — Ride-Hailing Trip

    Rider request, dispatch matching, trip and fare across four bounded contexts, with a driver cancellation event the model never causes.

    Architecture

  • Event Storm — Bank Account Opening

    Application, KYC checks and core banking for a current account, where the identity check fans out into verified and referred and the first payment arrives uncommanded.

    Business & Strategy

  • Event Storm — Warehouse Inbound

    Supplier slot booking through goods-in to putaway, with a quality check that fans out into accepted and quarantined pallets and a stock adjustment nobody commands.

    Flow & Process

  • Event Storm — Content Publishing with Model Moderation

    Newsroom draft through classifier-based moderation to distribution, where the human moderator is declared but sits on no command — the review loop nobody modelled.

    AI & Pipelines

  • Event Storm — Agentic Ticket Refunds

    Support desk, an LLM refund assistant and finance approval, with the assistant's escalation event left uncommanded and a policy-retrieval hotspot on stale guidance.

    AI & Pipelines

  • Event Storm — Rail Ticketing and Delay Repay

    Retailing, fulfilment and delay repay contexts for a train operator, with a compensation policy triggered by a journey completed late, a journey search written up as a command and a refund event nobody produces.

    Architecture

  • Event Storm — Mortgage Origination

    Application, underwriting and completion contexts for a building society, surfacing an affordability recalculation and a land registry charge that no command produces, either side of a surveyor-panel boundary.

    Business & Strategy

  • Event Storm — Electronic Prescription Dispensing

    Prescribing, spine and pharmacy contexts for an electronic prescription service, with a nominated-pharmacy policy, a stock substitution hotspot and an expiry event nobody commands.

    Flow & Process