rorymalcolm

Wrote this; the MultiXact system in Postgres is really pretty complicated but not something you come across _that_ often (unless you're running workloads like this) - it's worth understanding exactly the mechanics of what's happening when you do hit scaling issues like this and if something like the leasing we do here is possible.

Disclaimer: I work at the incident company

This is one of those projects where the end goal is to build the scariest button possible. You cannot complete the project until you’ve pressed that button. You do all the work to build the button, then you have to press it.

Never not scary, never not eventually fun, but type 2 fun for sure.

Disclaimer: I worked with Johanna on this

I had a lot of fun “long tail whackamoling” our way through edge queries that our model of “this is eligible for a read replica” wasn’t accurately catching. Honestly just one of those “keep reading traces and working through them” development processes that just keeps drive a graph down and to the right.

Building higher-touch AI products that are applicable across the entire customer base of an existing enterprise SaaS provider on release does feel impossible.

It's very obvious when you look at the AI companies that have 'exit-velocity' in this space that they are playing in that they are either one of the following:

1. Targeting a need within that org that's narrow enough to be MVP-able enough across a diverse customer base

2. Targeting IC work directly

As we add more complexity here, it's going to be a long, long slog to market - even with model advancements.

(Full disclosure, I work at incident.io!)

We recently released our On-call product, and as part of that, had to think a lot about redundancy and 'failing safety'.

Here's how we achieve it - and how we're thinking about it. Interested if any other examples of this exist in the wild - I'd love to know more about how eg: Datadog achieve this.

Yes - it is!

(Full disclosure, I work at incident.io!)

We recently released our On-call product, and as part of that, had to build a mobile app.

We'd noticed there's been some debate recently regarding React Native, and if you can build 'native tier' apps using it. We'd seen a lot of this but as part of an initial hackathon tried Explo / RN / Nativewind and were completely blown away by both the quality of app we could produce and the developer experience that let us do this quickly.

If anyone's in this space / thinking about making a technical decision here I couldn't recommend this stack strongly enough!

Were Prequel using RaabitMQ to stay cloud platform agnostic when spinning up new environments? Always wondered how companies that offer managed services on the customers cloud like this manage infrastructure in this regard. Do you maintain an environment on each cloud platform with a relatively standard configuration, or do you have a central cluster hosted in one cloud provider which the other deployments phone home to?