本质上,我们希望创建逻辑应用程序(每分钟很多),以创建计划的触发器,以将消息拖放到服务总线上,并在不再需要这些逻辑应用程序时将其删除.
We essentially want to create logic apps(many per minute) to create scheduled triggers to drop messages on service bus and delete these logic apps when they are no longer needed.
推荐答案
对于每个订阅和租户,资源管理器将读取请求限制为每小时15,000,将写入请求限制为每小时1,200.这些限制适用于每个Azure资源管理器实例.有每个Azure区域和Azure资源管理器中有多个实例部署到所有Azure区域.因此,在实践中,限制是有效地比上面列出的要高得多,因为用户的要求是通常由许多不同的实例提供服务.+
For each subscription and tenant, Resource Manager limits read requests to 15,000 per hour and write requests to 1,200 per hour. These limits apply to each Azure Resource Manager instance; there are multiple instances in every Azure region, and Azure Resource Manager is deployed to all Azure regions. So, in practice, limits are effectively much higher than those listed above, as user requests are generally serviced by many different instances.+
如果您的应用程序或脚本达到了这些限制,则需要限制您的请求.
If your application or script reaches these limits, you need to throttle your requests.
来自此处.
HTH
更多推荐
可以在资源组/订阅中创建的Azure逻辑应用程序的数量上限?
发布评论