Azure Service Fabric和消息队列 [英] Azure Service Fabric and Message Queues

问题描述

现在使用Azure Service Fabric，是否还会有一个用例，也可以使用单独的队列解决方案(例如Windows Service Bus)?不利之处可能是新的单点故障，但是有不利之处吗?队列可以添加一些缓冲，但是另一方面，Service Fabric应该能够很好地扩展并提供有状态功能，因此不需要队列缓冲吗?

Now with Azure Service fabric, would there be a use-case for also using a separate queue solution such as Windows Service Bus? The downsides would probably be a new single point of failure, but are there upsides? Queues can add some buffering, but on the other hand, Service Fabric should be able to scale really well and offer stateful capabilities, so no queue buffers should be needed?

推荐答案

当然，好的好处是，诸如Azure Service Bus和Azure Storage Queues之类的服务提供的功能并未包含在Service Fabric中.因此，要问自己的问题是:是否添加外部服务依赖关系以获得该功能，还是通过在Service Fabric上自行构建来保持独立性?在Service Fabric上自包含的应用程序是好的，但是重新发明现有的功能是不好的，因此您必须确定对您来说最大的价值并朝那个方向倾斜.

Sure, the upside is that services like Azure Service Bus and Azure Storage Queues offer features that are not included out-of-the-box in Service Fabric. So the question to ask yourself is: do you add an external service dependency to get that functionality, or do you stay self-contained by building it yourself on Service Fabric? A self-contained application on Service Fabric is good, but re-inventing existing functionality is bad, so you have to decide where the most value is for you and lean in that direction.

例如，考虑一下.

• 可移植性. Service Fabric自身包含的应用程序可以在Service Fabric可以运行的任何地方托管，几乎可以在任何地方(Azure，其他公共云，您自己的计算机或数据中心等)进行.
• 没有外部依赖关系意味着更少的故障点，单个工具集以及统一的开发，部署，升级和维护过程.

另一方面.

• 诸如Service Bus之类的服务提供了 rich功能集.花时间在Service Fabric上构建和维护您所需的功能是否值得?

• Services like Service Bus offer a rich set of features. Is it worth spending the time building and maintaining the features you need yourself on Service Fabric?

这篇关于Azure Service Fabric和消息队列的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！