The Model View Controller paradigm very nicely separates the web server layer into the different regions of responsibility. Unlike in ASP.NET Web Forms, the object model, controller logic and presentation don't get hopelessly mixed up.

Still, there is too much business logic in classic controllers for my taste. The web server should be there merely for presenting an already existing model, and for passing through commands to change that model to an existing application layer.

Thus, I am using ASP.NET MVC in combination with