Conventional wisdom for Apache’s high-performance, scalable database has been to avoid wide partitions for risk of impacting database performance and storage limitations. Backblaze’s work with a Cassandra consultant shows how version 3.11 can dramatically decrease garbage collection, lower latencies, and require nearly 30% less space when using wide partitions versus version 2.2.
Today we are announcing that beginning immediately, Backblaze B2 customers will be able to download data stored in B2 to Cloudflare for zero transfer fees. This means that customers can save up to 75% on storage versus Amazon S3 to store their content in the cloud and deliver it worldwide.
Version 2 of the Backblaze B2 API brings a number of enhancements. While existing applications using version 1 of the API will continue to function as before with no changes required, we encourage developers to try out the version 2 beta and submit comments to us.
In a guest post, John Matze, founder of BridgeSTOR, outlines the differences for application developers between S3 and B2 APIs, and concludes that adding B2 support is not a major job.
It’s been three years since the launch of Backblaze B2 Cloud Storage and the B2 developer community is strong and growing. In this post we survey what developers are doing with B2 and some of the many tools and resources available to developers.
If you get a 503 or 500 server error it does not mean that the B2 service is down. It simply means that B2 is functioning as designed. Let’s look at the process.
We’re often asked why Backblaze didn’t implement S3-compatible APIs for our B2 Cloud Storage. Here are the reasons why we believe our approach has advantages over Amazon’s APIs and enables us to offer our cloud services at lower cost than our competitors.
It’s been a few months since our last “What’s New In B2” blog post, so we wanted to highlight the latest B2 developments, which include new application keys, our Java SDK, and B2 compute partnerships with Packet and ServerCentral.