Decoupling Domain Code from Framework and Infrastructure
summary
Examines why and how to separate application and domain code from Symfony framework and infrastructure code. Explains techniques to keep domain logic framework-agnostic so code becomes cleaner, more testable, easier to upgrade, and simpler to integrate with new technologies, using Symfony as the concrete example.
AI-written summary · about
chapters (12)
- 0:00Domain and infrastructure
- 2:30Infrastructure testing problems
- 6:47Identifying infrastructure code
- 10:46Decouple domain and infrastructure
- 11:48Layered architecture separation
- 15:41Dependency inversion with abstract repos
- 17:06Practical refactor example
- 26:49Folder structure separation
- 30:20Testing architecture dependencies
- 32:05Benefits of decoupling
- 33:32Managing framework updates
- 34:38Q&A
related talks
25mCode decoupling from Symfony (and others frameworks)
38mHow to Effectively Isolate Layers?
31mSymfony and Hexagonal Architecture
54mFrom domain to code: a practical approach
27mForgoing the Framework While Working with a Framework
39mKeynote: Symfony without the Framework Bundle
43mControllers: Beyond HTTP and Symfony
17mSymfony Without Bundles