Live data from Hacker News

Show HN: Amazon S3, Microsoft Azure, Rackspace, Backblaze via a Single API

cloudrail.com

11–20 of 69 posts

Re: Show HN: Amazon S3, Microsoft Azure, Rackspace, Backblaze via a Single API

#13

No monthly fees, support open source: http://jclouds.apache.org/ Wouldn't surprise me if that's what they're using behind the SaaS

Nope, we don't use it but it is a very cool project. We have SDKs for Android, Objective-C, Swift, Java and Node.js so far. That's why we couldn't us it anyways. We don't want to compete with open source projects like this. Our goal is to offer easy integrations for all platforms and all major use cases (not only cloud storage). Btw, to support open source, we made our solution free for non commercial projects.

Re: Show HN: Amazon S3, Microsoft Azure, Rackspace, Backblaze via a Single API

#15
Do all these services provide equivalent or abstractable guarantees? Amazon S3, for example, provides 'read-after-write' consistency, meaning once you've received a positive response to a put operation, you can expect to be immediately able to retrieve that object. But it used to be 'eventually consistent', meaning it was possible to receive a positive response to a put, but then not be able to read the object immediately after.

Similar guarantees are needed around how soon after deleting something can readers expect to get 404s.

If these guarantees differ, you might find abstracting over the stores doesn't work the way you'd like...

Re: Show HN: Amazon S3, Microsoft Azure, Rackspace, Backblaze via a Single API

#16

Do all these services provide equivalent or abstractable guarantees? Amazon S3, for example, provides 'read-after-write' consistency, meaning once you've received a positive response to a put operation, you can expect to be immediately able to retrieve that object. But it used to be 'eventually consistent', meaning it was possible to receive a positive response to a put, but then not be able to read the object immedi…

Very good question. Of course all services behave a little differently which is out of our control. To be honest, I don't have an exact answer on that. In my first tests I could chain a download directly after the upload with all services. But I don't know if that's because they're all guaranteed to be read-after-write or some were eventually-consistent just really fast. In general, if one service is read-after-write and you want to switch it for one that isn't you might get problems, unless you've programmed defensively (checking for existence before proceeding). Give us some time to check that and run some more tests.

Re: Show HN: Amazon S3, Microsoft Azure, Rackspace, Backblaze via a Single API

#17

Do all these services provide equivalent or abstractable guarantees? Amazon S3, for example, provides 'read-after-write' consistency, meaning once you've received a positive response to a put operation, you can expect to be immediately able to retrieve that object. But it used to be 'eventually consistent', meaning it was possible to receive a positive response to a put, but then not be able to read the object immedi…

S3 only has read-after-write consistency for PUTs to new objects (not overwrites), and if you do a HEAD/GET before the PUT that degrades into being eventually consistent.

http://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction....

Re: Show HN: Amazon S3, Microsoft Azure, Rackspace, Backblaze via a Single API

#19
The Rackspace API is OpenStack Swift, a project used by many more public and private cloud providers than just Rackspace.

I've been working on Swift for the past 6 years, and I'd be happy to help with your OpenStack Swift API integration. See my profile for contact info.

Post reply on HN