Postgres as a Message Bus: Implementing Durable Event Queues with LISTEN/NOTIFY and Logical Decoding
You’ve got a small-ish system: a monolith plus a couple of background workers, maybe one or two sidecar services.
You’ve got a small-ish system: a monolith plus a couple of background workers, maybe one or two sidecar services.
If you’ve been doing data-heavy backend work over the last decade, your mental model probably looks something like this:
If you’d told me a few years ago that SQLite would be at the center of “planet-scale” serverless architectures, I would’ve assumed you were trolling.
If you’ve just set up a ClickHouse cluster, the next scary step is: “Okay… now how do I actually create tables the right way so I don’t regret everything in ...
There’s a decent chance you have a cron job somewhere that looks like this: