Engineering costs of changing storage providers The broad adoption of the S3 API by developers in their codebases and internal systems has transformed the S3 API into what WebDAV promised us to be: de facto standard HTTP File Storage API. However, Amazon S3 has remained a dominant player despite heavy competition and not being the most cost-effective player. It could be integrated into any application but there was one catch: you couldn’t use any existing standard such as WebDAV, FTP or SMB: your application needed to interface with Amazon’s bespoke S3 API.įast forward to 2020 and the storage provider landscape has become highly competitive with many providers capable of providing petabyte (and exabyte) scale content storage at extremely low cost-per-gigabyte. AWS launched to help eliminate this model by renting their physical computing and storage infrastructure.Īnnouncing updates to the AWS Well-Architected FrameworkĪmazon Simple Storage Service (S3) led the market by offering a scalable and resilient tool for storing unlimited amounts of data without building it yourself. Prior to 2006, before the mass migration to the Cloud, if you wanted to store content for your company you needed to build your own expensive and highly available storage platform that was large enough to store all your existing content with enough growth headroom for your business. History of the S3 APIįirst let’s dive into the history of the S3 API and why it’s important for Cloudflare users. We are excited to see Backblaze introduce a new level of compatibility in their Cloud Storage service. Backblaze has been a proud partner since 2018.
As a refresher, the Bandwidth Alliance is a group of forward-thinking cloud and networking companies that are committed to discounting or waiving data transfer fees for shared customers.
In May 2020, Backblaze, a founding Bandwidth Alliance partner announced S3 compatible APIs for their B2 Cloud Storage service. Post Syndicated from Tim Obezuk original
0 kommentar(er)
