Engineering on Raygun Blog

How we scale Raygun's architecture to handle more data

Tue, 25 Aug 2020 09:17:09 +1300

Due to the huge importance of sourcemaps in the workflow of our customers, sourcemaps are a crucial part of our Crash Reporting offering.

We constantly strive to stay ahead of our customer demands as the amount of data we process continues to grow. We identified the sourcemapping process as an area ripe for performance improvement, so we took it apart and looked at exciting ways to build it from the ground-up using cutting-edge tech. Our key objectives were: horizontal scalability, blazingly fast processing rates and easy monitorability.

How we made an 83% performance improvement using Real User Monitoring

Tue, 18 Aug 2020 09:17:09 +1300

As applications evolve, we may start to lose visibility into why things are slow.

Web apps often suffer in silence as customers are more likely to leave when they’re unsatisfied rather than reach out. Complex user flows, resource-intensive API calls, and an ever-growing codebase can all contribute to poor performance.

This is why we don’t have scheduled performance days. At Raygun, the engineers are empowered to investigate improving the performance of our product, using our own tools to support us.

How Raygun increased transactions per second by 44% by removing Nginx

Fri, 31 Jul 2020 09:17:09 +1300

Here at Raygun, improving performance is baked into our culture. In a previous blog post, we showed how we achieved a 12% performance lift by migrating Raygun’s API to .NET Core 3.1.

In publishing this, a question was asked on Twitter as to why we still use Nginx as a proxy to the Raygun API application. Our response was that we thought this was the recommended approach from Microsoft. It turns out this has not been the case since the release of .NET Core 2.1. Kestrel has matured a lot since the .NET Core 1.0 days when we first started using it and the security experts at Microsoft are comfortable with Kestrel being used on the front line since the release of .NET Core 2.1.

Achieving a 12% performance lift migrating Raygun's API to .NET Core 3.1

Thu, 04 Jun 2020 09:17:09 +1300

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.

.NET Core or Node.js? [We increased throughput by 2,000%]

Fri, 19 May 2017 02:36:09 +0000

A few months ago, Raygun was featured on the Microsoft website with how we increased throughput by 2,000 percent with a change from Node.js to .NET Core.

The performance improvements were immediate and nothing short of phenomenal.

In fact, using the same size server, we were able to go from 1,000 requests per second per node with Node.js, to 20,000 requests per second with .NET Core. Check out the case study for a quick refresh.