How far can you go without a message queue?

Re:How far can you go without a message queue? by tatersolid on Thursday August 25, 2022 @11:13PM (#32602955)

You probably don’t need a separate message queue service if you have a transactional (probably “real SQL”) database. The “table as queue” pattern in SQL has been used since the 1970s at massive scale and was taught in my CSE 100-level classes back in the 1990s. The natural API for such a thing is basically the same as Rabbit/Kafka//SQS/whatever.

[ Parent | on HN ]

Re:How far can you go without a message queue? by eurasiantiger on Friday August 26, 2022 @09:14AM (#32607050)

The ”massive scale” of the 1970s is very far from today’s ”ordinary scale”! Just saying that this approach really does not scale well and problems will start around high hundreds of thousands to low millions of messages queued.

[ Parent | on HN ]

Re:How far can you go without a message queue? by skyde on Friday August 26, 2022 @02:24AM (#32603940)

i agree with you if you have a transactional SQL it’s usually best to stick to this until it doesn’t scale.

it allows you to make the « add message to queue » part of a transaction that update other table which is nice!

[ Parent | on HN ]

Re:How far can you go without a message queue? by kevin526175998 on Friday August 26, 2022 @02:21AM (#32603931)

do you have any pointers? Just curious how this is taught in the old days

[ Parent | on HN ]