Struggling with migrating from your old ASP.NET application to .NET Core and don’t know how to have a smooth migration without having one day shutdown?

YARP -which stands for Yet Another Reverse Proxy – is a super-smart traffic director for a website or app.

Imagine you’re at a huge school with two cafeterias: an old one with junk food and a new one with healthy cuisines. In fact, the school wants to slowly switch everyone to the new and modern cafeteria without closing the fast-food one right away. YARP is like the person at the front door who says, “Okay, if you want pizza, go left to the old cafeteria. If you have health diet, go right to the new one.” This way, everyone gets their food without having one day off in the campus’s restaurant and overhead to the new section, even while the school is changing things.

In your web app project, YARP helps your old app (the pizza cafeteria) and your new .NET Core app (the brand-new one) work together. When someone visits your website, YARP figures out which part of the app they need and send them to the right place. This lets you move your app to .NET Core bit by bit, without breaking anything for your users.

YARP isn’t just for migrating legacy modules—it’s a general-purpose reverse proxy used for traffic management (load balancing, routing, A/B testing), security, transformations, and more.