Clever Geek Handbook

Using WebListener or OWIN as API Gateway for Azure Service

We have 4 stateless service microservices in service fabrics that use Kestrel as a server. We need to expose these 4 front-end services and ask a question about using WebListener or OWIN as server. Can anyone tell what is best for performance. And also we have an authentication service that is used to process tokens.

+1


source to share


1 answer


From OWIN I am assuming you are referencing Katana using Web API 2, which both implement OWIN.

In this case, the choice really lies between the "classic" Web API 2 with Katana and the new ASP.NET core with WebListener. I always recommend ASP.NET Core with WebListener for several reasons:



  • We have official NuGet package integration for ASP.NET core in Fabric service
  • These packages and their use cases are documented
  • Katana was pretty much the prototype of what will become ASP.NET Core. Most, if not all, of the new feature runs in ASP.NET Core, not Katana, and ASP.NET Core is officially supported by Microsoft.
+3


source






More articles:


All Articles