Error 503: Exceed queue limit number of transaction
Partition the messages between multiple queues.
Premium tier Redis caches support deployment within a VNet
Must deployed as the only resources in a separate subnet.
Access Azure tables directly using the following format with OData protocol
Ensure lead from Service Bus queue is processed no more than once
Call Complete() or CompleteAsync() when worker process finished processing a lead.
When create a MessageReceiver, the default mode is PeekLock mode. In this mode, when a message is retrieved for processing from the queue, it remains in the queue but locked. When MessageReceiver finishes processing, it should call Complete() or CompleteAnsyc() so that message is removed from queue.
This is a robust approach – if MessageReceiver fails, message remains in the queue and the lock will expire by default after 1 minute. The message will be processed by another MessageReceiver or when the failed receiver restarts.
Set MessageReceiver receive mode to ReceiveAndDelete
Messages are deleted from the queue as soon they have been retrieved by MessageReceiver.
This is not robust – if MessageReceiver fails, messages can be lost and never processed.
RESTful query that retrieve number of throttled request each hour
- SVRBSY – return number of requests that were throttled because the server was busy.
- Rollups – duration over which metric should be aggregated.
- PT1H – specifies data should be summarized for each hour.
Standard tier service bus namespace – supports publish/subscribe feature
Could store file in blob storage and configure a shared access signature to allow subscribers access actual file. The message would contain URL to the blob.
Verify ID token was acquired by user after completing Azure AD B2C sign in policy.
Check Authentication Content Class Reference (acr) claim. – Azure AD B2C use this claim to record the name of the policy the user completed to acquire the token.