Re:How do you cut a monolith in half?
by beat on Friday June 30, 2017 @10:33AM
(#14670985)
The reason to use message queues rather than RDBMS for queue behaviors isn't because queues do stuff databases don't, but rather because of connection cost. There's a lot of complicated handling noise around the database connection, whereas queues tend to be very inexpensive.
[ Parent
| on HN ]
As an alternate anecdote, I have had far more issues with MQ connections than with RDBMS connections. I don't think there is a clear advantage to messaging from that standpoint.
Re:How do you cut a monolith in half?
by balfirevic on Friday June 30, 2017 @11:43AM
(#14671437)
Do you mean development/complexity cost or performance cost? If it is the former, then I don't really see it. If it is the latter then yes - RDBMS backed queue is probably going to hit scaling limits earlier then dedicated product.