Anything can be a message queue if you use it wrongly enough

Re:Anything can be a message queue if you use it wrongly enough by bob1029 on Sunday June 04, 2023 @01:13PM (#36187356)

I am doing the same with SQL Server. The messages table is more of a bus than a queue in our case (columns like ReplyToId, etc). Using it for RPC communication between cloud bits. Much cheaper than Azure Service Bus and friends.

[ Parent | on HN ]

Re:Anything can be a message queue if you use it wrongly enough by andrewstuart on Sunday June 04, 2023 @01:24PM (#36187468)

MS SQL server supports SKIP LOCKED which enables messages queues.

[ Parent | on HN ]

Re:Anything can be a message queue if you use it wrongly enough by Digit-Al on Sunday June 04, 2023 @03:44PM (#36188860)

Just out of interest: any reason you're not using the SQL server service broker?

[ Parent | on HN ]

Re:Anything can be a message queue if you use it wrongly enough by bob1029 on Sunday June 04, 2023 @04:39PM (#36189362)

It's only available in managed instances or on-prem. We are trying to use the "serverless" flavor of Azure SQL throughout:

https://learn.microsoft.com/en-us/azure/azure-sql/database/f...

[ Parent | on HN ]

Re:Anything can be a message queue if you use it wrongly enough by Digit-Al on Sunday June 11, 2023 @07:12AM (#36280230)

Ah, okay. Cheers for the reply.

[ Parent | on HN ]

Re:Anything can be a message queue if you use it wrongly enough by nickpeterson on Sunday June 04, 2023 @04:45PM (#36189417)

I don’t know the OPs answer, but I’d hazard to guess because ssmb is a completely neglected feature with very little in the way of community or UI. In theory it would be great, but MS basically never invested in it after its release and now it’s just a random, “who knows when we’ll drop support for this” sql server feature.

[ Parent | on HN ]