Bridging Business and Frontend: Domain-Driven Design in Modern Web Architecture.
summary
A concrete recipe for untangling a shared frontend user type into per-domain vertical slices: create domain folders (profile/orders/preferences), domain-specific models and repositories (example uses Prisma select in repositories), expose versioned HTTP contracts like API/preferences/v1/notifications, and translate at boundaries with anti-corruption layers (ACL) instead of importing types. Claim: a notification-toggle implementation goes from two-day debugging to two-hour change, granting deployment independence and far fewer merge conflicts.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 7:10DDD fundamentals for frontend
- 14:11Five-step DDD transformation
- 24:57Results and trade-offs
- 26:00Takeaways and next steps
related talks
45mDomain-Driven Design in Micro Frontends
30mThe Art of Front-end Architecture
32mStrategic Domain-Driven Design
37mDemystifying Micro-Frontends
55mDomain Driven Design in practice - how to draw your domain boundaries IRL
55mFront-End Independence with GraphQL and Redux
21m[Eng Sub]if (extensible design) return "work life balance"
31mMigrating from Monolith to Microfrontends