.NET Domain-Driven Design with C# (Programmer to Programmer Series)by Tim McCarthy
As the first technical book of its kind, this unique resource walks you through the process of building a real-world application using Domain-Driven Design implemented in C#. Based on a real application for an existing company, each chapter is broken down into specific modules so that you can identify the problem, decide what solution will provide the best results,… See more details below
As the first technical book of its kind, this unique resource walks you through the process of building a real-world application using Domain-Driven Design implemented in C#. Based on a real application for an existing company, each chapter is broken down into specific modules so that you can identify the problem, decide what solution will provide the best results, and then execute that design to solve the problem. With each chapter, you'll build a complete project from beginning to end.
and post it to your social network
Most Helpful Customer Reviews
See all customer reviews >
This book has practical implementations of DDD patterns like Layered Super Type, Unit of work, Persistence Ignorance, Repository, as well as the common patterns like Template method, Specification, and Visitor. I liked the way Tim organized the book, every section enhances and refactors the code of the previous sections. Overall very good read! It's a good reference material for .NET developers who likes to implement the DDD in their software development, along with Domain-Driven Design: Tackling Complexity in the Heart of Software, Applying Domain - Driven Design and Patterns.
This was one book that I was very excited to read. Chapter 2 was when it hit me, this book wasn't what I thought! The entire book is nothing more than a walk-through of an application that the author is building, using DDD. I honestly don't see the point in this book at all, except for putting DDD to practical use, but even still, the author fails to explain some of the concepts in a clean manner. Very often throughout the book does the author make reference to Martin Fowler's book as well as 2 other authors. In fact, the author admits that he wrote this book after reading the other authors' books. If you are able to learn through osmosis then this book is for you. I was able to pick up some things and I was happy about that, but it just wasn't worth finishing the book. I suggest you read fowler's book based on the numerous recommendations that the author gave.
So let me state up front I've known Tim McCarthy for many years and we also worked together until recently. Having said that I recommend this book to those looking to design a custom business application, or those looking to understand how to create a custom business application. The book does an excellent job of taking a hands-on approach and does an excellent job of showing the role of refactoring over the life of a project.