哪种消息传递服务可与Azure功能扇出模式一起使用而无扇出功能? [英] Which messaging service to work with Azure Function Fan-out pattern without fan-back?
问题描述
我们是Azure消息服务和功能的新手，我们了解了不同消息服务的基本概念，例如存储队列，服务总线队列，服务总线主题和事件中心，我们还阅读了扇出模式由Microsoft提供，但是其工作方式更像是扇出，然后是扇回，这意味着在扇出过程中，当前功能仍会保留在那里，直到所有资源扇回为止.
We're new to the Azure messaging service and Functions, we learned the basic concept of different message service like Storage Queue, Service Bus Queue, Service Bus Topic and Event Hubs we also read the fan-out pattern by microsoft but that works more like fan-out then fan-back, which means during the fan-out process, current function still hold up there until all resource fan-back.
一种简单的情况是，我们将对象保存在 azure函数启动器中，并成功保存到存储中后，我们想向实施的3个不同的目的地/消费者发送一条通用消息/使用天青函数触发，
A simple scenario would be, we are saving an object in azure function starter and after saved successfully into storage, we would like to send a common message to 3 different destination/consumers implemented/triggered with azure functions,
功能1 将用于通知(signalR或电子邮件)
function 1 would be using for notification(signalR or email)
功能2 将用于日志记录(SQL Server)
function 2 would be using for logging(Sql Server)
功能3 将用于持续的业务逻辑.
function 3 would be using for continuing business logic.
上述所有Azure功能都将独立/隔离工作，并且我们的 azure功能启动器不必等待这3个功能中的任何一个，邮件发送出去后，它应该退出或终止.基本上，该概念将是一个拥有多个消费者的发布者，并且可以确保将消息传递给所有3个消费者.
All of above azure functions will be working independently/isolated, and our azure function starter doesn't have to wait for any of these 3 functions, it should exit or terminate once the message sent out. Basically the concept would be one publisher with multiple consumer and can guarantee that message would be delivered to all 3 consumers.
在Azure中将推荐使用哪些消息传递服务?我认为我们应该选择这三种消息传递服务存储队列，服务总线主题和事件中心之一，但是我们可以参考的Azure资源有限...
Which of the messaging service would be recommend in Azure? I think we should pick one of those three messaging servce Storage Queue, Service Bus Topic and Event Hubs but there is limitation of Azure resource that we can refer...
推荐答案
简单-Azure服务总线主题.
Simple - Azure Service Bus Topic.
我们在工作中实现了相同的模式.收到消息后，我们将其发送到主题，然后由不同的TopicListeners/Subscribers接收.然后，每个订户都调用第三方服务.
We implement the same pattern at work. Once a message comes in we then send it out to the Topic which then gets picked up by different TopicListeners/Subscribers. Each subscriber then calls a third party service.
Here is documentation of the difference between Service Bus and Storage Queue. https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-azure-and-service-bus-queues-compared-contrasted
这篇关于哪种消息传递服务可与Azure功能扇出模式一起使用而无扇出功能?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
