From domain to code: a practical approach

on YouTube ↗54m

" summary

Shows how a domain model actually becomes running code: implement CQRS and command/query buses with Symfony Messenger, keep domain and application layers free of DB concerns, and put Doctrine plumbing in infrastructure. Recommends aggregates with cascades, Doctrine deferred explicit change tracking, UIDs generated in infra and used as primary keys, custom Doctrine types instead of embeddables, persisters that flush and dispatch events, and enforce throws PHP docs enforced by static analysis (Psalm/PHPStan).

AI-written summary · about

" chapters (25)

1. 0:00Intro
2. 0:43Domain D Design
3. 2:01Domain Definitions
4. 4:43Domain Driven Design
5. 7:01CQRS
6. 8:46Layers
7. 9:47Domain
8. 14:02Abstractions
9. 16:23Implementation Focus
10. 18:21UUIDs
11. 21:51Cascades
12. 22:51Chain tracking policy
13. 24:40Custom types
14. 26:04Repository patterns
15. 27:38Buses
16. 29:29Dispatch
17. 30:07The end result
18. 31:30Dispatching events
19. 33:40Best practice for events
20. 34:24Error handling
21. 37:06Treat
22. 38:19Testing
23. 39:54Static analysis
24. 44:18Wrap up
25. 46:24Questions

" related talks

• 56mThe absolute beginner's guide to Domain Driven Design with SymfonyNeal Brooks · sfday 2020
• 59mA CQRS Approach with Api Platform and Symfony MessengerAlfredo Aiello · phpday PUG Edition 2021
• 40mDDD, CQRS, Hexagonal, Onion,... Putting it togetherJeroen Keppens · Dutch PHP Conference 2019
• 01h 03mUnbreakable Domain ModelsMathias Verraes · PHP UK Conference 2014
• 34mLevel up with a Microservices architectureDouglas Reith · Laracon AU 2018
• 44mAn Introduction to Symfony MessengerDenis Brumann · International PHP Conference Spring 2019
• 25mCode decoupling from Symfony (and others frameworks)Miguel Gallardo · PHPConf.Asia 2018
• 27mConfessions of a Backend DeveloperRichard Fussenegger · phpDay 2017