You've spent years scaling your infrastructure alongside your business growth, and day-to-day, your application performance is thriving. But what happens when your traffic spikes out of your predicted "normal" range, heading into unchartered territory? Are you prepared to support this new influx of customers? Or will you crumble under the pressure of it all - leaving customers dissatisfied at the poor user experience?

Here at Raygun, improving performance is baked into our culture. We don't just think about our application performance, but more broadly, we look at our own infrastructure and ask if there's anything we can do to make it more performant for our business and for our customers. Two years ago, we switched our API from Node.js to .NET Core and achieved a 2000% increase in throughput. To continue that story, we recently upgraded .NET Core 2.1 to 3.1 and saw a 12% increase in performance. We enjoy presenting our performance findings, so in this post, we'd like to give some context into why we upgraded and the conditions that helped us achieve the 12% performance lift.