We were working on a project that was starting to implement some form of Service Oriented Architecture (SOA) and Microservices. Why I read this bookĪlthough this book was originally published in 2004, I only got round to reading it the first time circa 2009 when it was recommended to me by a colleague at the time. Especially if you're working on any project that may have elements of microservices, because fundamentally Microservices are nothing more than Domain Services. We may even start to dabble with developing Micro-services.įor many developers out in the field, it's highly likely they are actually implementing the concepts presented in Domain Driven Design, without explicitly knowing about it. When working on larger projects or in software development teams we may learn about concepts such as the Repository Pattern and Model Driven Design and may even implement Software Design Patterns and take an interest in Patterns of Enterprise Application Architecture. There is a tendency to focus on the features and implementation details of the Software Development languages and frameworks and just simply trying to solve problems. Software Developers tend to pay for attention to the hard skills, when it comes to software development. A fantastic book on how you can make the design of your software match your mental model of the problem domain you are addressing.
0 Comments
Leave a Reply. |