Backblaze Rate Limiting Policy for Consistent Performance
Backblaze has introduced a rate limiting policy for its B2 Cloud Storage to manage API usage, prevent performance issues, and ensure equitable access for all customers, adjusting limits based on feedback.
Read original article
Backblaze has introduced a new rate limiting policy for its B2 Cloud Storage platform to enhance performance and manage customer usage effectively. This policy aims to prevent unexpected spikes in API usage by setting specific thresholds for call and byte rates. If these limits are exceeded, customers will receive a 503 status code for the S3 compatible API or a 429 status code for the Backblaze B2 native API. The policy is designed to ensure that all customers can access high-performance storage without disruptions caused by excessive usage from any single customer. Default rate limits will vary based on account history and usage patterns, with new customers starting with lower limits. Customers with larger datasets or those who have received sales assistance may qualify for higher or custom limits. Backblaze plans to adjust these limits over time based on traffic analysis and customer feedback. The policy does not apply to Backblaze Computer Backup usage. Customers are encouraged to consult the API documentation for more details and to reach out to support for assistance with rate limits tailored to their needs.
- Backblaze has implemented a rate limiting policy for its B2 Cloud Storage platform.
- The policy aims to manage API usage and prevent performance issues caused by spikes.
- Customers will receive status codes if they exceed their rate limits.
- Default limits vary based on account history, with new customers starting with lower thresholds.
- Backblaze will adjust limits over time based on usage patterns and customer feedback.
Related
Backblaze Drive Stats for Q2 2024
Backblaze monitored 284,876 drives in Q2 2024, reporting an annualized failure rate of 1.71%. Two models had zero failures, and the company is exploring AI for predicting drive failures.
Backblaze Drive Stats for Q2 2024
Backblaze analyzed 284,876 drives in Q2 2024, reporting an annualized failure rate of 1.71%. Notable findings included zero failures in two Seagate models and concerns over the 12TB HGST drive's rising failure rate.
Behind AWS S3's Scale
AWS S3, launched in 2006, supports 100 million requests per second, stores 280 trillion objects, utilizes over 300 microservices, and offers strong durability and data redundancy features for cloud storage.
Btrfs2s3 maintains a tree of incremental backups in an S3-compatible API
btrfs2s3 is a tool for managing incremental backups of Btrfs filesystems to S3-compatible cloud storage, offering automatic backup management, cost efficiency, and planned future enhancements for improved functionality.
Support for IPv6
Backblaze has launched IPv6 support for its S3 Compatible API to enhance network performance and accommodate more devices, while still supporting IPv4 during the transition. Future expansions are planned.
3 comments-> This policy is limited to Backblaze B2 Cloud Storage usage. Backblaze Computer Backup usage is not within the scope of this policy.
-> Customers storing 10TB or below will initially be provisioned for uploads up to 3,000 requests per minute and 800 megabits per second, and for downloads up to 1,200 requests per minute and 200 megabits per second, all per account. Other API operations may also be limited to keep traffic flowing, but again, this won’t be noticeable to most customers.
-> Customers storing more than 10TB, including all sales assisted customers whom we’ve supported during implementation and/or renewal, will experience no change at this time.
-> Traffic analysis and engineering is a dynamic activity, so we’ll likely revise limits over time in response to evolving usage patterns, improvements we roll out, and, of course, customer feedback. We will announce significant changes here on the blog.
Hope that clears things up and we have additional documentation on our API Documentation pages: https://www.backblaze.com/apidocs.
Our production web app can easily makes more than 20 requests for images per second on the initial page load for a single user. B2s new 20 requests per second cap means that it will just take one person viewing to cause anyone else also trying to view the app at that second to get an empty white screen. Cloudflare cache will only mitigate this so much.
Anyone got non Amazon suggestions to migrate to ASAP?
Related
Backblaze Drive Stats for Q2 2024
Backblaze monitored 284,876 drives in Q2 2024, reporting an annualized failure rate of 1.71%. Two models had zero failures, and the company is exploring AI for predicting drive failures.
Backblaze Drive Stats for Q2 2024
Backblaze analyzed 284,876 drives in Q2 2024, reporting an annualized failure rate of 1.71%. Notable findings included zero failures in two Seagate models and concerns over the 12TB HGST drive's rising failure rate.
Behind AWS S3's Scale
AWS S3, launched in 2006, supports 100 million requests per second, stores 280 trillion objects, utilizes over 300 microservices, and offers strong durability and data redundancy features for cloud storage.
Btrfs2s3 maintains a tree of incremental backups in an S3-compatible API
btrfs2s3 is a tool for managing incremental backups of Btrfs filesystems to S3-compatible cloud storage, offering automatic backup management, cost efficiency, and planned future enhancements for improved functionality.
Support for IPv6
Backblaze has launched IPv6 support for its S3 Compatible API to enhance network performance and accommodate more devices, while still supporting IPv4 during the transition. Future expansions are planned.