使用BizTalk代替NServiceBus或MassTransit的优点/缺点 [英] Pros/Cons of using BizTalk instead of NServiceBus or MassTransit

问题描述

我很好奇它是否考虑将BizTalk用于发布/订阅消息传递体系结构的实现(基本上，我真正需要的只是NServiceBus或MassTransit的功能).我的经理趋向于坚持直接从Microsoft提供的框架，因此，作为我尽职调查的一部分，我需要为双方都使用一套很好的赞成/反对意见.任何指导将不胜感激！

I am curious if it even makes consider BizTalk for the implementation of a pub/sub messaging architecture (basically what you can do with NServiceBus or MassTransit is all I really need). My manager tends to want to stick with frameworks provided directly from Microsoft and so as part of my due diligence as to which one to use I need to give a good set of pro/cons for both sides. Any guidance would be greatly appreciated!

推荐答案

Broker的主要缺点之一是版本和升级非常困难.您将必须停止消息流以升级特定端点.服务总线允许端点自治并独立升级.

One of the major cons of a Broker is that it is very difficult to version and upgrade. You would have to stop the flow of messages to upgrade a particular endpoint(s). A Service Bus allows endpoints to be autonomous and be upgraded independently.

然后在规模上有所不同.对于Broker，趋势是将那些扩展(垂直)与为扩展(水平)而构建的服务总线相对.您还必须通过某种类型的HA设置(通常是集群)使Broker具有高度可用性.再加上这样做的软件成本，可能会导致成本过高.

Then there is a difference in terms of scale. With a Broker the tendency is to scale those up(vertical) versus a Service Bus which is built for scaling out(horizontal). You would also have to make the Broker highly available through some sort of HA setup(clustering usually). This combined with the cost of software to do so can become pretty cost prohibitive.

特别是，NSB将提供付费支持模式，因此，如果您的经理担心出现问题时不希望有人在电话线的另一端，则可以购买支持.

NSB in particular will be offering a paid support model so if your manager is nervous about not having someone on the other end of the line when something goes wrong, you can buy into support.

这篇关于使用BizTalk代替NServiceBus或MassTransit的优点/缺点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！