Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

cloudrail.com

Post reply on HN
Print view View original

31–40 of 69 posts

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

#31

Post by okreallywtf »

tmm_ wrote: post #6
kierenj wrote: post #4

It's a nice feature-set, looks well-designed, and handy - but anyone using one of these APIs would find it super trivial to implement this themselves? I'm not sure I see the cost-benefit making sense here? I'm keen to be convinced, though - what's the killer use case? (I'm not aware of APIs changing or being deprecated in any big way) Edit: ah, the other APIs make way more sense to me. You can offer multiple options…

This allows you to easily integrate multiple of these providers if necessary or easily switch. Of course you can integrate them one by one on your own but that takes a lot of time time. With CloudRail it's one API which works even cross platform. Our ultimate goal is to handle all your integrations and not only cloud storage. So unified APIs for fast API integrations and API Change Management to keep your integration…

Can you provide a use-case for when you would need to be able to easily switch (or potentially hot-swap) cloud storage? It sounds like some of the justification for ORM's; while it would be nice to have if it took no more time to integrate with that API its hard for me to see how it could justify extra effort in implementation/maintenance unless you have a concrete understanding of when you need it.

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

#32

Post by reilly3000 »

tmm_ wrote: post #3

This is our brand new unified API for enterprise cloud storage providers. It's part of the CloudRail API Integration Solution which consists of multiple unified APIs for different categories like social, payment, consumer cloud storage etc. Our value props are: A single API for multiple providers & No API changes since we keep the integrations up-to-date. All that without a hosted middleware. So we never touch the da…

Looks like a handy set of tools. Check the spelling of 'Download' on the linked page :)

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

#33

Post by reilly3000 »

tmm_ wrote: post #3

This is our brand new unified API for enterprise cloud storage providers. It's part of the CloudRail API Integration Solution which consists of multiple unified APIs for different categories like social, payment, consumer cloud storage etc. Our value props are: A single API for multiple providers & No API changes since we keep the integrations up-to-date. All that without a hosted middleware. So we never touch the da…

Looks like a handy set of tools. Check the spelling of 'Download' on the linked page :)

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

#35

Post by tmm_ »

reilly3000 wrote: post #32
tmm_ wrote: post #3

This is our brand new unified API for enterprise cloud storage providers. It's part of the CloudRail API Integration Solution which consists of multiple unified APIs for different categories like social, payment, consumer cloud storage etc. Our value props are: A single API for multiple providers & No API changes since we keep the integrations up-to-date. All that without a hosted middleware. So we never touch the da…

Looks like a handy set of tools. Check the spelling of 'Download' on the linked page :)

Thanks. I'll correct that typo asap but currently I don't want to clear the cache :)

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

#36

Post by kevan »

jamesblonde wrote: post #30
Scaevolus wrote: post #17

Earlier quoted context omitted.

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....

It's so bad that big companies, like Netflix, have to write a whole service to store a copy of the s3 metadata: http://techblog.netflix.com/2014/01/s3mper-consistency-in-cl... Netflix have turned the S3 metadata eventually consistent problem into s3mpr metadata eventually consistent problem. The difference is that they can now inspect and reason about s3mpr's metadata. Spotify have had to do the same thing for Google…

>I can't help wonder if eventually consistent object stores will go the way of NoSQL databases, when a consistent, scalable hierarchical filesystem appears.

Of course they will. Eventual consistency is a huge tradeoff that I don't think anyone would make if they weren't forced to.

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

#37

Post by jamesblonde »

kevan wrote: post #36
jamesblonde wrote: post #30

Earlier quoted context omitted.

It's so bad that big companies, like Netflix, have to write a whole service to store a copy of the s3 metadata: http://techblog.netflix.com/2014/01/s3mper-consistency-in-cl... Netflix have turned the S3 metadata eventually consistent problem into s3mpr metadata eventually consistent problem. The difference is that they can now inspect and reason about s3mpr's metadata. Spotify have had to do the same thing for Google…

>I can't help wonder if eventually consistent object stores will go the way of NoSQL databases, when a consistent, scalable hierarchical filesystem appears. Of course they will. Eventual consistency is a huge tradeoff that I don't think anyone would make if they weren't forced to.

Maybe something like this - 1 million ops/sec on HDFS: http://www.logicalclocks.com/index.php/2016/10/14/hops-smash...

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

#38

Post by yandie »

kevan wrote: post #36
jamesblonde wrote: post #30

Earlier quoted context omitted.

It's so bad that big companies, like Netflix, have to write a whole service to store a copy of the s3 metadata: http://techblog.netflix.com/2014/01/s3mper-consistency-in-cl... Netflix have turned the S3 metadata eventually consistent problem into s3mpr metadata eventually consistent problem. The difference is that they can now inspect and reason about s3mpr's metadata. Spotify have had to do the same thing for Google…

>I can't help wonder if eventually consistent object stores will go the way of NoSQL databases, when a consistent, scalable hierarchical filesystem appears. Of course they will. Eventual consistency is a huge tradeoff that I don't think anyone would make if they weren't forced to.

Then you trade availability with consistency. No system can't escape CAP

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

#40

Post by tmm_ »

jsiepkes wrote: post #20

Isn't this what Hashicorp's Terraform also provides?

As I understood it, it is more a solution for dev-ops to create the infrastructure. Like a provider agnostic CloudFormation. CloudRail is about making it super simple to integrate APIs into an app.
Post reply on HN