Skip to main content

OWIN and Katana

OWIN and Katana. This two words are now the buzz words in Web development over Microsoft technologies. I heard pretty often this two buzz words used, but without knowing very clear what is OWIN and what is Katana. The main scope of this post is to define this two new terms and determine when we should talk about OWN and when we should talk about Katana.
OWIN comes from Open Web Interface for .NET and is an abstraction level between our web application and .NET web server infrastructure. This mean that from now on we will be able to host our web applications on different web servers, not only on IIS.
Until now the only possibility to host a web application written in .NET was using IIS. OWIN is here to help us. Because OWN define the abstraction level between the web server and web application we can now start to develop owner own web servers or integrate it in existing one.
It is important to know that OWIN only defines the specification of this layer and not the real implementation. Based on this specification we can create and integrate a middleware layer between our web application and the request/response. For example in this way we can change the request before arriving to our web application without having to change our web application or create a custom component for IIS (creating a custom component for IIS is not wrong, but cannot be reused on other web servers).
Katana comes with the implementation of web server made by Microsoft. It represents only an implementation of OWIN that can be used to host our web application. I expect in the future to see different implementation of OWIN for Mono that will run on Linux system and why not on Android.
I think that most of us already saw the demo where using OWIN we were able to self-host a web application in a console application. Using Katana we can do a lot of crazy things and we will be able to create and deploy different tools and web application faster and easily and we don’t need IIS anymore to host web application.
This is great especially in the development and testing step, where managing 3-5 versions of the application could be pretty complicated.
Porting between different platforms is pretty cool for small and simple application. Think about the following scenario. We create a web application that can be used in our home to search pictures shared in our network. We will be able to develop in in .NET and hosting it on a Raspberry PI using Mono.
Another good example is related to Authentication, that can be done now very easily over OWIN. We can support now Facebook, Google and other providers extremely simple.
Why we should use Katana? Well, we don’t need. It is optionally, but using Katana we will have more flexibilities because of OWIN specification. Also, expect that in the future, to see and hear about Katana more and more often.
Now with OWIN we can:

In conclusion. OWIN is the abstraction level between our web application and web server. Katana is the implementation of OWIN made by Microsoft.


Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...