![]() As you can see in Figure 7-10, in the ordering domain model there are two aggregates, the order aggregate and the buyer aggregate. You might find that a different folder organization more clearly communicates the design choices made for your application. The folder organization used for the eShopOnContainers reference application demonstrates the DDD model for the application. ![]() You should not have hard dependencies or references to EF Core or any other ORM in your domain model. ![]() It will have just the EF Core model requirements, but not real dependencies on EF. Your domain model will be composed simply of your code. Now it is time to explore possible ways to implement the domain model by using. In the previous section, the fundamental design principles and patterns for designing a domain model were explained.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |