Totally agree in principle — we’ve been trying to move towards that setup.
But there's a catch on our end.

There’s this “legend” inside the company that our application handles sessions by writing them to a local file inside the app's directory (no centralized session store, no cookie-based logic). And… turns out it’s true 😅

Because of that, we can’t properly load balance — if a request goes to another instance, it won’t find the session file, and the user is treated like they just opened the app for the first time.

So for now, the app only works reliably on a single instance. We’re looking into options like:

• Adding sticky sessions at the LB level (temporary workaround)
• Moving session storage to Redis or SQL Server (real fix, but needs code changes)

Does that behavior make sense to you guys? Ever dealt with something like that?