I've read so many articles about OWIN and Katana, and one of the benefits of using OWIN in ASP.NET application is that when building ASP.NET application, i'm inherently bound to IIS due to the heavy dependency on System.Web assembly. In other words, the System.Web assembly by the default run on every request.
Actually, i didn't get how does the System.Web runs on every request, thus consuming the resources and making ASP.NET applications in general lot slower. And how does the Middleware components solve this problem? does they don't depend on System.Web Assembly?
System.Web.dll
is not bound to IIS, it can run in other host-processes (such as Cassini, circa 2005). Also I feel you're overstating the performance impact of the ASP.NET pipeline. – Dai