Azure 队列存储的行为与 MSMQ 相同吗？
我构建了一些在 Windows Server 上利用 MSMQ 的应用程序。我想将它们移植到基于 Azure 的 Web 应用程序，这可以帮助我解决过去遇到的一些安全和信任障碍挑战。
我的问题是，我是否可以期望 Windows Azure 存储的消息队列方面的行为与 MSMQ 相同？
I have a few applications that I have built that leverage MSMQ on a Windows Server. I would like to port these to Azure-based Web Applications which helps me with some of the security and trust-barrier challenges I have faced in the past.
My question is, can I expect that the Message Queue aspects of Windows Azure storage will behave the same as MSMQ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
一般来说，事实并非如此。虽然两者都是队列解决方案，但您会发现 Windows Azure 队列不具有与 MSMQ 相同的保证（有充分的理由）。例如，WAQ 支持“至少一次”与“恰好一次”的交付模型。它还使用 2PC 模型，您必须弹出然后删除消息。它也不像 MSMQ 那样涉及事务可以处理。然而，对于云排队场景，其中一些考虑因素就不那么重要了。还有其他细微差别（消息 TTL、不可见性、更新、存储时间等）。
如果您解释一下您的排队需求必须具有哪些功能，可能会更容易更完整地回答。另外，请记住，AppFabric 有一个队列服务，该服务也可能适合您的实际需要。
In general, not really. While both are queueing solutions, you will find that Windows Azure queues don't have the same guarantees that MSMQ will have (for good reason). For instance, WAQ supports a delivery model of 'at least once' versus 'exactly once'. It also uses a 2PC model where you must pop and then delete a message. It is also not involved in transactions like MSMQ can handle. However, for cloud queuing scenarios, some of these considerations matter less. There are other nuances as well (message TTL, invisibility, renewals, storage time, etc.) that differ.
It might be easier to answer more completely if you explain what features your queueing needs must have. Also, keep in mind that AppFabric has a queueing service that also might be appropriate depending on what you really need.