/blog / series/ddd-hexagonal-symfony
$ DDD, CQRS and Hexagonal Architecture in Symfony 8
1 posts, in reading order
Domain-Driven Design and Hexagonal Architecture as they behave in a real Symfony 8 codebase: which component does what, what goes in which YAML file, and where the framework helps versus where it quietly pulls the design apart. The running example is a money-lending domain, built one block at a time.
Each part adds one layer to the same application — the domain model and the dependency rule, the application layer and a working HTTP API, CQRS read models, domain events on an asynchronous Messenger transport, then event sourcing swapped in behind the same port. Every recommendation comes with its cost, and the final part is the bill, measured from the example repository: what all of it buys, and the thresholds below which it is over-engineering.
$ Posts in this series
15 min readNEW
The Domain Model, and the Only Rule That Matters
Part 1 of a Symfony 8 series: modelling money lending in PHP 8.5, keeping the container out of the domain, and choosing between Doctrine ORM and DBAL with the costs on the table.
DDD, CQRS and Hexagonal Architecture in Symfony 8 · part 1#ddd#hexagonal-architecture#symfony#php#doctrine#software-architecture