
Domain-Driven Design
Eric Evans · 2003
Programming and computer science › Software design and clean code
#146 most recommended
Hacker News
252
mentions by 191 people · top 1.0% of 15,732 books
Open Library
4.25★★★★★★★★★★
8 ratings · 103 want to read
Wikipedia
—
No article yet
About the book
Domain-Driven Design is a approach to building software for complex business problems, centred on the domain the software serves rather than on technical infrastructure. It covers modelling techniques such as entities, value objects, aggregates, repositories and services, along with strategic design for large systems, including bounded contexts, context maps and the reshaping of legacy code. Its audience is mainly software developers and architects working in object-oriented languages. The central claim is that the hardest part of complex software is understanding the domain, so design should be organised around a model that developers and domain experts build together. That model should be expressed in a ubiquitous language used consistently in conversation, diagrams and code, so that the code itself reflects what the business means. Because understanding deepens over time, the model must be refactored continually and kept aligned with the implementation rather than fixed at the start. Large systems should be divided into bounded contexts with explicit boundaries and relationships, instead of forcing one unified model across the whole organisation.
Written by Claude from what it knows of this book.
What Hacker News says 54% recommend · 5% critical
In the commenters’ own words
Hello, Apart from my family and some minor health issues, I currently am focused on 2 things: learning Luxembourgish/Luxembourgian and develop a deep…
> Yes, for the organization. However when the organization is larger, this may not be a disadvantage - if the teams are already as large as small startups…
What Open Library readers say 4.25 from 8 ratings
- 54
- 42
- 32
- 20
- 10
- 103 want to read
- 3 reading
- 14 have read
Only 8 ratings: treat the average as a hint.
What critics say, via Wikipedia
No Wikipedia article about this book yet, so no critics to quote.
Reddit communities — coming later
The threads it came up in
- Ask HN: Books you plan to read in 2020?
- Ask HN: Which book are you reading these days?
- Ask HN: What language-agnostic programming books should I read?
- Ask HN: What books do you keep on your desk?
- Ask HN: Book Recommendations?
- Ask HN: What three books impacted your career the most?
- Ask HN: What are the most fundamental books on computer science?
- Ask HN: What books had the greatest effect on how you structure your code?
Details
- First published
- 2003
- ISBN
- 9780321125217
- Editions known
- 2 at Open Library
- Open Library
- OL4464385W
005.1Computer softwareComputer software, developmentComputer software--developmentDevelopmentObject-oriented programming (Computer science)Qa76.76.d47 e82 2004
Read next: its neighbours on the mosaic
Clean CodeRobert C. Martin · 2008 · recommended by 298 people · 25 people recommended both
Clean ArchitectureRobert C. Martin · 2017 · recommended by 47 people · 7 people recommended both
Patterns of Enterprise Application ArchitectureMartin Fowler · 2002 · recommended by 34 people · 8 people recommended both
Growing object-oriented software, guided by testsSteve Freeman · 2010 · recommended by 43 people · 7 people recommended both
Domain Modeling Made FunctionalScott Wlaschin · 2018 · recommended by 43 people · 6 people recommended both
Extreme programming explainedKent Beck · 1999 · recommended by 23 people · 5 people recommended both
Code CompleteSteve McConnell · 1993 · recommended by 393 people · 15 people recommended both
Working effectively with legacy codeMichael C. Feathers · 2004 · recommended by 186 people · 14 people recommended both
Head First design patternsEric Freeman · 2004 · recommended by 65 people · 6 people recommended both
Refactoring to PatternsJoshua Kerievsky · 2004 · recommended by 15 people · 4 people recommended both
The Pragmatic ProgrammerAndy Hunt · 1999 · recommended by 353 people · 13 people recommended both
Design PatternsErich Gamma · 1994 · recommended by 95 people · 5 people recommended both
Designing Data-Intensive ApplicationsMartin Kleppmann · 2017 · recommended by 457 people · 9 people recommended both
Test-driven developmentKent Beck · 2002 · recommended by 30 people · 3 people recommended both
The clean coderRobert C. Martin · 2011 · recommended by 53 people · 3 people recommended both
RefactoringMartin Fowler · 1999 · recommended by 94 people · 2 people recommended both
Java Concurrency in PracticeBrian Goetz · 2006 · recommended by 53 people · 5 people recommended both
A Philosophy of Software DesignJohn K. Ousterhout · 2018 · recommended by 163 people · 6 people recommended both
The Mythical Man-MonthFrederick P. Brooks · 1975 · recommended by 383 people · 10 people recommended both
Domain-Driven Design QuicklyAbel Avram · 2006 · recommended by 5 people · 2 people recommended both
Planning extreme programmingKent Beck · 2000 · recommended by 2 people · similar by subject and what people say about it
Continuous DeliveryJez Humble · 2010 · recommended by 16 people · 3 people recommended both
Smalltalk best practice patternsKent Beck · 1997 · recommended by 17 people · 2 people recommended both
Lean Software DevelopmentMary Poppendieck · 2003 · recommended by 6 people · 3 people recommended both