How many requests per min we can make to send messages api call for a notification hub ?

Question

Hi,

We are planning to use notification hub as our notification service. We have a bit complex use case where it is really hard for us to keep on updating tags of an installation object. The other possible solution for us is to associate a unique identifier as a tag to each user's installation object and using this identifier as tag we intend to send notifications. With this approach comes a problem. That is we might end up making millions of request on 'send messages endpoint' (POST https://{namespace}.servicebus.windows.net/{NotificationHub}/messages/?api-version=2015-01) of notification hub. We tried to dig into the documentation but could not find any conclusive answers on the following questions.

1. Is there a rate limit on send message api ?
2. Is it dependent on the tier we have selected ?
3. Will the limit be based upon calls made from a notification hub, namespace, resource group or subscription?

It will be really helpful if we can get exact number for the above.

Answer 1

Apologies for late response on this, The discussion with PG has led to that we do not officially publish throttling limits as they are subject to change without notice. In general you can expect:

1. 20000 per minute for Basic SKU, 200000 per minute for Standard SKU
2. Yes, Standard have 10x more capacity
3. The limit is counted per namespace

If you have individual sends per customer and must already maintain per customer identifier, you can use our Direct Send API.

It has 100k and 1M per minute limits for Basic and Standard SKUs and in general is much faster (sub 1 second 99% of time).

Please let us know if further query on this.