SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a Postgres Queue

Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by TedDoesntTalk on Tuesday April 11, 2023 @05:07PM (#35531569)

When you’re dealing with billions of messages, i think queuing systems may be tuned more for it?

I’d like to hear why people chose Kafka over some RDBMS tables.

[ Parent | on HN ]

Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by RhodesianHunter on Tuesday April 11, 2023 @07:30PM (#35533152)

Performance and distributed nature.

[ Parent | on HN ]

Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by jjeaff on Tuesday April 11, 2023 @08:18PM (#35533513)

Billions of jobs with hours long time to complete seems like something no one would have the resources for.

[ Parent | on HN ]

Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by OOPMan on Wednesday April 12, 2023 @10:07AM (#35539881)

Just wait till a start convinces someone to give them money for a system that allows anyone, anywhere to queue up infinite loops XD

[ Parent | on HN ]

Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by raverbashing on Wednesday April 12, 2023 @01:54AM (#35535542)

I'm going to be honest, I think some 80% of Kafka users are overengineering it.

Kafka has specific use cases but it seems a lot of people just go "ok use Kafka here" and wait for the load that rarely comes

[ Parent | on HN ]

Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by eurasiantiger on Wednesday April 12, 2023 @08:55AM (#35538867)

In an online environment, having your system go down during those rare times will eventually cost you your business.

[ Parent | on HN ]

Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by raverbashing on Wednesday April 12, 2023 @09:34AM (#35539387)

Sure, then kafka stays online and the rest doesn't because you forgot some details.

[ Parent | on HN ]