Domain-Driven Design: Tackling Complexity In The Heart Of Software
  • Domain-Driven Design: Tackling Complexity In The Heart Of Software
  • Domain-Driven Design: Tackling Complexity In The Heart Of Software
  • Domain-Driven Design: Tackling Complexity In The Heart Of Software
  • Domain-Driven Design: Tackling Complexity In The Heart Of Software
  • Domain-Driven Design: Tackling Complexity In The Heart Of Software
ISBN: 0321125215
EAN13: 9780321125217
Language: English
Release Date: Aug 20, 2003
Pages: 560
Dimensions: 1.4" H x 9.5" L x 7.3" W
Weight: 2.75 lbs.
Format: Hardcover

Domain-Driven Design: Tackling Complexity In The Heart Of Software

by
$43.81
List Price: $74.99
Save: $31.18 (41%)
Select Format
Select Format Format: Hardcover Select Conditions Condition: Very Good

Selected

Format: Hardcover

Condition: Very Good

$43.81
List Price: $74.99
Save: $31.18 (41%)
Quantity
Almost Gone!
Only 2 at this price.

Select Conditions
  • Very Good $43.81 Domain-Driven Design: Tackling Complexity In The Heart Of Software
  • New $74.99 Domain-Driven Design: Tackling Complexity In The Heart Of Software

Frequently Asked Questions About Domain-Driven Design: Tackling Complexity In The Heart Of Software

Book Reviews (12)

5
  |   12  reviews
Did you read Domain-Driven Design: Tackling Complexity In The Heart Of Software? Please provide your feedback and rating to help other readers.
Write Review
Captcha
5
   One of the best software books I've read
I read this book in its draft form on a cross-country flight and was just blown away by it, so I bought a bound version to make it easier to carry and read. I think what blew me away was that Evans crystallized and laid quite clearly about a dozen ideas that existed at the edge of my consciousness, but which I could not verbalize clearly. It fits quite nicely between the patterns books and the process books, but is not a cookbook and is not strictly a method book. It is a must read for the multitude of JavaC#C++ developers who continue to write procedural code while claiming that they are OO developers because they use an OO language and they have read design patterns.
 
2
   Too much theory, less practical
I bought this book with expectations of building a domain layer in a better way, but could not apply the theory mentioned in this book. I tried to read more and more, but could hardly think about implementing the concepts discussed in the book. The concepts that the author tries to explain are great, but i think they are not very well presented. I stick to books like Head First OOA or Fowler's Domain Analysis Patterns.
 
4
   Perfect content - but too long for many readers
In domain-driven design, Evans describes a set of patterns that capture exactly what MDA and AOP attempt to be a solution. The approach of Evans is realistic, yet elegant. Unlike other model-focused approaches, he has a good focus on lessons learned from extreme software development, such as agile programming, and explains how domain modeling fits with testing-driven development, iterative and incremental development, and refactoring. However, I have a big gripe with this book. If the book had a thinner companion version or a reading guide for people who were in a rush during the introduction, it would be perfect. As it is, I can not recommend it to coders or business analysts, only to software architects and modelers.
 
3
   Repetitive and too long, but a must.
Have to admit right from the start, i'm only about 13. What I saw so far, however, is 1) Lots of repetition of previously made points. 2) Failing to engage you will need all the concentration you can muster, which is constantly frustrating combined with. 3) As peculiar as it may sound quite Java-oriented. Others may argue with that, but is not practical in lots of other environments. As someone pointed out in Fowler's Enterprise Patterns review, frameworks place restrictions on what patterns you can use if you force your way. And this book is about the process and patterns. Revised : I have had time to see how little some experienced developers, architects and business analysts value domain modeling and the development process. The writing of the book may be imperfective, but the material is essential.
 
4
   Changes the way you view software
Not for the feint of heart, not for people who just want a paycheck. This book is for thoughtful engineers who care about their craft and are willing to step up to the plate and make significant changes in the way they think about software. I particularly like the emphasis on progressive improvements ''. In today's world, everything just doesn 't work. Evens outlines ways to make software expressive and supple gradually more dimensional and therefore easier to work with and enhance.
 
5
   Excellent Book
I loved reading the book, and I would recommend it to all serious software architects. The book introduces the practical aspects of OO techniques as they apply to real world applications. It goes beyond the identifying the words and nouns - approach of identifying objects and methods into entities, value objects and aggregates. I also found the book to have a very refreshing approach to XP methods and the tight interdependence between modeling and design.
 
5
   Inspiring, necessary, must-read
This is a book describing a software design technique that I am currently a deep fan of. Regardless of the application development method you will be a follower of, Domain Driven Design is a must-read book for any programmer.
 
4
   A must read book for an inspiring architect
A business formalisation of the methodology and patterns of good software architecture. It is going to be interesting to people who start their careers in large scale business software development. It will not be a revelation to a veteran. However, great work is done!
 
5
   Fantastic book
Regardless of the domain or discipline, a must-read for software developers and architects. Every day I use the concepts in this book.
 
4
   Very important book
Not just software, but something else as well. Lots of content on how to organise teams around business value and how this reflects in the design of your system. The only thing that keeps me from being a fiveth star is that in certain areas it can be a very dry book. There could also have been more code samples and less UML and walls of pure text. Most important contexts are limited by this book, and the most bounded concept is taken from it. If you're on the fenceline, check out the talks of Eric Evans on YouTube.
 
12