All geek questions in one place

In Azure Service Fabric, what is the reverence between the stateless API and the ASP.NET Core API?

I didn’t dig it, but what are the pros and cons of both. They seem to be redundant, obviously the Core version is experimental and probably won't work with many major libraries like Odata and Entity Framework

+4
source share
2 answers

tl / dr: Stateless Web API is the older "classic" web API. ASP.NET Core is the new material in which all the new features come.

More details:

The idle user API template:

  • The "classic" OWIN-based ASP.NET Web API 2. It does not support MVC (without rendering on the server side of Razor).
  • .NET Framework.
  • "" .NET(.csproj) Visual Studio 2015.
  • Katana -, System.Net.HttpListener, API HTTP HTTP Server ( http.sys).

ASP.NET Core:

  • ​​ASP.NET, MVC Web API Razor ASP.NET.
  • .NET Framework .NET Core, .NET Framework Service Fabric.
  • .NET(.xproj) Visual Studio 2015. VS 2015 " " . "" Visual Studio 2017 ( .csproj). , VS 2015.
  • - WebListener Kestrel.
    • WebListener http.sys .
    • Kestrel (libuv), , , DoS.
+6

, ASP.NET Core Web API .NET Core. Stateless, ServiceManifests, ETW, .

API - ASP.NET HTTP-, Microsoft.AspNetCore.Hosting.IWebHost WebListenerCommunicationListener Microsoft.ServiceFabric.AspNetCore.WebListener ( ASP.NET Core host. ASP.NET ASP MVC.

API Stateless HTTP-, Microsoft.Owin.Hosting.WebApp OwinCommunicationListener, .

, Service Fabric , , , . , , , NuGets PackageRoot .

, .NET Core .

+2

Source: https://habr.com/ru/post/1667696/

More articles:


All Articles