Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
Slow apps frustrate users, which leads to bad reviews or customers that swipe left to competition. Unfortunately, seeing and solving performance issues can be a time-consuming struggle.
Most developers use profilers within IDEs like Android Studio or Xcode to hunt for bottlenecks and automated performance tests to catch performance regressions in their code during development. However, testing an application before it ships is not enough.
Time is money, especially in the age of the Internet. In fact, users decide within 8 seconds if they're going to continue using your service.
Frequent lags can destroy your reputation. If you have a serverless architecture, cold starts can cause these lags.
Welcome back! If you missed Part 1, you can check it out here.
The .NET framework is undoubtedly a powerful tool with which to build applications. Incorporating it on serverless platforms unlocks myriad architectural and cost-related benefits. However, the serverless ambitions of .NET developers are often dashed by unendurable cold start durations. This is mainly attributed to how .NET assemblies are jitted which, among other issues, puts a lot of stress on serverless containers starting up. Nevertheless, there are solutions to the overbearing problem, and that is the purpose of this piece: to highlight the solutions any .NET developer can implement to drastically reduce cold start durations and, ideally, even eliminate them completely.