4 ms·
> 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.sq
by simplotek 3y ago
> 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 https://www.sqlite.org/inmemorydb.html
If a message queue does not require any form of persistence, writes don't sound like an issue.
- avinassh 3y agoBut this is purely in-memory with no disk persistence. That’s quite risky
- michaelcampbell 3y agoNot 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.