"Selfless sharing: ASP. NET CORE Project Combat (Chapter III)" Application of domain driven design under EntityFramework

Catalog Index

"Selfless sharing: ASP. NET CORE Project Combat" Catalog Index

Brief introduction

In our "selfless sharing: from beginner to proficient in ASP. NET MVC" series, we actually have ddd thinking, but not completely to achieve, because not all the good things must be used, or according to the actual situation, DDD in the large system is a very good design idea, This is not to be denied. But depending on the situation, in our small project, our design framework is more about enabling users to develop quickly and easily, and to quickly understand the framework for project development.

Reconstruct our ideas.

Recently studied the blogs of several great gods, in particular: a tentative study of the realm-driven design (1) for complex business and @dax. NET EntityFramework domain-driven design practice (i)

Let me re-understand the DDD, for this design idea, to tell the truth, I am still relatively unfamiliar, is a beginner, according to some of their own understanding, I compared a brief discussion of the field-driven design (1) The invocation relationship of the sample code for the complex business:

Previous Call Relationship: interface Implementation class inherits warehousing repositorybase<t> realize business operation and data operation, the way to operate is to invoke interface method to implement operation

Takeoff (Jesse) research on domain-driven design (1) A call relationship for the sample code in a complex business: The domain layer invokes the warehousing irepository<t> for business operations and data operations, and then his interface implements the class, which looks like a "relay", and the way to do it is Call the interface method interface method and call the domain layer method to implement the operation

It seems to be more than mine. A "transit layer", our interface as a transit, the domain layer inherits the warehousing to achieve business and data operations, what is the practical significance? I hope you will correct me:

I do not understand is that if it is in accordance with this, then I would like to modify the registration method, such as I want to pass the Eamil,name,password in the above method also need to pass the mobile phone number, then I need to modify the "three" places, one is the application layer interface Iuserservice Register parameters, one is the application Layer implementation Class UserService register parameters, and the domain layer of register parameters and method body; In my previous code, only the parameters of the register of the interface Iusermanage need to be modified and the parameters and method body of the Register that implements the class Usermanage can be.

I want to learn from you. ASP.

Just beginning to contact, the level is limited, a lot of things are their own understanding and flipping through the online god of information, if there are wrong places and do not understand the place, I hope you correct!

Although ASP. NET Core is now very hot, but many of the online information is the copy of the previous article, so there are a lot of problems I have not resolved, I hope we can help together!

Selfless sharing: ASP. NET CORE Project Combat (Chapter III) "Application of domain driven design under entityframework"