News for hackers. Stuff that matters.
Re:Postgres transactions are a distributed systems superpower by jayd16 on Thursday July 02, 2026 @05:43PM (#48767773)
It's a bit of trick that the outbox to queue part of it likely needs to support "at least once but duplicates possible" into the queue.
Re:Postgres transactions are a distributed systems superpower by mrkeen on Thursday July 02, 2026 @05:47PM (#48767814)
"Send multiple times from D to Q and deduplicate with a UUID" (idempotency) is well short of "insert into both D and Q or neither" (atomicity)
Re:Postgres transactions are a distributed systems superpower by jayd16 on Thursday July 02, 2026 @06:32PM (#48768223)
What are you saying here? I'm pointing out that you need to be ok with the lack of exactly once transaction between O and Q. Maybe you're agreeing and simply saying that's a fine?
Re:Postgres transactions are a distributed systems superpower by KraftyOne on Thursday July 02, 2026 @05:46PM (#48767794)
Every item will be written to the queue exactly once (as the update is transactional). Queue processing may need at-least-once semantics, yes, depending on what exactly you're doing.
Re:Postgres transactions are a distributed systems superpower by jayd16 on Thursday July 02, 2026 @06:35PM (#48768250)
The queue write is not in the transaction. The proposed trick is that that is ok because an outbox is able to be transacted on. It kicks the can some what...