Different people use these terms in somewhat different ways, but here’s my take: 1) “Business” and “domain” are roughly synonyms. “Domain” is a bit more general in that it doesn’t make the assumption that you’re writing a business application. So if we were writing a scientific app or a game, we might prefer to refer … Read more
It is all about decoupling your app into self contained pieces, each one defined by the requirement to do one job really well. This allows you to apply specialised design patterns and best practices to each component. For example, the business layer’s job is to implement the business logic. Full stop. Exposing an API designed … Read more
The way I have done it – and I’m not saying it is right or wrong, is to have my View and then a model that applies to my view. This model only has what is relevant to my view – including data annotations and validation rules. The controller only houses logic for building the … Read more
It seems like you are asking about the difference between the data model and the domain model – the latter is where you can find the business logic and entities as perceived by your end user, the former is where you actually store your data. Furthermore, I’ve interpreted the 3rd part of your question as: how … Read more