In my company, there is an ASP.NET Core application that is being used today but will retire in a year. The application started having huge amount of concurrent users so we need to scale the application without too much investment in it since we will retire it in a year. So we don't want to use a load balancer on a project that will retire in a year at this point.
As a quick fix, without using a load balancer, we are considering using IIS's multiple application pool strategy to handle concurrent requests by vertical scaling the application machine. (increasing RAM, CPU, etc.)
The app can use shared cookies (using ASP.NET Core's DataProtection where key management is stored in the database) so spawning App Pools won't break the cookie authentication the app uses.
Is this feasible? Will having multiple App Pools help connections not to timeout? (We are upgrading the server with 32 core Xeon 2.9 GHz CPU and 512 GB RAM) We don't mind down time if there is a failure with the single server, we are only looking to handle concurrent requests till the end of the year at this point.