Why this book?
This book has foundational to me. I discovered it after a few years in my professional career, and it shaped my way of thinking about software and my relationship with teams and the environment. Eric distilled different patterns that helped the software community to find boundaries for the software, and I recommend it to anyone in the software industry. By discovering and setting the boundaries for the software, teams can be more effective, and software can be more efficient. “Making the implicit explicit” is the mantra of the DDD community!
Domain-Driven Design: Tackling Complexity in the Heart of Software
Why should I read it?
2 authors picked Domain-Driven Design as one of their favorite books, and they share why you should read it.
What is this book about?
Incorporate effective domain modeling into the software development process
Software design thought leader and founder of Domain Language, Eric Evans, provides a systematic approach to domain-driven design, presenting an extensive set of design best practices, experience-based techniques, and fundamental principles that facilitate the development of software projects facing complex domains. Intertwining system design and development practice, this book incorporates numerous examples based on actual projects to illustrate the application of domain-driven design to real-world software modeling and development.Domain Model: Part I outlines the goals of domain-driven development, defines terms, and gives an overview of the implications of using the…
- Coming soon!