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 vidarh on Tuesday April 11, 2023 @01:27PM (#35528272)
I processed ~3m messages a day on Sqlite using a pair of ca 2006 era Xeon on spinning rust (for redundancy; each could easily handle the load by itself). The queue processor was written in Ruby and ran on the (very slow) 1.8.x series (even then it used about 10% of a single core.

On modern hardware you should be able to trivially handle more than that.

[ Parent | on HN ]
Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by randito on Tuesday April 11, 2023 @01:49PM (#35528597)
Does this mean you are processing messages on only one machine, since it's Sqlite? Depending on what you are processing, that could take longer than the queue/dequeue.
[ Parent | on HN ]
Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by vidarh on Tuesday April 11, 2023 @02:26PM (#35529168)
The queue was managed by a server written in Ruby that spoke Stomp [1], so while for the biggest queue most of the processing did in fact happen on the same machine, that was just because it happened to fit.

[1] https://stomp.github.io/

[ Parent | on HN ]