walex

Oh, and http://github.com/agoodway/walex if you need the realtime database change stuff.

Worth mentioning that WAL is enabling and used by Supabase Realtime [0] and WalEx [1] which both are doing very similar thing - polling the WAL changes in order to emit them as Websocket events. I never worked with WalEx but have experience with Supabase Realtime and it is a joy to work with and fits great into the Supa ecosystem. So many layers are disappearing when you rely more on Postgres! [0] https://github.com/supabase/realtime [1] https://github.com/cpursley/walex

Thanks for the WalEx mention!: https://github.com/cpursley/walex also, there’s https://github.com/sequinstream/sequin if you want something more robust that already works with connectors and smokes debezium in terms of performance and is simpler to operate.

Why not just hook up postgres to something like https://github.com/cpursley/walex or any of the other libraries like Debezium, https://sequinstream.com? Isn't postgres enough?

Right, plus there's character limitations (column size). This is why I prefer listening to the Postgres WAL for database changes: https://github.com/cpursley/walex?tab=readme-ov-file#walex (there's a few useful links in here)

Turning on replication in neon.tech is literally just a switch. And it plays well with a CDC library of mine: https://github.com/cpursley/walex

Check out WalEx for this, it doesn't suffer from the character limits of listen/notify: https://github.com/cpursley/walex

If you're looking for something that's simple to operate (but not quite as robust yet), check out WalEx: https://github.com/cpursley/walex

Node is not appropriate for this sort of workload. You can use WalEx and forward the events to your Node app via webhook: https://github.com/cpursley/walex?tab=readme-ov-file#webhook...

The WAL CDC approach: https://github.com/cpursley/walex?tab=readme-ov-file#publica... CREATE PUBLICATION news_item FOR TABLE news WHERE (topic IS "AAPL");

Great post, I really like the approach of adding additional context for WAL CDC. I imagine this could be implemented with something like Hasura pretty easily (you can access hasura session data in the db). I use both the trigger + audit table approaches in my sass (for user-facing activity feeds) and subscribe to CDC WAL changes for dealing with callback-like logic (i.e., send registration email, clear cache). I'm not a fan of the pg_notify approach due to requirement of adding triggers (performance penalty) and the 8k character limit per column (you will lose data as it will splice off anything larger than that). Application-level tracking or callbacks makes the stack dependent on the application for data integrity, I'd rather the database be the source of truth on all things data. Especially in the age of microservices. For something tu

What do you mean testing with processes? I won't suggest these are the best written tests, but I test various processes, supervisors, etc like this: - https://github.com/cpursley/walex/blob/master/test/walex/sup... - https://github.com/cpursley/walex/blob/e13a9cbf9aca1a2a2d4ed...

You don’t send the entire WAL, just what you subscribe to - and you can even filter via SQL: https://github.com/cpursley/walex?tab=readme-ov-file#publica...

WalEx instead of pub/sub (listen/subscribe): https://github.com/cpursley/walex Supavisor connection pooler: https://github.com/supabase/supavisor

Yep, I should add that. One of the libraries in my list (that I maintain) is WalEx: https://github.com/cpursley/walex/issues It subscribes to the Postgres WAL and let you do the same sort of thing you can do with listen/notify, but without the drawbacks like need for triggers or character limits.