Spring microservices in depth using domain driven design
![spring microservices in depth using domain driven design spring microservices in depth using domain driven design](https://techdozo.dev/wp-content/uploads/2021/08/image-5-1024x616.png)
- #Spring microservices in depth using domain driven design how to#
- #Spring microservices in depth using domain driven design software#
More students say, “look at the code directly, don’t look at their PPT and documents, you will be misled, otherwise you won’t know how to die”. This is also when some documents are imperfect. It would be better if there were unit test and code review. Even if it is written by different developers, considering the compliance with design pattern, naming conventions, development language constraints, etc., the code is basically the same and easy to understand. We all know that the code can reflect the real situation when expressing some business or logic. I’m not saying that giving play to sexual thinking is not allowed, but from the perspective of preaching, it is still necessary to respect theory and facts. At the same time, how do I know that my DDD is relatively orthodox and has not been misguided by others.
Which design expression is better and easier to understand. So do we want to accept the fact that “each author’s interpretation of DDD may not be the same” and “DDD design documents may be presented in different forms”? If so, students who want to learn DDD will have a great burden. Such a simple MVC architecture can have different architecture design documents, and DDD is relatively more abstract and difficult to understand, so the length of architecture design documents is different, which is understandable. The design documents written by different students were also very different. It was based on the MVC framework struts 1. I remember that there were not so many middleware at the beginning. Of course, you said I was old and conservative. Even if the two students know DDD very well and have practiced several projects for several years, they still write different things. We should not use the concept of blind people touching elephants for analogy. Are these DDD designs? In fact, there is a problem here, that is, when describing some abstract concepts through words and diagrams, there will be great differences. If you open several DDD articles on the Internet, although each author says he carries out architecture design according to DDD ideas, careful students will find that the structure description and architecture drawings in each author’s DDD articles are very different.
#Spring microservices in depth using domain driven design software#
Everyone wants to master good design methods to solve problems in software development. There are many articles about DDD on the Internet, which is of course a good thing. So which design method is better? How do you know which DDD is more orthodox and not distorted by others? This paper attempts to use the concept of “DDD as code“, that is, use DSL code to describe DDD, unify the design idea of DDD, introduce in detail how to complete the expression of a project based on DDD DSL based on contextmapper through a case, and share the relationship between DDD design process and micro service in reality. Introduction:Compared with the conventional MVC architecture, DDD is more abstract and difficult to understand, and various developers have different interpretations of DDD.