Hacker News Reader

dralley is saying your queue push and database write aren't transactional. You have to be ok suffering some small % of message loss or messages sent without a database commit

Depends on your queue semantics, ie is it just an at least once delivery or is there an ack back to the queue service.

If there is a two phase process then you just need idempotence and can safely transact with the db.

It doesn't matter what your queue semantics are. If it's not part of the transaction, delivery and push cannot be guaranteed to be atomic.

At the end of the day, the ONLY way to reliably do this is to hook into the databases native journal/log anyway. Postgres gives you better primitives to work with than installing Qlik for example.

Why do you think so?

Admittedly we're not using it for anything high volume.