Upgrade to Pro — share decks privately, control downloads, hide ads and more …

OWIN&Katana

 OWIN&Katana

How many web and application servers can you name that host .Net applications? How many web frameworks exist for building .Net applications? My bet is you can count either number on one hand. One of the goals of OWIN is to change that. We'll explore other goals of OWIN, the Katana library, and build a simple application that's portable across multiple application servers. I'll also show the power of middleware built for OWIN.

Dusty Burwell

August 13, 2013
Tweet

More Decks by Dusty Burwell

Other Decks in Programming

Transcript

  1. History Lesson: 2002 ASP.NET Released alongside .Net 1.0 Optimized for

    desktop LOB customers Designed to run on IIS with System.Web
  2. History Lesson: 2002 ASP.NET Released alongside .Net 1.0 Optimized for

    desktop LOB customers Designed to run on IIS with System.Web Tightly coupled to IIS
  3. History Lesson: 2009 ASP.NET MVC released Shipped out of band

    from .Net framework Still tightly coupled to System.Web, and therefore IIS
  4. History Lesson: 2012 Web API released No dependencies on System.Web

    Ability to “Self-Host” without IIS Can be hosted on OWIN compatible servers
  5. OWIN (Open Web Interface for .Net) Like Rack for Ruby

    Or WSGI for Python Or Connect for Node.js
  6. OWIN (Open Web Interface for .Net) Like Rack for Ruby

    Or WSGI for Python Or Java Servlet Specification for... Or Connect for Node.js
  7. OWIN A specification for hosting abstractions for .Net web applications.

    A standard interface between .Net web servers and web applications.
  8. decouple server and application GOALS: - Paraphrased from owin.org portability

    enabled by reducing the abstraction to as few primitives as possible
  9. decouple server and application, encourage simple modules GOALS: - Paraphrased

    from owin.org providing a programming model that enables the development of middleware
  10. decouple server and application, encourage simple modules, stimulate the open

    source ecosystem of .NET web development. GOALS: - Paraphrased from owin.org
  11. decouple server and application, encourage simple modules, stimulate the open

    source ecosystem of .NET web development. GOALS: - Paraphrased from owin.org *Important!