News for hackers. Stuff that matters.

A comment on SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a Postgres Queue. Parent comment

Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by simplotek on Tuesday April 11, 2023 @01:52PM (#35528637)
> The problem with a queue on SQLite is that every successful read implies a write.

SQLite also supports in-memory databases with shared cache.

https://www.sqlite.org/inmemorydb.html

If a message queue does not require any form of persistence, writes don't sound like an issue.

[ Parent | on HN ]
Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by avinassh on Tuesday April 11, 2023 @02:28PM (#35529189)
But this is purely in-memory with no disk persistence. That’s quite risky
[ Parent | on HN ]
Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by michaelcampbell on Tuesday April 11, 2023 @04:36PM (#35531192)
Not to be coy, but it only is if it is. For this application I'd agree, but there are plenty of apps that want queues for in-memory use, and if the thing that holds the memory for the queue dies, chances are the whole ecosystem has.

Sometimes this is fine.

[ Parent | on HN ]