Published on 09 June 2013 by @mathiasverraes
Data Mappers (like Doctrine2) help us a lot to persist data. Yet many projects are still struggling with tough questions: - Where to put business logic? - How to protect our code from abuse? - Where to put queries, and how test them?
Let’s look beyond the old Gang of Four design patterns, and take some clues from tactical Domain Driven Design. At the heart of our models, we can use Value Objects and Entities, with tightly defined consistency boundaries. Repositories abstract away the persistence. Encapsulated Operations helps us to protect invariants. And if we need to manage a lot of complexity, the Specification pattern helps us express business rules in the language of the business.
These patterns help us evolve from structural data models, to rich behavioral models. They capture not just state and relationships, but true meaning.
The presentation is a fast paced introduction to some patterns and ideas that will make your Domain Model expressive, unbreakable, and beautiful.
Check out Elephant in the Room #002: The Heart and Soul of OOP for more info about Value Objects.
Follow @mathiasverraes on Twitter.
|Introduction to Event Storming||CukeUp||Workshop||London, UK||April 14-15|
|CQRS/EventSourcing + EventStorming||NCrafts||Workshop||Paris, FR||May 11|
|TBD||NCrafts||Talk||Paris, FR||May 12-13|
|Experiencing Domain-Driven Design||Value Object Comm.V||Workshop||Berlin, DE||July 6-8|
|Tactical Domain-Driven Design||Laracon EU||Workshop||Amsterdam, NL||Aug|
|Experiencing Domain-Driven Design||Value Object Comm.V||Workshop||Amsterdam, NL||Sep 7-9|
|TBD||TYPO3 Developer Days||Talk||Nürnberg, DE||Sep|
This work by Mathias Verraes is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 License.