Message Queue vs Message Bus-有什么区别? [英] Message Queue vs Message Bus -- what are the differences?

问题描述

有什么吗?对我来说，MB既了解订户又知道发布者，并充当中介者，向订户通知新消息(实际上是推送"模型).另一方面，MQ更像是一种拉"模型，在此模型中，消费者将消息从队列中拉出.

And are there any? To me, MB knows both subscribers and publishers and acts as a mediator, notifying subscribers on new messages (effectively a "push" model). MQ, on the other hand, is more of a "pull" model, where consumers pull messages off a queue.

我在这里完全偏离轨道了吗?

Am I completely off track here?

推荐答案

总的来说，当涉及到供应商软件产品时，它们可以互换使用，并且在您所描述的推或拉方面没有明显的区别.

By and large, when it comes to vendor software products, they are used interchangeably, and do not have the strong distinctions in terms of push or pull as you describe.

BUS 与 QUEUE 确实是一个遗留概念，最近源自IBM MQ和Tibco Rendezvous之类的系统. MQ最初是1:1的系统，实际上是将各种系统解耦的队列.

The BUS vs. QUEUE is indeed somewhat a legacy concept, most recently stemming from systems like IBM MQ and Tibco Rendezvous. MQ was originally a 1:1 system, indeed a queue to decouple various systems.

Tibco是(作为一个消息传递的)骨干，您可以在同一主题上拥有多个发布者和订阅者.

Tibco by contrast was (sold as a) messaging backbone, where you could have multiple publishers and subscribers on the same topics.

但是，这两种(以及较新的竞争产品)如今都可以在彼此的空间中玩耍.两者都可以设置为中断以及轮询新消息.两者都可以调解各种系统之间的交互.

Both however (and newer competing products) can play in each other's space these days. Both can be set to interrupt as well as polling for new messages. Both mediate the interactions between various systems.

但是短语 message-queue 也用于内部线程内消息泵等，在这种情况下，用法的确不同.如果您想到经典的Windows消息泵，这确实是您所描述的拉模型，但实际上，它比应用程序间或应用程序间更适合应用程序内.

However the phrase message-queue is also used for internal intra-thread message pumps and the like, and in this context, the usage is indeed different. If you think of the classic Windows message pump, this indeed is more the pull model you describe, but it is really more intra-app than inter-app or inter-box.

这篇关于Message Queue vs Message Bus-有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！