Azure的服务总线队列主题VS队列网络/辅助角色 [英] Azure Service bus queues topics vs queues for web/worker roles

问题描述

我知道
<一href=\"http://stackoverflow.com/questions/1906244/choosing-between-net-service-bus-queues-vs-azure-queue-service\">Choosing .NET服务总线队列VS Azure的队列服务

提供了一些答案，何时用于Web /辅助角色VS的Azure服务总线队列，但我刚开始学习Azure和一直在寻找一些更彻底。

provides some answers as to when to use queues for web/worker roles vs Azure Service bus, but I'm just starting to study Azure and was looking for something more thorough.

它说：NET服务总线更是专为集成系统，而不是提供一个通用的可靠的消息传递系统设计。

It says "NET service bus is more specifically designed for integrating systems rather than providing a general purpose reliable messaging system".

只是想知道如果我能得到澄清呢？是否单独的远程应用程序之间，最好是使用服务总线队列和web /辅助角色之间通信时使用正常的Azure队列通信时的意思。

Was just wondering if I could get clarification of this? Does it mean when communicating between separate remote applications it is better to use the Service bus Queue and when communicating between web/worker roles you use the normal Azure queues.

感谢

推荐答案

服务总线队列相比，存储队列对应提供了更多的复杂性。
下面是比较和对比的链接。

The service bus queues offer a lot more sophistication compared to the storage queue counterpart. Here is a link comparing and contrasting.

http://msdn.microsoft.com/ EN-US /库/ hh767287％28VS.103％29.aspx

我会用最能满足我的需求有利于仿制工作分配和存储队列服务总线队列队列中，如果我的需求是更复杂的像的Pub / Sub等等...

I would use the queue which best serve my needs favoring storage queue for generic work distribution and the service bus queues, if my needs are more sophisticated like Pub/Sub etc ...

这篇关于Azure的服务总线队列主题VS队列网络/辅助角色的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！