管理大量 Azure 队列
我的应用程序的一部分包括一个“聊天”系统。我为每个用户维护一个队列。发送给用户的消息被放置在队列中，并且用户的软件定期轮询休息服务以获取新消息，此时队列中会抽取消息，并将它们返回给用户。
该系统非常简单，运行良好，并且可以完成我需要它做的所有事情。
我的问题是；我有数百个（很快数千个）队列使应用程序的队列列表变得混乱。
我还有其他队列，令我不安的是我无法像处理 Blob 存储中的内容那样“组织”它们。
我是否遗漏了某些内容，或者我应该忽略队列列表，并依赖于我在用户进出时正确管理队列的创建和删除的事实？
Part of my application includes a "chat" system. I maintain a queue for each user. Messages to the user are placed in the queue, and the user's software periodically polls a rest service for new messages, at which point the queue is pumped for messages, and they are returned to the user.
The system is very simple, works well, and does all I need it to do.
My problem is; I have hundreds (and soon thousands) of queues cluttering up the queue list for the application.
I have other queues as well, and it's disconcerting to me that I can't "organize" them like I can with things in blob storage.
Am I missing something, or should I just ignore the queue list, and rely on the fact that I'm properly managing the creation and deletion of queues as users come and go?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我会忽略列表混乱的事实。 Blob 存在于容器中，但队列没有容器。一切都是一张简单的清单。
除非您想以某种方式查询队列，否则平面列表不会打扰您。如果您确实需要查询队列（例如“最近使用的”或类似的内容），您可能需要保留一个包含队列列表及其一些属性的表，以便于查询。
I would just ignore the fact that the list is cluttered. Blobs live in containers, but queues don't have a container. Everything's one flat list.
Unless you want to query the queues somehow, the flat list shouldn't bother you. If you do need to query queues (like "most recently used" or something like that), you'll probably need to keep a table with the list of queues and some of their properties to make it easier to query.