You need change data capture (CDC). That is, when your database changes, you need those changes to trigger actions or sync data with other systems. The question is: how do you capture and deliver those changes reliably?...

We're Sequin, a Postgres CDC tool to streams and queues like Kafka, SQS, HTTP endpoints, and more. Like any Postgres maxi, we tend to find ourselves down a Postgres rabbit hole a couple times per month. This is one of those times :) Who doesn't like to...

The differences between at-most-once, at-least-once, and exactly-once delivery in messaging systems....

I set out to benchmark pg_net to give the Supabase community the information needed to decide when pg_net will work for them and when they should evaluate other options....

We're Sequin, a Postgres CDC tool to streams and queues like Kafka, SQS, HTTP endpoints, and more. A lot of our users use Supabase, so we've explored all the ways they've done event-driven workflows before Sequin. Supabase makes it easy for your frontend to...

We're Sequin, a Postgres CDC tool to streams and queues like Kafka, SQS, HTTP endpoints, and more. We have a web console for managing tables and streams, and that console is built with LiveView + LiveSvelte. We wrote previously about how much we enjoyed using LiveView with LiveSvelte. Since...

We're Sequin, a Postgres CDC tool to streams and queues like Kafka, SQS, HTTP endpoints, and more. Stable, sequential ordering is a very useful thing to have when building a streaming system. But Postgres' behavior here can be surprising! We go down the rabbit hole below. An...

Phoenix's LiveView is powerful. But it felt like it was missing something. Adding Svelte not only filled a big gap – it introduced us to an entirely new way to develop web apps....

Working with data at rest is where Postgres shines. But what about when you need data in motion? What about when you need to trigger a workflow based on changes to a table? Fortunately, Postgres comes with a lot of options to make this happen....

Let's look at how we can use `:noreply` and `GenServer.reply` to allow a GenServer to continue working even while its `call`ers wait for the result of long-running operations....

An outline of the options available in the Elixir BREAK menu....

How we used Elixir's Observer to chase down and fix some puzzling runtime issues....

Webhooks come with some challenges. We prefer polling an /events endpoint instead when possible....