0

We have a big ASP.NET Framework application hosted in IIS and we are considering a progressive migration to ASP.NET Core using YARP, as explained here: https://devblogs.microsoft.com/dotnet/incremental-asp-net-to-asp-net-core-migration/

The basic idea is to deploy a ASP.NET Core app that will proxy all the requests to the old application, and then move the code progressively from the legacy app to the proxy, until the legacy app is empty and can be removed.

We are wondering about the hosting of the ASP.NET Core proxy app. In priciple there is no limitation, it could be deployed in IIS alongside with the legacy app or be deployed with Docker/Kubernetes. However, we don't know if that second option will cause a performance penalty or any other kind of problem. So before doing a POC, we'd like to ask if somebody has experience with this problem and some advice about it.

Tao Gómez Gil
  • 2,228
  • 20
  • 36
  • The YARP proxy is work as url rewrite which will rewrite the request to the ASP.NET Framework application. This means the Docker/Kubernetes will serve as the server and client. This means it may face some latency issue if there is network issue between the Docker/Kubernetes and ASP.NET IIS server. – Brando Zhang Feb 03 '23 at 02:33

0 Answers0