Turns out Domain-Driven Design (DDD) works not only for cargo shipping. Domain-driven design consists of a set of patterns for building enterprise applications from the domain model out. In your software career you may well have encountered many of these ideas already, especially if you are a seasoned developer in …
The greenfield project started out so promising. Instead of devolving into big ball of mud, the team decided to apply domain-driven design principles. Ubiquitous language, proper boundaries, encapsulation, it all made sense.
For the long-time database focused developer, setting persistence concerns in the back seat as you shift your focus to designing software around solving business problems is a scary prospect. But it doesn’t need to be.
How can we quickly tell what an application is about? How can we quickly tell what it does? How can we distinguish business concepts from architecture clutter? How can we quickly find the code we want to change? How can we instinctively know where to add code for new features? …
This session allows you to examine the essential elements of Domain-Driven Design (DDD), both the strategic and tactical modeling tools. Attendees see the problems commonly faced without the use of DDD. By looking at the common struggles and failings in many enterprises, developers are helped to find avoid the same …
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?
