I created youjustneedpostgres.com to argue that most teams could use Postgres for almost everything. For queues, for searching, for documents. The recommendation was to stop using a new tool every time a new problem arises, because Postgres probably already does that.

And then I spent months building a tool whose sole purpose is to make you dive even deeper into Postgres. Yes, and the irony doesn't escape me. But the point remains, okay? Postgres can do more than you imagine. The WAL is a complete, ordered, and durable record of every state transition in your database. When you start using it, several architectural problems become much simpler.

In this community you should know, but Change Data Capture is a concept where Instead of your application announcing "this changed," the database notifies you: each insert, update, and delete, in order, at the moment it happens, with the values before and after. And this is already built into several databases; it just needs the "wiring."

This concept already exists in several tools, but all the ones I've used are either too overpowered/expensive, or didn't completely solve my problem. That's why I created Kaptanto (https://kaptan.to). It means "the one who captures" in Esperanto. I wrote a great article about how it was built. I hope you like it!

Oh, and it's open source :)