Slice & Dice your Monolith with Domain Driven Design
summary
Live-coding shows how an anemic monolith becomes a model-first DDD system: custom immutable value types (OrderNumber, Price), JPA 2.1 attribute converters and JSF phase converters, minimizing mutability and exposing only safe factory methods; OrderItems modeled as @ElementCollection embeddables when small, otherwise entities; read side uses DTO projections (QueryDSL style) for CQRS; migration copies customer schema to a new microservice, then publishes JSON change messages on an ActiveMQ JMS topic to sync the monolith read store, making a practical step toward event sourcing.
AI-written summary · about
chapters (22)
- 0:00Intro
- 2:09Digital Economy
- 3:43Examples of Digital Economy
- 4:27Software Craftsmanship
- 6:32Computer Programming is an Art
- 8:12People Care
- 8:50Domain Driven Design
- 12:07Code Smells
- 13:01Primitive Obsession
- 13:46Go to Make a Type
- 14:11No Pointer Exceptions
- 14:47Splitting
- 15:17Simple vs Complex
- 16:56Wash Rinse Repeat
- 17:46Embrace Events
- 18:36Live Coding
- 28:47Serialization
- 33:04Entities Value Objects
- 38:07Mutability
- 44:30Protection
- 48:27Product
- 51:57Value Object
related talks
45mUsing DDD To Decompose Your Monolith
53mCrafting a self-documenting Modular Monolith with DDD principles (theory not included)
52mBuilding monolith applications that could scale to microservices..
48mDomain Driven Design: The Good Parts
59mDomain-Driven Design - Where Rubber Meets the Road
45mBuilding Monoliths that Could Scale (Easily) to Microservices (If They Need)
02h 29mPractical advice for building glorious monoliths
01h 02mCuring you Domain Model Anemia with Effective & Clean Tips from the Real World