Some of the patterns and definitions have been edited or rewritten by Evans to clarify the original intent. The practice and understanding of DDD has not stood still over the past decade, and Evans has taken this chance to document some important refinements. In this reference, those original summaries have been updated and expanded with new content. The starting point of this text was a set of excerpts from the original book by Eric Evans, Domain-Driven-Design: Tackling Complexity in the Heart of Software, 2004 - in particular, the pattern summaries, which were placed in the Creative Commons by Evans and the publisher, Pearson Education. It is complementary to the more discursive books. On the other hand, we often need to scan a topic quickly or get the gist of a particular pattern. Eric Evans' original book and a handful of others explain DDD in depth from different perspectives. It is not meant as a learning introduction to the subject. This reference gives a quick and authoritative summary of the key concepts of DDD. Easier said than done! The techniques of DDD help us approach this systematically. DDD tackles that complexity by focusing the team's attention on knowledge of the domain, picking apart the most tricky, intricate problems with models, and shaping the software around those models. Domain Driven Design Reference Book Summary/Review:ĭomain-Driven Design (DDD) is an approach to software development for complex businesses and other domains.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |