NET Domain-Driven Design with C#: Problem, Design, Solution (Programmer to Programmer)
NET Domain-Driven Design with C#: Problem, Design, Solution (Programmer to Programmer) by Tim McCarthy
- Binding:
- Paperback
- Number of Pages:
- 432
- ISBN:
- 0470147563
- Product Group:
- book
- Publisher:
- John Wiley & Sons
- Publication Date:
- April 18, 2008
- BooksForGeeks.com ID:
- 3788
Buy NET Domain-Driven Design with C#: Problem, Design, Solution (Programmer to Programmer) from Amazon »
This first technical title of its kind, this is a revolutionary book for the object oriented developer. It takes the reader through the intense process of building a real-world application using Domain-Driven Design principles implemented in C# 3. 0 (. NET Framework 3. 5).
Reviews for NET Domain-Driven Design with C#: Problem, Design, Solution (Programmer to Programmer)
-
Completing the DDD trilogy
Rated out of 5 stars, August 12nd, 2008
After reading the seminal work by Eric Evans "Domain-Driven Design: Tackling Complexity in the Heart of Software" I immediately bought in to the DDD way of thinking, although it was all bit abstract and I didn't really know where to start to turn the ideas into an real application.
Then along came "Applying Domain-Driven Design and Patterns: With Examples in C# and .NET" by Jimmy Nilsson, which combined the ideas of Eric Evans with known Design Patterns. However it didn't provide an end to end implementation but suggested ways to architect an application.
Tim's book ".NET Domain-Driven Design with C#: Problem, Design, Solution" seems to be the logical end to the collection of DDD books out at the moment, you can see that the author has understood ideas from Evans and suggested techniques from Nilsson, along with widely known patterns of Fowler (Martin Fowler - Patterns of Enterprise Application Architecture).
In my opinion this is a great book which shows you how to make a solid DDD application that stays true to Evans's original work.
Top banana. -
let down
Rated out of 5 stars, June 12th, 2008
After buying this book I thought it would prove to be a good way to get acquainted with DDD using a real world example however this was spoilt by a number of items:
* Too much code examples detract away from the main DDD principles not sure why the author could not have leveraged more of the existing libraries out there already for things like IoC & persistence
* Most of the unit tests used I would class more as integration tests because they require the database to be present and to be in certain states
* Some of the object designs I did not agree with and found them to go against the S.O.L.I.D. principles and reduce testability
* Some of the source code examples included descriptions that were for the wrong pieces of code
* After downloading the source code from codeplex I could not get basic functionality to work without exceptions being thrown
* Once your passed the chapter 3 the next chapters until chapter 10 all have a sense of deja-vu

