Feature Request: Logic segregation / grouping for messaging entities

[epomatti]

It would be beneficial for some projects to have the option to organize entities in groups or domains, as opposed to using a flat structure. This is the equivalent maybe of a vhost. A common workaround is to add a prefix or multiple prefixes to express that hierarchy in a flat model.

Today:

• customerA-invoice-queue
• customerB-invoice-queue

Proposed:

• CustomerA
  • invoice-queue
• CustomerB
  • invoice-queue

Probably within this model, permissions, analytics, and other features could be integrated as well to give sort of like a control plane for each domain. This could be an optional feature when creating the namespace.

As another workaround, some teams create multiple namespaces but that adds unwanted complexity, and that approach is sometimes prohibitive when using Premium (which some are required to not because of throughput requirements, but due to ever growing security compliance rules such as private-only access).

[SeanFeldman]

This already exists (to an extent) with Azure Service Bus when you create a queue or a topic name with the path delimited by "/".

[epomatti]

@SeanFeldman

I get this with the web explorer, which is official. We also rely on Linux desktop.

[SeanFeldman]

This has nothing to do with the clients as it's a server side feature. You asked for it and I merely pointed out that partially it's already there.

[epomatti]

I can't find this in the documentation. Can you link it to me where this feature is explained?

I'm more interested in the functionality around it, as in the analogy that I've made with the virtual host.

[SeanFeldman]

@EldertGrootenboer I can't locate the official docs on the topic. Is it no longer around?

[EldertGrootenboer]

This is still supported, and for example described on https://learn.microsoft.com/en-us/rest/api/servicebus/addressing-and-protocol. I will open an investigation item to check if we can make this clearer in the portal UI.

[epomatti]

@EldertGrootenboer nice, and perhaps the current list view could still be kept, but have an additional hierarchical tree view, or something along those lines.

[EldertGrootenboer]

Thank you for your feedback on this item, it helps us in our efforts to continuously prioritize the different requests we get from all our various feedback channels. We have added this feature in our backlog, however we currently don't have an ETA on when development might start on this. For now, to help us give this the right priority, it would be helpful to see others vote and support this feature, as well as explain their scenarios.

[EldertGrootenboer]

This feature in our backlog, however we currently don't have an ETA on when development might start on this. For now, to help us give this the right priority, it would be helpful to see others vote and support this feature, as well as explain their scenarios.