For clarity, when I mention layers in my question, I mean physical layers (i.e. different servers for presentation, application and database)
My company has a public site, which is currently built as a typical two-tier system (web server and database server).
A project will begin soon, in which we will rewrite the entire site. We must divide the project into three physical levels. In fact, when you are considering a browser, you can consider its 4 physical levels.
In my experience, most asp.net applications are built on two levels. The web application itself can have several levels, but physically it is deployed on two servers (web and database).
I searched for examples, but it seems that layers and levels are confused. I see many multi-level examples, but not multi-level examples.
In a nutshell, it seems like the web application is making a web service or WCF calls at the application level, which marching data to and from the database using ADO (or L2S or EF).
Does ASP.MVC help achieve this? Does it make it easier or just different?
Is there a good link or an example of this somewhere?
source
share