Is Owin / Katana supposed to replace the Web API?

Question

When ASP.NET MVC appeared, Microsoft has repeatedly stated in many places that it should not replace ASP.NET web forms. In other words, this is just another technology that you may find useful, or you can use web forms in other scenarios.

However, as companies enter the market, they cannot have the jungle of technology because it is too expensive. They usually choose mature technology, stick to it, build on it and expand it and reuse elements in it to reduce costs.

Now we are trying to move to Owin / Katana from the Web API. We just wonder if we are moving 100% to Ovin normally?

The reason I ask this question is because we have created a very rich code base for web APIs, including streaming, compression, authentication, UGC normalization, support for I18N and L10N, etc.

If we want to switch to Owin, we need to create these objects / utilities for Owin again, because its architecture is different from the web API.

We want to switch to Owin because it is a faster, easier, self-service server, and it looks like Microsoft's future service technology.

Is it safe for us to completely switch to Owin and imagine a future in which all our services are delivered through Owin and we stop using the web API?

Answer 1

OWIN - , . , , , .

ASP.NET IIS. Katana , . , Katana, ASP.NET(Core.NET).

OWIN, HTTP ( ). , , .

: OWIN, , ASP.NET.

ASP.NET Core - ASP.NET -API. , : , . , ASP.NET.