Is there any open source S3 compatible software? I know Riak Cloud Storage ( http://docs.basho.com/riak/cs/2.1.1/ ), but I think it’s not maintained anymore.
Object Storage: AWS vs Google Cloud Storage vs Azure Storage vs DigitalOcean
81–90 of 115 posts
Re: Object Storage: AWS vs Google Cloud Storage vs Azure Storage vs DigitalOcean
#82This is great, but I’m disappointed Backblaze B2 isn’t included. That seems like an oversight unless someone can point out how B2 doesn’t hold its own with these options in a glaring way. There are tradeoffs, but B2 seems to be very competitive overall. B2 is cheaper than every option here for both storage ($0.005/GB) and egress ($0.01/GB).[1] Their transaction pricing is also cheaper.[2] Despite being cheaper, it’s…
The world is not only Google, Amazon, Azure and DigitalOcean!
Re: Object Storage: AWS vs Google Cloud Storage vs Azure Storage vs DigitalOcean
#83Would be nice to add things like: - Consistency - First byte latency - Limits on requests - Max upload size - Extra features
Re: Object Storage: AWS vs Google Cloud Storage vs Azure Storage vs DigitalOcean
#84Cool site, but noticing an error: This compares AWS S3 single region pricing ($0.024/gb) to GCP GCS multi-region pricing ($0.026/gb) rather than GCP GCS single region pricing ($0.020/gb). Hopefully the creator/author will correct the discrepancy... Disclosure: I'm a pricing dweeb at Google Cloud
I sincerely hope your business card says "Pricing Dweep, Google Cloud Products". If not, you need to get this fixed.
Re: Object Storage: AWS vs Google Cloud Storage vs Azure Storage vs DigitalOcean
#85Re: Object Storage: AWS vs Google Cloud Storage vs Azure Storage vs DigitalOcean
#86Re: Object Storage: AWS vs Google Cloud Storage vs Azure Storage vs DigitalOcean
#87Earlier quoted context omitted.
I really wanted to like B2. I love the docs and super-clean interface. But B2 was just too "weird" when it came to uploading an object. You can't replace an object key, so you always get a new object key when uploading. This is unlike any normal object store, where you can just upload to an existing key. Also, if you upload an object with the same name (e.g. myphoto.png) it creates a new version, and there's no way t…
If you upload an object with the same 'name' to S3, you also get a new version. When you say 'key', do you mean the opaque object ID granted to objects in B2 which object stores like S3 doesn't have at all? I don't understand the rant here. S3 only operate by 'name' (key). I have had no problem integrating B2 side-by-side with S3 and GCP in the products I have written. Their high-level models are largely compatible.
Re: Object Storage: AWS vs Google Cloud Storage vs Azure Storage vs DigitalOcean
#88Earlier quoted context omitted.
What are bandwidth costs? This comes up again and again, people see HE.net / Cogent / Level3 / Hibernia / NTT whatever offering 10gig handoff IP transit at a colo neutral location for X per month and somehow determine the true cost. When I suspect the reality is that much of cost is invested in routing equipment both internally and externally, evolving SDN and all the goodness it affords, being able to offer SLA per…
I met a network engineer for amazon about a year ago and I brought up the prices since I had heard about them being expensive here on hacker news. He laughed about it and said it was one of their most profitable departments with like a 90% margin.
Re: Object Storage: AWS vs Google Cloud Storage vs Azure Storage vs DigitalOcean
#89Earlier quoted context omitted.
B2 is great as a backup store. I use it for backup. I wouldn't use it for non backup object storage, as it's in a single data center. S3 and Google Cloud are completely different, I'm not sure on the Google specifics but S3 has data replicated across three AZs.
Isn't backing up the last place where you want zero redundancy?
Re: Object Storage: AWS vs Google Cloud Storage vs Azure Storage vs DigitalOcean
#90Earlier quoted context omitted.
I really wanted to like B2. I love the docs and super-clean interface. But B2 was just too "weird" when it came to uploading an object. You can't replace an object key, so you always get a new object key when uploading. This is unlike any normal object store, where you can just upload to an existing key. Also, if you upload an object with the same name (e.g. myphoto.png) it creates a new version, and there's no way t…
If you upload an object with the same 'name' to S3, you also get a new version. When you say 'key', do you mean the opaque object ID granted to objects in B2 which object stores like S3 doesn't have at all? I don't understand the rant here. S3 only operate by 'name' (key). I have had no problem integrating B2 side-by-side with S3 and GCP in the products I have written. Their high-level models are largely compatible.