![]() Normal applications follow the following architecture. Thinking of domain driven design over Normal Layered Architecture Object should be named a Customer in code - it should have the same rules as aĬustomer does in the real world or as close as it is possible. It is addressing either in the physical or real world. It means eachĭomain class should have a direct relation to what it represents in the businessĭomain. So what we follow is that the customer discuss each business case in business meetings.ĭomain driven design purely based on these assumptions to map the businessĭomain Driven Design is all about how you model your Domain. Your prime goal is to understand all the terms of business that customer uses and how he/she models the requirement domain. We are about to start to write a system, here we first try to understand exactly what customer is looking for, what business they are going to do with the More into the business need not focusing on the technology. Similarly domain driven design is something which focuses ![]() So here domain means the business knowledge about that We have heard of different domains such as Banking, Telecom, Supply chain, health care, etc. Domain Driven Design is all about understanding the customer real business need.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |