Rebuilding Twitter Following Clean Architecture and Domain-Driven Design
summary
Rebuilds a Twitter-sized system by showing concrete steps: use Big Picture event storming then process modeling to find bounded contexts, map integrations and extract domains; model the timeline with small list timeline aggregate units (avoid one “God aggregate”), merge aggregates only when invariants require synchronous consistency, and accept eventual consistency elsewhere. Shows folder layout + clean architecture layers (presentation → application → infrastructure → domain), CQRS handlers, repository interfaces with an EF Core example, and a Figma/online EventStorming tool used for collaboration.
AI-written summary · about
chapters (17)
- 0:00Rebuilding Twitter with DDD
- 2:06Motivation and overview
- 4:56Strategic DDD design
- 6:21Event storming boundaries
- 14:49Core and supporting subdomains
- 16:55Context mapping relationships
- 19:01Process modeling
- 28:07Bounded contexts and language
- 31:17Tactical DDD design
- 33:04Entities and value objects
- 34:51Timeline subdomain modeling
- 38:26Aggregates and consistency
- 42:43Entity or value object?
- 45:31Small aggregates for performance
- 51:10Clean architecture layers
- 55:01Twitter codebase structure
- 58:15Summary and resources
related talks
40mArchitecture Modernization with DDD
54mThinking in Events
50mDomain Prototyping or Design Is How It Works
37mBuilt to last: A domain-driven approach to beautiful systems
45mDomain-Driven Design in Micro Frontends
01h 02mBuilding that glorious monolith. And carving it too.
58mBuilding that glorious monolith. And carving it too.
50mDomain-Driven Transformation