4 ms·
What's the snarky bit at the end of article about? > And then of course, there's the use case where you use the queue as a messaging mechanism between front-en
by bhaak 3y ago
What's the snarky bit at the end of article about?
> And then of course, there's the use case where you use the queue as a messaging mechanism between front-end threads/processes [...] because your language doesn't support inter-process communications.
Isn't it the other way around? A message broker is used as a simple queue but then you immediately have the option to scale up to n producers and m consumers if demand requires is.
But even if there is only one single producer and one single consumer you still got the advantage of the decoupling of the two sides of the queue.
- macintux 3y agoI imagine he's being snarky about the fact that Erlang was designed around simple queues and thus you get that abstraction essentially for free, while in other languages you have to add more infrastructure once you recognize the need.