Table of Contents
Book Reviews Tech - This article is part of a series.
In today’s post, we’re going to be diving into a review of Eric Evans’ Domain-Driven Design (DDD), a cornerstone text in the field of software architecture. This book, a hefty 500-page tome, is an essential read for software developers, from the novice to the veteran.
At its core, Domain-Driven Design is a book about designing systems correctly the first time (or at least trying to). Evans skillfully uses Domain Modeling to guide the rules and understanding of a domain’s space, sharing precious insights about software architecture, system design, and design patterns.
The text draws from Evans’ more than two decades of experience building large-scale systems. Throughout the book, he uses a single Logistics and Freight Shipping example to illustrate each newly introduced concept, demonstrating how an application’s architecture evolves from something primitive to something sophisticated and extensible.
Key Points #
One of the standout elements of this book is Evans’ introduction of three key concepts: Entity Objects, Value Objects, and Aggregates. He meticulously details how any data object you deal with can be categorized into one of these three categories. Furthermore, Evans introduces a concept he terms Bounded Contexts, which encourages architects to draw conceptual boundaries across domains and group entities and behaviors within them.
Here are a few takeaways:
- Entity Objects have an ID and are trackable through time, while Value Objects do not.
- It’s essential to discuss your system and use cases with Product Managers, Engineers, Managers, and others to develop your Ubiquitous Language.
- The Ubiquitous Language evolves over time. Don’t be afraid to revisit your models and refactor when better fitting models are discovered.
- Carve out the responsibility of your system, preferably using a Service Oriented Architecture (SOA) in large scale systems.
Despite its in-depth coverage, Domain-Driven Design is not without flaws. The book’s dense language and tendency towards redundancy may prove challenging for some readers. It reads more like a college textbook (in fact, it probably is at some schools), which may be off-putting for those seeking a more casual read.
Rating and Recommendation #
Overall, Domain-Driven Design receives high praise. Despite its dense language, the practical tips and insights it provides make it an essential read for software developers of all experience levels. It’s especially beneficial for those who want to build their systems as ‘right’ as possible the first time around. It’s a must-have for any software developer’s library, but particularly for those involved in large-scale systems design.
Additional Reads #
If you enjoyed Domain-Driven Design, here are a few additional reads that might pique your interest:
- Applying Domain-Driven Design And Patterns: With Examples in C# and .NET is an excellent choice for C# and .NET developers. It explores three ways architects and developers can create robust and maintainable systems: patterns, domain-driven design, and test-driven development.
- Practical Domain-Driven Design in Enterprise Java is a hands-on book ideal for Java programmers. It implements domain-driven design in Java, and you’ll immediately start working on a project, even building a cargo tracking reference application using the Jakarta EE platform.
Domain-Driven Design by Eric Evans is a classic in the field of software architecture. Despite its dense language, it provides valuable insights into designing systems, making it a must-read for any software developer. If you’re interested in understanding domain-driven design better, this book should undoubtedly be on your reading list.
- Review of Domain-Driven Design by Eric Evans: Be a Better Dev
- Applying Domain-Driven Design And Patterns: With Examples in C# and .NET: Amazon
- Practical Domain-Driven Design in Enterprise Java: Amazon