Blob API and Volatile Blob API

These APIs are optimized for high load and high-throughput workflows. To achieve ultimate performance, applications should use multiple connections to retrieve or upload data in parallel. We recommend using a pool of HTTP connections and re-using each connection for multiple requests.


To maintain reasonable quality of service (QoS), Blob API will reject slow write requests with the HTTP 408 Request timeout status code if the average upload speed is lower than 50 kB/sec. This could be especially an issue when working with Data API in China region.

Additionally, when dealing with batch and streaming workloads, it is hard to anticipate a “traffic spike” of a sudden surge in demand, typically more than doubling existing traffic levels in a very short period of time. To continue functioning and meet the existing service level agreement (SLA), the system can return HTTP 429/503 status codes for short periods of time (usually up to 10 minutes) and throttle requests from one or more users while it adapts to new request rates.

results matching ""

    No results matching ""