It requires Amazon to have a massive and expensive choke point in their network: load balancers. The interface to upload data into Amazon S3 is actually a bit simpler than Backblaze B2’s API. Uploads (Load Balancing vs Contract Architecture) The easiest way to understand B2’s Contract Architecture is to deep dive into how we handle the Upload process. To understand what we’re doing, I’d like to introduce the concept of Backblaze’s “Contract Architecture.” My assertion is that a 2 step architecture is ~60% simpler than having a 5 step approach. B2’s architecture enables secure authorization in just 2 steps.
The 5 step approach for S3 is well outlined here. If the detail is of interest, I’m happy to get into that on a later post or answer questions in the comments below.īackblaze and Amazon did take different approaches to how each service handles Authorization. Fundamentally, we ended up having similar approaches when solving those challenges. The comparison between B2 and S3 on the List and Download functions is, candidly, not that interesting. List - Data checking/selection/comparison.Authorization - Providing account/bucket/file access.Throughout cloud storage, S3 or otherwise, APIs are meant to mainly provide access to four major underlying functions: The Four Major Functions of Cloud Storage APIs The quick answer to either question? So our customers and partners can move faster while simultaneously enabling Backblaze to sustainably offer a cloud storage service that is ¼ of the price of S3.īut, before we jump all the way to the end, let me step you through our thinking. When we get asked, “why did Backblaze make its own set of APIs for B2,” the question behind the question is most often “why didn’t Backblaze just implement an S3-compatible interface for B2?”Įither are totally reasonable questions to ask.
0 kommentar(er)
