3 ms·

I got the impression that the author didn't really want a message based system at all, but rather a request response system that they tried to impliment within

I got the impression that the author didn't really want a message based system at all, but rather a request response system that they tried to impliment within a message broker. Of course that's going to create more headaches than it solves; it's the wrong solution. Both message brokers and request-response code have their places in distributed systems, but they really need to learn when each is appropriate. I agree, saying that request-reply is "what you really want" was kind of silly, especially after the opening paragraph that states "it depends".

ambicapter 9y ago
Can you elucidate the differences between message-broker and request-response use cases in your eyes?
- marcosdumay 9y ago
  In my eyes (where the GP makes perfect sense), a message broker is asynchronous, there's no implicit wait while your consumers work on our request. A request-response interface will stop the producer until the consumer is done.