Search code examples
owinazure-service-fabrickestrel-http-serverweblistener

Using WebListener or OWIN as API Gateway for azure service fabric

We have 4 stateless services microservice in service fabrics which are using Kestrel as server. We need to expose those 4 services to the front end and have question regarding either to use WebListener or OWIN as server. Can any one tell which is better for performance. And also we have authentication service which is used to handle tokens.

Solution

  • By OWIN I'm assuming you're referring to Katana with Web API 2, which both implement OWIN.

    In that case, the choice is really between "classic" Web API 2 with Katana and the newer ASP.NET Core with WebListener. I always recommend ASP.NET Core with WebListener for a few reasons:

    • We have official integration NuGet packages for ASP.NET Core in Service Fabric
    • These packages and their use cases are documented
    • Katana was largely a prototype for what would become ASP.NET Core. Most, if not all, new feature work is going into ASP.NET Core, not Katana, and ASP.NET Core is officially supported by Microsoft.