24Jun/10
.NET Domain-Driven Design with C#: Problem – Design – Solution (Programmer to Programmer)
Sponsored By
.NET Domain-Driven Design with C#: Problem - Design - Solution (Programmer to Programmer)
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.
List Price: $ 39.99
Price: [wpramaprice asin="0470147563"]
[wpramareviews asin="0470147563"]
[wprebay kw="domains" num="6" ebcat="-1"] [wprebay kw="domains" num="7" ebcat="-1"]
June 24th, 2010 - 09:08
Nice reference app for DDD,
I’ve been playing with Domain Driven Design off-and-on for about a year now. I’ve read the Evans book (Domain-Driven Design: Tackling Complexity in the Heart of Software), the Nillson book (Applying Domain-Driven Design and Patterns: With Examples in C# and .NET), and the Fowler book (Patterns of Enterprise Application Architecture (The Addison-Wesley Signature Series)), but what I really need is a real-world reference app to put all these concepts together.
That’s what Tim McCarthy’s book does. It presents an anotated reference application, a real estate construction management application built as a WPF smart client. McCarthy’s writing is clear and to-the-point–he simply provides a running commentary on the reference app from a sequence-of-development perspective. He starts with a skeleton and builds out the app from there, discussing his refactorings as he goes. I find this very helpful as a template for developing my own DDD apps.
The reference app is written in C#, as are the book’s code snippets. However, since most of the code discussed boils down to .NET calls, even VB users with only limited experience with C# may find it useful. As C# is my language of choice, it did not present any problem for me.
This is a really good book; the best I’ve bought in a while. I do not hesitate to recommend it to any developer learning DDD in C#.
Was this review helpful to you?
|June 24th, 2010 - 09:57
Useful, but irritating,
I find the book useful in the way it present a design the evolves as the authors attack new parts of the problem area. There are many interesting patterns and ways of dealing with problems that I can see myself using in my own projects.
My main objective is that it can get a bit repetitive. By accident I skipped from the middle of one chapter to the middle of the next. Because of the repetitiveness it took me a while to discover it. At the same time new aspects are constantly introduced so there are still value in the new chapters.
A big annoyance is all the textual errors. It is obvious that cut and paste has been a big part of writing this book, and many times the author has forgotten to update the copied text appriopriately. There is also evidence of the restructuring of the book gone bad, with reference to items not having been introduced yet. It all seems like a bit of a rush job.
Even so, I will give it a pretty high score for the content of the book and the way it can help developers approach their challenges in a good way
Was this review helpful to you?
|June 24th, 2010 - 10:10
Great for reference,
This book was entirely describing the design and implementation of SmartCA application using domain-driven design pattern. The author put every detail of steps in building this application from class design classes, creating solution, configuration, writing unit test… I did not run sample code so I did not know if it actually worked. My focus was the design. The author also provides detail of MVC model for SmartCA application
About the topic, the design was very interesting to me. I used this approach in my past company ( about 10 years ago). However, the design in this book was much cleaner with the favor of .Net 3.5. I like the concept of “the domain model is ignorant of how its data is saved or retrieved from its underlying data store or stores” . The introduction of unitOfWork and Repository objects for each aggregate was good in the design. I think chapter 2 was most important chapter. This described the architecture design of the application, what layer needed, how they interacts with each other. This must be understood completely before moving down to the detail. Once the design pattern was clear, the later chapters provided detail implementations. The structure was similar exception each chapter focus on particular aggregate entity.
I think this book is definitely not for C# beginner. It can be a good reference for higher level.
Was this review helpful to you?
|