Azure服务总线:什么是“请求"和“消息"? [英] Azure Service Bus: What's a 'request' and a 'message'?

查看:66
本文介绍了Azure服务总线:什么是“请求"和“消息"?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在Microsoft Azure的服务总线下,您可以查看不同队列/主题等的活动图.

In Microsoft Azure, under service bus, you can see activity graphs for the different queues/topics etc.

该图显示了各种不同的行,例如传入消息传出消息成功请求等.

The graph shows various different lines, such as incoming messages, outgoing messages, successful requests etc.

什么是请求?什么是消息?

What is a Request? And what is a Message?

请求似乎一直在发生,并且通常比消息的数量(在主题中)大得多.即使侦听队列的服务器数量保持不变-有时请求的数量也会急剧增加,而不会看到消息的数量发生任何变化.

Requests seem to be constantly occurring and often significantly large than the number of messages (in topics). Even though the number of servers listening to the queue remains the same - sometimes the number of requests will dramatically increase without seeing any change in the number of messages.

推荐答案

假定,请求是对队列/订阅的轮询,即使这并未导致消息被拉出.使用OnMessage消息泵模型,您通常会永远"等待直到消息到达,从而导致接收和接收消息的数量相等.消息.但是,当您的角色/线程/泵停止并重新启动时,即使没有找到消息,这也会触发新的接收.

I assume that a request is a poll on a queue / subscription, even if that didn't result in a message being pulled. With the OnMessage message pump model , you typically wait 'forever' until a message arrives, resulting mostly in an equal number of receives & messages. But when your role/thread/pump stops and restarts, that will trigger a new receive, even if no message was found.

这篇关于Azure服务总线:什么是“请求"和“消息"?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆