I'm considering an architecture that could have tons of subscribers to a single topic. Like tens or hundereds of thousands of individual subscribers. Each would have a SQL filter, something like:
User = 'SomeUserIdentifier'
Just wondering if I'm going to run into a max number of subscriptions on a topic at some point.
Service Bus messaging services (queues and topics/subscriptions) allow application to send messages of size up to 256 KB (standard tier) or 100 MB (premium tier).
Maximum delivery countThe default value is 10. Whenever a message has been delivered under a peek-lock, but has been either explicitly abandoned or the lock has expired, the delivery count on the message is incremented. When the delivery count exceeds the limit, the message is moved to the DLQ.
By default, a maximum of 50,000 Azure AD resources can be created in a single tenant by users of the Azure Active Directory Free edition. If you have at least one verified domain, the default Azure AD service quota for your organization is extended to 300,000 Azure AD resources.
A topic subscription resembles a virtual queue that receives copies of the messages that are sent to the topic. Consumers receive messages from a subscription identically to the way they receive messages from a queue.
Service Bus supports up to 2,000 subscriptions per topic. (source)
But if you need to go beyond the 2,000 subscriptions limit you can create multiple levels of subscriptions with the Auto-forwarding capabilities of a Subscription. This means you could have the following:
Topic A
This means you would have virtually no limit on the number of subscriptions you could have on a topic.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With