Event Sourcing & CQRS · Capstone
Capstone: Should We Event-Source It?
Evaluate event sourcing for three systems and justify each decision.
Scenario
Your company is considering event sourcing for: (1) the customer support ticketing system, (2) the product catalog CMS, and (3) insurance claims processing (multi-step approvals, regulatory audits, frequent disputes about who changed what).
Requirements
- Recommend per system
- Justify with costs and benefits
- Propose alternatives where you say no
Constraints
- Two teams have no event-sourcing experience
Deliverables
- Make and justify a recommendation for each system.
Draft each deliverable below before revealing the model answer and rubric.
Further reading: Azure: Event Sourcing — when to use
Deliverables
Make and justify a recommendation for each system.
Model answer
(1) Ticketing: probably not full ES — CRUD + an append-only activity log covers history needs; maybe ES for SLA timers later. (2) Catalog CMS: no — edit-heavy, ad-hoc queries, little value in history beyond revisions (use versioned documents/temporal tables). (3) Claims: yes — complex state transitions, regulatory audit, disputes; start with this bounded context, invest in training, use a framework or Postgres-based store, integration events via outbox.
Rubric
Strong answers apply ES selectively, consider team skills, and offer lighter alternatives (audit logs, temporal tables, CDC).
Open in the app to mark lessons complete, take notes and track your progress.