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

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…