Domain-Driven Design Aggregate Redesign for a Lending API
Overview
What this challenge is about.
Facilitate a 1-day event-storming workshop with 8 participants from product, engineering, risk, and operations to surface domain events. From the events, identify 3-5 bounded contexts (e.g. Origination, Underwriting, Servicing) and the aggregates inside each. Document the ubiquitous language for each context in a glossary that resolves at least 10 current term collisions (e.g. 'Application' means different things to Origination vs Underwriting). Author a 3-phase migration plan over 12 weeks, with the first phase scoped to one bounded context. Deliver workshop artifacts, bounded-context map, aggregate diagrams (Mermaid), glossary, and migration plan.
The Brief
What you'll do, and what you'll demonstrate.
Redesign a lending API into proper DDD bounded contexts and aggregates and propose a phased 12-week migration the engineering org can fund.
Earning criteria — what you'll demonstrate
- Facilitate an event-storming workshop with non-engineers in the room
- Identify bounded contexts from domain events, not org chart
- Design aggregates that own their invariants
- Build a ubiquitous-language glossary that survives PR review
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Product Manager
Product managers who co-facilitate DDD workshops get to shape the ubiquitous language their roadmap is written in.
This challenge sharpens
- event-storming
- ubiquitous-language
- facilitation