"Eric Evans has written a fantastic book on how you can make the design of your software match your mental model of the problem domain you are addressing. "His book is very compatible with XP. It is not about drawing pictures of a domain; it is about how you think of it, the language you use to talk about it, and how you organize your software to reflect your improving understanding of it. Eric thinks that learning about your problem domain is as likely to happen at the end of your project as at the beginning, and so refactoring is a big part of his technique. "The book is a fun read. Eric has lots of interesting stories, and he has a way with words. I see this book as essential reading for software developers-it is a future classic." -Ralph Johnson, author of Design Patterns "If you don't think you are getting value from your investment in object-oriented programming, this book will tell you what you've forgotten to do. "Eric Evans convincingly argues for the importance of domain modeling as the central focus of development and provides a solid framework and set of techniques for accomplishing it. This is timeless wisdom, and will hold up long after the methodologies du jour have gone out of fashion." -Dave Collins, author of Designing Object-Oriented User Interfaces "Eric weaves real-world experience modeling-and building-business applications into a practical, useful book. Written from the perspective of a trusted practitioner, Eric's descriptions of ubiquitous language, the benefits of sharing models with users, object life-cycle management, logical and physical application structuring, and the process and results of deep refactoring are major contributions to our field." -Luke Hohmann, author of Beyond Software Architecture "This book belongs on the shelf of every thoughtful software developer." -Kent Beck "What Eric has managed to capture is a part of the design process that experienced object designers have always used, but that we have been singularly unsuccessful as a group in conveying to the rest of the industry. We've given away bits and pieces of this knowledge...but we've never organized and systematized the principles of building domain logic. This book is important." -Kyle Brown, author of Enterprise Java(TM) Programming with IBM(r) WebSphere(r) The software development community widely acknowledges that domain modeling is central to software design. Through domain models, software developers are able to express rich functionality and translate it into a software implementation that truly serves the needs of its users. But despite its obvious importance, there are few practical resources that explain how to incorporate effective domain modeling into the software development process. Domain-Driven Design fills that need. This is not a book about specific technologies. It offers readers 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 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 development. Readers learn how to use a domain model to make a complex development effort more focused and dynamic. A core of best practices and standard patterns provides a common language for the development team. A shift in emphasis-refactoring not just the code but the model underlying the code-in combination with the frequent iterations of Agile development leads to deeper insight into domains and enhanced communication between domain expert and programmer. Domain-Driven Design then builds on this foundation, and addresses modeling and design for complex systems and larger organizations.Specific topics covered include: * Getting all team members to speak the same language * Connecting model and implementation more deeply * Sharpening key distinctions in a model * Managing the lifecycle of a domain object * Writing domain code that is safe to combine in elaborate ways * Making complex code obvious and predictable * Formulating a domain vision statement * Distilling the core of a complex domain * Digging out implicit concepts needed in the model * Applying analysis patterns * Relating design patterns to the model * Maintaining model integrity in a large system * Dealing with coexisting models on the same project * Organizing systems with large-scale structures * Recognizing and responding to modeling breakthroughs With this book in hand, object-oriented developers, system analysts, and designers will have the guidance they need to organize and focus their work, create rich and useful domain models, and leverage those models into quality, long-lasting software implementations.
在书中提到 value object 具有不变性和代数的计算封闭的性质。 在最近的几个开发项目中,大量地使用了 value object 。当使用 c/c++ 来开发的时候,使用 value object 可以减轻内存管理的负担。能带来这种便利的正是因为 value object 具有不变性。value object 一经构造就不...
评分软件最有价值部分是它的领域模型部分。软件开发应该围绕这个核心进行组织,这是领域驱动设计的核心理念。 这本书有价值的地方甚多,值得反复细细揣摩,书中最重要观点,摘录如下: 1.软件开发复杂性的根本原因是问题领域本身错综复杂,控制复杂性的关键是有一个好的领域模型...
评分我是一个所谓前端er,但我觉得对领域的概念对所谓的前端er们而言也非常重要。特别是中后台的业务前端在不需要实现界面操作的前提下,了解业务的实现非常重要。 这本书里讲了很多的"道",例如团队协作,开发人员对待需求的态度。 我觉得这本书适合想要了解业务实现的开发人员,...
评分刚开始是冲着这个书的副标题来的,软件核心复杂性应对之道,主标题并没有太在意。最后看了不到一半吧,零散着跳读的。翻译问题很大!!! 进书便开始和我说模型的事,又是分层又是画图,看了几章发现,弄了半天不就是一个UML图吗。 这书给我感觉是一本教 不懂业务只懂编程的程...
评分读了前面大半本,后面讲的太宏观了,暂时用不到,以后再读。
评分确实没看懂。。
评分第三次重读这本书. 写代码时很容易将实现细节与领域模型耦合在一起.因为这是最不需要思考的作法. 但是耦合在一起显然是有问题的, 包括维护理解, 及后续对新需求和演进的支持. 作者给出了一系列的方法和模式来分享给我们如何来保护领域模型的内聚与一致性. 起码让我们写出耦合代码后知道了往哪个方向改变是好的. 另外微服务的出现, DDD中的各种分BoundedContext, 分核心域和支撑域, 通用域以及分层思想, 按职责分层, 等大规模的组织方式. 给微服务的划分提供了相通的思路.
评分.
评分看了三分之一都不到,感觉能够收获的东东有限。
本站所有内容均为互联网搜索引擎提供的公开搜索信息,本站不存储任何数据与内容,任何内容与数据均与本站无关,如有需要请联系相关搜索引擎包括但不限于百度,google,bing,sogou 等
© 2025 book.quotespace.org All Rights Reserved. 小美书屋 版权所有