{"id":42,"date":"2024-11-22T06:40:07","date_gmt":"2024-11-22T06:40:07","guid":{"rendered":"https:\/\/prageeth.online\/?p=42"},"modified":"2025-09-05T13:15:47","modified_gmt":"2025-09-05T13:15:47","slug":"coldstart-improvements-in-legacy-but-money-making-dotnet-applications","status":"publish","type":"post","link":"https:\/\/prageeth.online\/?p=42","title":{"rendered":"Coldstart improvements in legacy dotnet applications"},"content":{"rendered":"\n

Before we dive into the details, let\u2019s clarify what a cold start is. Cold start <\/em>refers to a problem where a system or its part was created or restarted and is not working at its normal operation[1].<\/p>\n\n\n\n

I’m going to talk about how quickly a web application can handle a request from the cold. It’s important to understand that some of the legacy applications have to deal with cold start depending on the server that’s hosted. In this example, let\u2019s take IIS. You may be thinking, why on earth are you using IIS? But the truth is most of the well-established .NET Framework-based web applications still use IIS.\u00a0<\/p>\n\n\n\n


There are a few things you can do in IIS to do things faster. Before talking about that, let\u2019s see why things start slowly.<\/p>\n\n\n\n


First, take a closer look at the startup. There can be many things there, from dependency injection to creating resources such as pub sub-topics and subscriptions. Strangely, there could be some compilation processes in there, creating artifacts that can be consumed later. None of these approaches may be wrong at the time of implementation. However, money-making applications have a tendency to grow rapidly in terms of features as well as users. Eventually, you will start having scaling and performance issues. <\/p>\n\n\n\n


How can we resolve some of the issues?<\/p>\n\n\n\n