Architectually, do you need a n-tier ASP.net MVC web server when you have a separate n-tier business server to connect to for logic processing?
Is there any other reasons to use the n-tier architecture for the web server besides separation of business logic? Would it make sense for the data layer to be handled by the business server also?
To me it seems like the web server has no need for the n-tier?
As far as I know there is no application that can not fit into 1-tier. So in theory You do not need multi-tier everywhere.
From MSDN:
Decide if you need a separate business layer. It is always a good idea to use a separate business layer where possible to improve the maintainability of your application. The exception may be applications that have few or no business rules (other than data validation).
You may have different reasons to add extra layer and that may be for example:
All depends on specific needs. So You need to know Your trade offs.
Also good to know from MSDN:
A layer is a logical structuring mechanism for the elements that make up your software solution; a tier is a physical structuring mechanism for the system infrastructure.
