Earlier quoted context omitted.
Multiple facilities != "one datacenter"
Like I asked below, do you have a citation?
"No one data center serves two availability zones" :
http://www.theregister.co.uk/2015/04/16/aws_data_centre_arch...
Backblaze B2 Cloud Storage
71–80 of 237 posts
Re: Backblaze B2 Cloud Storage
#72Took a quick look at the API. For context, I was involved in the early days of Google Cloud Storage. It is surprising that they didn't make it compatible with the S3 API -- at least for common object/bucket create/delete. This will require more code to be written and it will be harder to adapt client libraries. The API documentation is here: https://www.backblaze.com/b2/docs/ Other notes: * The lack of scalable front…
> It is surprising that they didn't make it compatible with the S3 API .... The lack of scalable front-end load balancing is shown by the fact that they require users to first make an API call to get an upload URL And... you answered your own question. :-) We reduce our operating costs by not having as many load balancers in the datacenter and pushing off the responsibility to the API. It all comes from our tradition…
S3 compatible API is the only reason preventing us from migrating to your cheaper option right now.
Re: Backblaze B2 Cloud Storage
#73The price is being heralded as the thing to get excited about, but I'm also very concerned about the security and availability of my data. I suppose those details are somewhere, but they're not in this article which is quite lengthy. I would like to know more of the implementation of this and more information on policies to protect access to my data. And I would like to know where the data is stored. I suppose I got…
Brian from Backblaze here: We're really transparent about our redundancy and pretty much everything we do. We use 17+3 Reed Solomon across 20 computers in 20 different locations in our datacenter. You can read about it here: https://www.backblaze.com/blog/vault-cloud-storage-architect... You can also read about our "Backblaze Storage Pods" (the things filled with drives) here: https://www.backblaze.com/blog/storage-pod/
Also, we are the only company we know of that releases our drive failure rates. We release them quarterly, here is the most recent failure analysis: https://www.backblaze.com/blog/hard-drive-reliability-stats-...
Re: Backblaze B2 Cloud Storage
#74Are they using Ceph?
Re: Backblaze B2 Cloud Storage
#75Whether or not I decide to use this service, this is one of the most useful announcement blog posts I've read in a while. The tone is not just "ok we released this" but instead " we released this, and here are some practical use cases if you are already doing X, Y, or Z " -- nice job.
Yev from Backblaze here -> I cannot describe how pleased I am to read this comment. Thank you!
I want a way to be able to use this with ssh rsync scp and so on to preserve legacy backup routines that are now in place. (Including on systems that you will not be writing b2 clients for like old versions of Solaris).
Re: Backblaze B2 Cloud Storage
#76I'm thrilled that we can offer this raw cloud storage for just $0.005/GB/month. Would love to hear from the Hacker News community what you do with storage today & what you might do with B2. Here are my thoughts on our announcement today: https://www.backblaze.com/blog/b2-cloud-storage-provider/ Gleb
Is it me or there's no mention of durability?
Is this only for noncritical, reproducible data as S3 reduced redundancy?
Re: Backblaze B2 Cloud Storage
#77[deleted]
Re: Backblaze B2 Cloud Storage
#78Earlier quoted context omitted.
Like I asked below, do you have a citation?
"No one data center serves two availability zones" : http://www.theregister.co.uk/2015/04/16/aws_data_centre_arch...
Is there a reason you're focused on AWS topics and your account is only ~2 days old?
Re: Backblaze B2 Cloud Storage
#79Took a quick look at the API. For context, I was involved in the early days of Google Cloud Storage. It is surprising that they didn't make it compatible with the S3 API -- at least for common object/bucket create/delete. This will require more code to be written and it will be harder to adapt client libraries. The API documentation is here: https://www.backblaze.com/b2/docs/ Other notes: * The lack of scalable front…
> It is surprising that they didn't make it compatible with the S3 API .... The lack of scalable front-end load balancing is shown by the fact that they require users to first make an API call to get an upload URL And... you answered your own question. :-) We reduce our operating costs by not having as many load balancers in the datacenter and pushing off the responsibility to the API. It all comes from our tradition…
I, for one, prefer the directness of not having to go through a front-end proxy. It probably eliminates some failure modes. I think that, instead of Backblaze providing an S3-compatible API, someone should do an open-source S3-compatible front-end for B2, that any interested user can run on a cheap VPS.
Re: Backblaze B2 Cloud Storage
#80Earlier quoted context omitted.
> This is a feature for EU and US-West. US Standard is bi-coastal and doesn’t have read-after-write consistency. Quote from Jeff Barr @ AWS: http://shlomoswidler.com/2009/12/read-after-write-consistenc... .
Their documentation is really inconsistent on this...
I've emailed Jeff to get clarification on it.