> Pub/sub and request/response are totally different animals. [...] (Is this view uncommon?)
One model is synchronous, the other is asynchronous. I don't see why would
anybody have any doubts.
> Second, pub/sub != work queues.
Publish/subscribe model doesn't say anything about preserving and
acknowledging the messages, and with work queues usually only one worker takes
the queued job. I don't see why would anybody mistake one for the other.
One model is synchronous, the other is asynchronous. I don't see why would anybody have any doubts.
> Second, pub/sub != work queues.
Publish/subscribe model doesn't say anything about preserving and acknowledging the messages, and with work queues usually only one worker takes the queued job. I don't see why would anybody mistake one for the other.