Case Study 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.

Why high-performing teams consolidate monitoring tools with Raygun APM

Tue, 02 Jun 2020 09:17:09 +1300

Raygun helps thousands of software teams diagnose and resolve performance problems faster and more efficiently. We understand that in today’s current climate, there is even more pressure on teams to ensure software quality across the whole stack, all while being cost-effective.

It’s no easy task! But we know that consolidating tools can help. Resolving performance problems becomes faster and more cost effective when your whole team has access to performance data without needing to correlate between disparate tools.

.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.

Raygun adds value at every stage of the development process

Thu, 11 Sep 2014 02:23:15 +0000

Ross Hawkins is the Owner (and a Consultant/Developer) of Ignition Development Limited. The company mainly provides consulting and bespoke web development services (using ASP.NET and other Microsoft technologies) to large scale ecommerce shops in Europe. They also have their own CMS product which is supplied to a number of small/medium sized business in New Zealand. With a team of around 10 people, everyone works remotely, spanning locations from New Zealand to Norway.

Raygun allows GoChime to deliver great software to users

Wed, 03 Sep 2014 02:52:03 +0000

Brian Falk is the Chief Technical Officer at GoChime, and manages a growing team of developers for their innovative product. The company creates tools to empower companies and brands to extend the reach of their email campaigns onto Facebook.

GoChime uses Raygun to manage errors and crashes across their applications and ultimately keep end users happy. Software bugs are inevitable, but as Brian explains, having Raygun implemented gives them peace of mind and the ability to react quickly if any problems occur.

Using Raygun with Lighthouse Issue Tracker

Tue, 26 Aug 2014 23:21:22 +0000

Another integration is now live with Raygun, this time it’s issue tracking software – Lighthouse, a collaborative issue tracker with a simple workflow for teams of any size.

This powerful integration will let your team connect error groups in Raygun to existing Lighthouse tickets, or create new ones.

** How to set up the Lighthouse Issue Tracker + Raygun integration**

In your Raygun dashboard, click on Application Settings -> Plugins -> Lighthouse, then click Setup.
Enter your Lighthouse URL, this will look something like: “https://example.lighthouseapp.com”.
Also, enter a Lighthouse API token and hit Save Changes. To get a token, log in to Lighthouse, navigate to your profile page and locate the API token section on the sidebar. Select the project(s) you wish to use from the drop down and click create, you can give the key a label if you wish. The key should appear in the “Your API Tokens” list. You can read the article on Lighthouse about retrieving your API key here.
Pick a project that you want to link tickets with, click Enabled then Save Changes.

View an error group in Raygun and you’ll notice a blue Lighthouse button in the top-right of the screen. This will allow you to create a new Lighthouse ticket for the error, or link with an existing one.

Hanx Writer Makers, Hitcents, Use Raygun For Awesome Error Reporting

Tue, 19 Aug 2014 23:38:57 +0000

The Hanx Writer hit the top spot of the App store this week. The app replicates all the noises typewriter lovers have come to associate with the computer keyboard predecessor. The clicking of the keys and the chiming when you come to the end of a line makes for a nostalgic experience, the app comes with a single font, color and typewriter in the free, default version, but you can unlock more font and typewriter features with in-app purchases.

Segmenting your users to increase conversions

Mon, 21 Jul 2014 05:00:14 +0000

Well, it’s time for another post on growth techniques and how to increase conversions, but I’m in danger of appearing to have a bucket obsession, after my last post was also largely bucket themed. Anyway, we’ll press on with things and gloss over that as I wanted to share with you how we manage users inside our sales funnel at Raygun by dividing and segmenting them up into groups. This is a great way to ensure the on-boarding process of new customers for your website, application or service is working efficiently.

The hourglass sales funnel – How to get more sign ups

Fri, 13 Jun 2014 01:36:27 +0000

The term ‘growth hacker’ has become a bit of a buzz word of late. The amount of tools that are now available to developers and marketers to fine-tune customer on-boarding performance, retention and engagement can often be overwhelming. What do I measure? What conclusions can I take away and how do I implement a change? Just what does all this data mean?

The issue with ‘growth hacking’ is that it spans across multiple roles inside an organisation, it’s very hard to find a single person with the unique skills to cover both sides of the role. Usually it ends up with the developer doing ‘a bit of marketing’ and a marketer trying to do ‘a bit of development’ to get things like analytics and tracking codes installed. Where does development stop and marketing take over and vice versa? Strategy quickly goes out of the window.