CDN$ 30.23
  • List Price: CDN$ 47.99
  • You Save: CDN$ 17.76 (37%)
Only 1 left in stock (more on the way).
Ships from and sold by
Gift-wrap available.
Add to Cart
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See all 2 images

.NET Domain-Driven Design with C#: Problem - Design - Solution Paperback – Apr 28 2008

Amazon Price New from Used from
"Please retry"
CDN$ 30.23
CDN$ 23.00 CDN$ 18.27

Join Amazon Student in Canada

Customers Who Bought This Item Also Bought


Product Details

  • Paperback: 432 pages
  • Publisher: Wrox (April 28 2008)
  • Language: English
  • ISBN-10: 0470147563
  • ISBN-13: 978-0470147566
  • Product Dimensions: 23 x 19 x 3 cm
  • Shipping Weight: 662 g
  • Average Customer Review: 3.0 out of 5 stars  See all reviews (1 customer review)
  • Amazon Bestsellers Rank: #576,111 in Books (See Top 100 in Books)
  • See Complete Table of Contents

Inside This Book (Learn More)
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Search inside this book:

Customer Reviews

3.0 out of 5 stars
5 star
4 star
3 star
2 star
1 star
See the customer review
Share your thoughts with other customers

Most helpful customer reviews

Format: Paperback
I've practiced Domain-Driven Design for more than a year. I got a lot hints also from its famous user group. This book helped me to see the points that I diverged from the DDD in my own implementations.
The first chapters are somehow more fundamental since it presents the creation of O/R mapper and infrastructure frameworks which I think for simplicity sake were created mainly in-house rather using current available in the industry.
DDD is a process and I think this book presents the concept quite well, though the pattern for solving the case are repetitive after chapter 6, so I could read through or skip them faster to see what's more the content conveys.
Overall I think this book is just a DDD starter.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again.

Most Helpful Customer Reviews on (beta) 10 reviews
15 of 16 people found the following review helpful
Nice reference app for DDD June 20 2008
By David C. Veeneman - Published on
Format: Paperback Verified Purchase
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#.
7 of 8 people found the following review helpful
Liked it first three hours March 6 2010
By 3P - Published on
Format: Paperback
There are some things I don't like.

1. UnitOfWork is broken. What happens when someone adds entity to repository, and then removes it before commiting? The code will try to remove not existing objects from database and then it will add it!

2. Handling of child objects. For example addresses. In any real world app deleting every child object and then adding it again whether there were changes or not would have no place. First performance. Second what If You have to keep history of changes of that child object? What if they have Id's in database and have other children? What if two users work with same objects? What about concurrency? These are problems I have to deal with every day and I would expect some good examples from book writer. Especially that has so many certificates.

3. This book has a lot of repetitive text/code for every factory/repository/service clsss... I would like to have some discussion about problems I mentioned in p.2

4. WPF that nobody knows (yeah some know, but how many WPF have You seen?) shouldn't be used in book about DDD. Do it in WinForms, ASP.NET or even Console app. Why show us WPF? Hell You can't even build sources from this book without going to 3rd party for their GridControl. What's the point of using WPF?

This book is good for someone that doesn't know much about DDD and is doing apps for one user. O
1 of 1 people found the following review helpful
Great for reference Oct. 16 2009
By Amazon Customer - Published on
Format: Paperback
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.
3 of 4 people found the following review helpful
Useful, but irritating July 29 2008
By Maltese Falcon - Published on
Format: Paperback
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
5 of 7 people found the following review helpful
Important concepts, but impossible to read... Nov. 15 2008
By ColorNerdChris - Published on
Format: Paperback
I think that too many of us who code for fun and profit get caught up in the Smart Client Anti-pattern way of programming due to limited resources and the trappings of RAD. That is why so many of the concepts presented in the book are so important - using real structure so that if you get hit by a bus, someone can read your code and do something with it.

The problem with this book is that it is unreadable.

When a book's goal is to present logical design, but does so in a completely haphazard fashion. Perhaps I expected more of a logical design from a book that talks about logical design.

I feel like there was another book I should have read before this book - I just don't know what that book is. Reading this material without some other primer and coming away with a real sense of DDD is like watching 'Empire' and having a real sense of the entire Star Wars series.

You get a lot of 'Do This', but not a lot of 'This is what needs to happen, and here is how we get there...' Maybe after a few more reads I will get more out of this book, but they are long, slow, painful reads. Sorry Tim - I know how hard it is to write technical material on this high of a level, but this is very unfun reading...

Product Images from Customers