Tibco EMS 和 Rendezvous 之间有什么区别
这两种技术之间有哪些主要区别？其中一个比另一个有明显的优势吗？
What are some of the key differences between these two technologies? Does one have obvious advantages over the other?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
RV就像一个广播电台，EMS就像一个电话。
如果您想向城里的每个人发送一条消息（例如今天的天气预报），那么收音机是很好的选择，因为一条消息会同时发送给每个人。电话很糟糕，因为给每个人打电话要花很长时间，而且每次通话要付 20 分钱。
如果您想告诉某人您的信用卡号码，您可以使用电话，因为您可以确定您正在与正确的人交谈。收音机很糟糕，因为镇上的每个人都知道你的信用卡号码。
RV 使用可靠的多播协议，因此它支持快速高扇出消息传递功能，例如将股票报价发送到大量交易台（最初设计的目的）。但代价是安全性差和管理受到一些限制。对于跨多个 LAN 网段或 WAN 的通信也有特殊的考虑因素。
EMS 是一个 JMS 提供者，它以点对点的方式进行通信，就像电话一样。安全性更好，管理任务也更容易。 EMS 是基于服务器的（相对于 RV 的点对点架构），因此存储和转发类型的活动比 RV 更容易。
您可以将两者混合搭配，以获得两全其美的效果。我认为 EMS 的更高版本具有主题的多播功能，但我没有使用过。
RV is like a radio broadcaster and EMS is like a telephone.
If you want to send a message to everyone in town (e.g. the weather forecast for today) then a radio is good because one message goes to everyone simultaneously. Telephone is bad because it takes a long time to call everyone and you pay 20c a call.
If you want to tell someone your credit card number you would use the telephone because you can be sure you are talking to the right person. Radio is bad because then everyone in town knows your credit card number.
RV uses a reliable multicast protocol so it supports fast high fan-out messaging capabilities like sending stock ticks to a large number of trading desks (what it was originally designed for). But the tradeoff is poor security and some limits on administration. There are also special considerations for communication across multiple LAN segments or WANs.
EMS is a JMS provider which communicates in a point-to-point fashion much like a telephone. Security is better and administration tasks are easier. EMS is server based (vs RV's peer-to-peer architecture) so store and forward type activities are easier than with RV.
You can mix and match the two to get the best of both worlds. I think later versions of EMS have a multicast capability for Topics, but I haven't used that.
以上述答案为基础：
To build on above answers:
特定的路由规则或显式订阅来接收数据
来自新主题
对于任何低延迟消息传递（29West 和/或 Rendezous/RV）的粉丝，我建议看看 ZeroMQ（又名
0MQ) 或 Akka。我从未将其投入生产，但我已经使用0MQ构建了速度极快的原型。他们的新服务器产品（2018 年新增）很有趣。RV 中的API 注释
CreateInbox()specific routing rules or explicit subscriptions to receive data
from new topics
For any fans of low-latency messaging (29West and/or Rendezous/RV) I would recommend taking a look at ZeroMQ (a.k.a.
0MQ) or Akka. I've never put it in production at work, but I've built prototypes with0MQthat were blazing fast. Their new server offerings (new in 2018) are interesting.API Note
CreateInbox()