Why Katana should be on your radar

Agility, flexibility and composition: Unlike traditional ASP.NET, Katana decouples components, which are independently updatable by NuGet. Rather being restricted to the functionality built into your server or framework, you can now compose together multiple middleware and frameworks to get only what you need. For example, Self-Hosting WebApi and SignalR in the same application, guarded by the same security middleware. Components can release independently, which means that it’s likely features and functionally would be changing more quickly. More frequent changes is not universally positive, more frequent changes could introduce more problems.

Portable: Your application can be portable across servers; IIS, HttpListener, or even something like NOwin (which uses raw sockets in lieu of HttpListener). Some of these may be available on Mono.

Footprint: Footprint is not directly related to Katana , but rather that Katana can be hosted without going through the normal ASP.NET (System.Web) request processing pipeline (which brings in the .Net System.Web and all its dependencies).

Tags

Join the conversation

What is the best practices for how many OWIN components to limit the number of points of failure for an application which needs to be in production for 6-8 years? It is to avoid components that stop being actively developed within 1-2 years after the initial production rollout of the application.