Managing multiple azure bursts

Question

Part of my application includes a chat system. I maintain a queue for each user. Messages for the user are queued, and user software periodically examines the recreation service for new messages, after which the queue is downloaded for messages, and they are returned to the user.

The system is very simple, works well and does everything I need.

My problem; I have hundreds (and soon thousands) of queues cluttering the list of queues for the application.

I have other queues, and it bothers me that I cannot "organize" them, as I can, with things in the blob repository.

Am I missing something or should I just ignore the queue list and rely on the fact that I correctly manage the creation and deletion of queues when users come and go?

Answer 1

I would simply ignore the fact that the list is cluttered. Blobs live in containers, but there is no container in the queues. All one flat list.

If you want to somehow request the queues, a flat list should not bother you. If you need to query the queues (for example, "last use" or something like that), you probably need to save a table with a list of queues and some of their properties to simplify the query.