This book is Eric Evans's own dictionary-style reference to Domain-Driven Design - Coping with Complexity at the Core of Software, which can be used to quickly find many of the concepts in Domain-Driven Design and their concise explanations.
There are more and more people who know about DDD so far. It happened that I found this dusty electronic version in my book list today. I checked the Internet and no one came to translate it, so I plan to publish this book in the near future. Translate it, and exercise your poor English level. If you have any mistakes, please point them out in time. >_<||| The content is not much, it is more than 50 pages, I will send it one chapter at a time, so stay tuned. Since the first chapter is mainly about some thanks and so on, this time I will send two chapters together (Portal: [translation] Domain Driven Design Reference (2) - making the model work ). If you want to read the original version, you can privately send me your email address, and I will send it to you. Well, let's start with "Acknowledgments":
Thanks
It has been more than 10 years since my book Domain-‐Driven Design, Tackling Complexity in the Heart of Software (or "The Big Blue Book", as some people call it) was published. During this period, the fundamentals discussed in the book haven't changed much, but a lot has changed about how we build software. DDD remains relevant because smart and innovative people are constantly changing it. I want to thank those people.
Let me start with Greg Young, Udi Dahan and people inspired by them at CQRS, Event Sourcing. These are the mainstream architectural options for DDD systems today. This was the first successful major development derived from the limited perspective architecture of the early 2000s.
Since then, many interesting techniques and frameworks have emerged with varying degrees of success aimed at making DDD more accessible (and other goals of their designers). Including Qi4J, Naked Objects, Roo and more. Such attempts are of great value, if not widely adopted.
I still want to thank the people and communities who have transformed our technology ecosystem and made DDD more interesting and useful. Most of these people have little interest in DDD, but their work has benefited us immensely. I especially think about the freedom NoSQL gives us, the reduction of syntactic noise from new programming languages (some features), and the relentless effort towards lighter technical frameworks and non-intrusive, decoupled class libraries. The technology of 10 years ago was complex and cumbersome, making it difficult to use DDD. Of course there are bad new technologies, but the trend is good. So I'm especially grateful to everyone who has contributed to this trend, even though you've probably never heard of DDD.
Next, I want to thank those who wrote books on DDD. The first book about DDD after me was from Jimmy Nilsson [ 1, and the additional supplement is this "Applying domain-driven design and patterns "]. If you have a book, you just "have a book". But with 2, you have a theme. Next, InfoQ released "DDD Quickly", which made many people aware of the topic for the first time due to its simplicity, free download and the influence of InfoQ. Over the years, there are still many valuable blog posts and other short articles. There are also special books, such as "DDD with Naked Objects" [ 2, additionally add that the book with the same name in the text cannot be found, guess it may be this "Domain-Driven Design Using Naked Objects" ]. In addition I would especially like to thank the indispensable Martin Fowler, who in addition to often providing authoritative documentation on emerging patterns also helps to clearly convey the concept of DDD. Just last year, Vaughn Vernon published the most ambitious book I've ever published, Implementing Domain-‐Driven Design (some seem to call it the "big red book").
I feel a sense of desperation that I will be throwing away so many people who have contributed so much, and I really regret that. Let me at least give thanks to those who pushed DDD into the public eye and those who pushed DDD into quieter corners of the organization. A software philosophy needs thousands of followers to make an impact.
Although this is the first printing edition of DDD Reference, it is the original look of my book published in 2004. Following a suggestion from Ralph Johnson, I extracted brief summaries of each pattern and used them in the workshop, with each pattern read aloud by attendees, followed by a discussion. I have used these files for training courses for several years.
Then, a few years after my book was published, Ward Cunningham, presented some of his work in the Repository schema to several authors, and we added a short summary of our schema to Creative Commons [ 3, a Creative Commons organization, see https://baike.baidu.com/item/creative%20commons/8755425?fr=aladdin ]. Martin Fowler and I did this under an agreement with the publisher Pearson Education, which opened up the possibility of this kind of derivative work.
definition
Domain: A range of knowledge, influence, or role. The subject area to which the user applies a program is the domain of the software.
Model: An abstract system that describes specified aspects of a domain and can be used to solve problems related to that domain.
ubiquitous language: A language built around a domain model that all team members can use in a defined context to connect all of the team's activities.
Context: determines the context in which a word or sentence appears to represent the meaning. The life of a model can only be understood in context.
Bounded context: Describes the boundaries within which a particular model is defined and applicable (usually a subsystem, or the work of a particular team).
Mode preview overview
Author: Zachary_Fan
Source: http://www.cnblogs.com/Zachary-Fan/p/DDDReference1.html
If you want to get the news push of personal self-written articles in time, please scan the QR code below~.
