Wednesday 2nd December, 2015
9:00am to 6:00pm
For too long Domain-driven design (DDD) has been sold as the ideal solution for very complex problems that only a few teams very actually writing. While technically correct, this statement sparked a number of misconceptions, the most important of which is that DDD requires an object model and must be agnostic of persistence and databases. At the end of the day, DDD is only an approach to the design of software system and is driven by the domain of the problem. The purpose of this talk is clearing the ground around DDD emphasizing the theoretical pillars of the approach: ubiquitous language and bounded context. From there, we’ll move ahead to creating a context map and then finally we’ll touch on the most commonly used supporting architectures for DDD: the popular Domain Model, CQRS and also event-sourcing. The key takeaway is that DDD is not for complex things; it is just a savvy approach for any software, including CRUD.
JetBrains and WURFL technical evangelist, book and Pluralsight author. CTO @ Crionet.com.
Sign in to add slides, notes or videos to this session