design patterns - Differentiating between domain, model, and entity with respect to MVC -
Can anyone explain these 3 concepts and the difference between them in relation to an MVC framework with these examples? For me this looks almost equal, and it seems that they are used in some articles for each other and not in others.
The words are a bit unclear. I will use the domain to reference the business area that you are working on. You do not have a domain model like banking or insurance or after that you have these things that you deal with in that business domain, such as banking, domain for you account, customer, transfer etc. Are there. I refer to the class unit POJO or the prevailing / concrete version of a model. Are you confused here that in the MVC word, model is a solid thing, but it is a web GUI to represent some presentation Refers to the data model used for it, so do not mix with the above explanations.
Comments
Post a Comment