While someone’s use case would have to be verified, the below is to show that there are streaming options in Postgres. Would be interesting to get your take on

While someone’s use case would have to be verified, the below is to show that there are streaming options in Postgres. Would be interesting to get your take on queues vs streams on the below. I consider myself a little late to the Postgres party after time with other nosql and rbdms, but it seems more and more an ok place to consider beginning from. For Streaming… Supabase has some Kafka stream type examples that covers change data capture: https://supabase.com/blog/postgres-wal-logical-replication https://supabase.com/blog/postgres-wal-logical-replication Tables can also do some amount of stream like behaviour with visibility and timeout behaviours: pg-boss — durable job queues with visibility timeouts and retries. Zilla — supports Postgres as a source using CDC to act as a stream. • ElectricSQL — uses Postgres replication and CRDTs for reactive sync (great for frontend state as a stream Streaming inside Postgres also has some attention from Postgres as Event Store https://eventmodeling.org https://eventmodeling.org. This can combine event sourcing with Postgres for stream modeling. pgmq — from Tempo - this is a minimal message queue built on Postgres using append-only design.. Effectively works as a persistent stream with ordered delivery