Hexagonal Architecture in DDD
summary
Argues that separating domain from frameworks keeps behavior stable: replaces ActiveRecord in Kohana with a club repository port, concrete adapters (MySQL, Redis) and a file-system adapter for fast Behat tests, and uses PHPSpec-style specs to detect domain shifts. Shows a booking service, a porter that maps requests to domain objects, and controllers that only orchestrate adapters; swapping storage or input formats requires writing an adapter, not changing domain code.
AI-written summary · about
chapters (5)
- 0:00Start
- 5:41ENTITIES & VALUE OBJECTS
- 8:43MODEL DRIVEN DESIGN
- 16:33BOUNDED CONTEXT
- 21:06CONTINUOUS INTEGRATION
related talks
27mConfessions of a Backend Developer
40mDDD, CQRS, Hexagonal, Onion,... Putting it together
31mSymfony and Hexagonal Architecture
01h 29mArchitecture Beyond Clean & Hexagonal
50mStrategic Domain Driven Design in CakePHP How to Get Organized and Get Started
59mDomain Driven Design: The Good Parts
51mEscaping the Framework
37mBuilt to last: A domain-driven approach to beautiful systems