We’ve just launched our new Status Pages!Learn more

The latest news from incident.io HQ

We’re building the best way for your whole organisation to respond, review and learn from incidents. This is where we talk about how and why.

Engineering

Keep the monolith, but split the workloads

Everybody loves a monolith, but you can hit issues as you scale. This post is about a technique – splitting your workloads – that can significantly reduce that pain, costs little, and can be applied early.

Lawrence JonesPicture of Lawrence Jones

Lawrence Jones

9 min read
Engineering

Taking the fear out of migrations

Migrations can be scary: here’s how we run migrations at incident.io to keep things simple and safe

Lisa Karlin CurtisPicture of Lisa Karlin Curtis

Lisa Karlin Curtis

9 min read
Engineering

Intermittent downtime from repeated crashes

This is a technical write-up of an incident on Friday 18th November 2022 where we experienced 13 minutes of downtime from intermittent crashes.

Lawrence JonesPicture of Lawrence Jones

Lawrence Jones

12 min read
Engineering

Making code-generation in Go more powerful with generics

Go 1.18 added generics to the language a few months ago. Here’s how we’ve combined generics with code generation to make our code safer and easier to read and write.

Isaac SeymourPicture of Isaac Seymour

Isaac Seymour

11 min read
Engineering

Building great developer experience at a startup

We’ve invested in our developer experience to help our team ship great a product at pace.

Lisa Karlin CurtisPicture of Lisa Karlin Curtis

Lisa Karlin Curtis

8 min read
Engineering

Building Workflows, Part 1 — Core concepts and the Workflow Builder

Part one of a deep-dive into building our workflow engine, covering core workflow concepts and how they are used to power the Workflow Builder.

Lawrence JonesPicture of Lawrence Jones

Lawrence Jones

20 min read
Engineering

Building Workflows, Part 2 – the executor and evaluation

Part two of the series lookin at the workflow executor, and concluding with an evaluation of the project in terms of developer time, extensibility, and quality of outcome.

Lawrence JonesPicture of Lawrence Jones

Lawrence Jones

21 min read
Engineering

Updating our data stack

How we’ve updated our data stack since it was first built in January.

Jack CookPicture of Jack Cook

Jack Cook

13 min read
Scrabble of Own Your Errors
Engineering

Making Go errors play nice with Sentry

Getting Go errors to work well with Sentry is hard. This post explains how we got them playing nicely by deduping stacktraces.

Lawrence JonesPicture of Lawrence Jones

Lawrence Jones

8 min read

Stay in the loop: subscribe to our RSS feed.