ASP.NET MVC

In the past decade, the most common architectural pattern used to build web applications is the n-tier architectural pattern. n-tier patterns mainly consists of a presentation tier which contains the interface code, the business logic tier that focuses on the core logic of the client and the data access tier that is responsible for retrieving and storing data to the backend.

One of the main common problems I have faced when dealing with n-tier architectural patterns is having the business logic and data access tiers pushed towards the user interface tier until it is impossible to revert the code done. When working with ASP.NET forms one has to learn to be disciplined in coding. Common issues like SQL queries are not hardcoded as strings in the data layer.

Lately I have been reading and trying an alternative architecture which is gaining popularity. This architecture is known as MVC (Model-View-Controller). This pattern helps to encourage the splitting of components into their respective tiers. i.e. (application control, business logic and User Interface).

Around 2 weeks ago at the MIX conference, Microsoft released ASP.NET MVC 1.0. It is a completely free product which enables developers to code web applications using model view controller pattern. It also has full control over HTML markup and URL structure. It helps the test driven development.

I will post more details about the ASP.NET MVC architecture with more examples. In the meantime you can find a lot of useful resources in the ASP.NET Official site by going in the ASP.NET MVC section