Holy Grail of Solutions: Solving .NET Lambda Cold Start Part II

The .NET framework is undoubtedly a powerful tool to build applications with. Incorporating it on serverless platforms unlocks myriads of architectural and cost 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, among other issues.


The Fundamental Problem: Solving .NET Lambda Cold Start Part I

As the age-old battle of .NET(C#) vs Java rages on, it is evident that there is still no clear victor albeit Java’s larger user group. Both languages emerged from the same aspirations of humanity and both languages have served similar purposes throughout the evolution of technology. However, as we now enter the era of serverless, .NET is on the back foot with an evident disadvantage regarding cold starts.


.NET monitoring with Datadog APM and distributed tracing

Since it was first introduced in 2002, Microsoft’s .NET Framework has garnered a robust user base that includes organizations like UPS, Stack Overflow, and Jet.com. And now, thanks to the rise of the .NET Core runtime, this high-performance framework also supports cross-platform development. To provide deeper visibility into all of these environments, we are pleased to announce that Datadog APM and distributed tracing are generally available for .NET Framework and .NET Core applications.


Writing High Performance .NET Code

At some point in our careers, many of us have found ourselves working on a project that requires performance tuning. The need to write high performance .NET code should come from performance issues or business needs. Today, we’ll take a look at just a few of the ways we can improve our .NET application’s performance. And hopefully, you’ll take away something that you can use on your current and future products.