Symfony and Hexagonal Architecture
summary
Argues that using Symfony as an infrastructure layer and applying ports and adapters (interfaces, dependency injection, concrete adapters) yields a domain decoupled from framework code, raising testability and making vendor or framework upgrades low-effort. Demonstrates refactoring a payment flow that originally appears in 42 places into a gateway interface and adapters, shows a repo+controller+service directory layout for user and payment contexts, and reports successful migration of a complex legacy component out into the hexagonal structure.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:42A NEW APPLICATION IS COMING
- 11:14Coupled code
- 17:03Input ports
- 18:24Adapter example
- 19:16Directories structure example
- 19:36Dependency inversion principle
- 25:40Where can you start from?
related talks
54mHexagonal Architecture in DDD
25mCode decoupling from Symfony (and others frameworks)
40mDDD, CQRS, Hexagonal, Onion,... Putting it together
42mDecoupling Domain Code from Framework and Infrastructure
57mEating spaghetti with Symfony
27mForgoing the Framework While Working with a Framework
34mDon't Let the Framework Stand in Your Way
17mSymfony Without Bundles