Fields-driven design Lite version

I often see someArticleWe mentioned "domain-driven design ". Domain, drive, design, just three words, it sounds mysterious, and each word has enough weight to install B ....

I didn't care much at the beginning until one day I suddenly realized that I had a field-driven design shadow on my own projects. As a result, I came up with an idea of deep understanding. I read many articles in the garden, but I can see what is a domain-driven design in the fog of the cloud. There is still no clear concept in my mind.

Yesterday, I downloaded a book titled "Domain-driven design Lite version", which contains about 80 pages. I want to satisfy my understanding of the concept.

After reading the book, I seem to know something about it, but I still don't understand it. It seems that I am not competent enough to explore it in the future. Of course, write down some of your current understandings for future reference...

 

What is domain-driven design?

In my initial understanding, I thought it wasCode. Similar to the classic three-tier architecture. In fact, I also discovered that I used domain-driven design in my current development project through the Code architecture and some key terms. In fact, according to the content in the book and my previous articles, the layered architecture of code is indeed part of the domain-driven design, but not all. Domain-driven design provides a systematic requirement analysis and modeling method. What is "domain "? According to the book, it should be understood as the business field. Then, the "get drive design" can be translated as: driving your design through the business field.