服务总线并将推送通知推送到设备 [英] Service Bus and push notifications to device

问题描述

       我正在研究如何使用云服务应用程序.应该可以在一侧处理服务总线，而在另一侧处理WebSocket.该应用程序.应该对消息做出反应并将其推送到设备.我正在寻找这种设计的任何材料 而且这如何扩展.看来，总线可以比云服务应用程序更好地扩展.设备数量也可能会增长.设计注意事项是什么?

         I am researching how a Cloud service app. should work to handle a Service Bus on one side and WebSockets on the other. The app. should react to messages and push them to devices. I am looking for any material on such designs but also how this could scale. It seems that the Bus could scale better than the cloud service app. Number of Devices could grow too. What are the design considerations ?

我认为我们不是在寻找https://azure.microsoft.com/en-in/services/notification-hubs/吗?

I don't think we are looking for https://azure.microsoft.com/en-in/services/notification-hubs/ ?

AFAIK总线是面向消息的中间件.我想念什么吗?

AFAIK the bus is Message-oriented middleware. Am I missing something ?

谢谢

Mohan

推荐答案

我相信

I believe SignalR is the service that you are looking for.

使用SignalR Service，您不必在WebSockets前端上考虑性能和扩展性，但是由于Service Bus无法直接将消息推入SignalR，因此您将需要一个简单的Function应用程序，该应用程序可在Service Bus Messages和输出 到SignalR.

With the SignalR Service, you wouldn't have to think about performance and scaling on the WebSockets front but since Service Bus can't directly push messages to SignalR, you would need a simple Function app that triggers on Service Bus Messages and outputs to SignalR.

有一个文档解释这种情况 这里.

There is a doc explaining scenarios like this here.

此外，根据您方案中的消息量，您还将考虑将Azure Service Bus与Azure Event Grid集成在一起，如所述 这里.

Also, depending on the volume of messages in your scenario, you would also look at integrating Azure Service Bus with Azure Event Grid as explained here.

这篇关于服务总线并将推送通知推送到设备的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！