Live data from Hacker News

Google Storage Now Available To Developers

code.google.com

41–50 of 65 posts

Re: Google Storage Now Available To Developers

#41
post #33

Download data: $0.15 to Americas, Europe, the Middle East, and Africa $0.30 to Asia-Pacific So if a bunch of people from Japan decide to download from your app, you are screwed.

You're screwed if a bunch of people download from your app from anywhere, for sufficiently large values of 'bunch'.

Re: Google Storage Now Available To Developers

#43

Earlier quoted context omitted.

It probably wouldn't have worked out that way if Google didnt clone S3's API.

To be fair to Google, most of the S3 REST API is pretty obvious. Even if you'd never seen S3, you'd likely come up with an API that was 80% similar.

not the openstack storage api..

Re: Google Storage Now Available To Developers

#44
post #38
post #28

Earlier quoted context omitted.

Amazon was hardly a startup 5 years ago. And we're talking about a service and a space that's difficult to replicate and get into. S3 had resources most startups won't have to get that 5-year lead.

Amazon wasn't the "startup" in his example. His point was the 5 year wait time for a "giant"* to get a product out the door... * who, even worse for their case, already had the infrastructure, resources, engineers, etc. to get it done.

The point still stands; this isn't an example of why startups shouldn't fear giants/incumbents. Just because Google couldn't/chose not to get a product like Amazon S3 out the door to compete with Amazon, doesn't mean incumbents can't replicate and dominate a bootstrapped start-up's low-cost, innovative web app or mobile app.

The statement should say that startups with innovative, hard-to-reproduce products have nothing to fear; you'll either produce a product that they'll choose not to compete with/can't compete with (Twitter, Facebook) or get bought by them.

How many startups get killed because they can't compete with the big guys, though? Here's an example: http://family.go.com/assets/bubbleshare/

Re: Google Storage Now Available To Developers

#45

Earlier quoted context omitted.

Wait, who's the incumbent and who's the startup? Amazon was founded four years before Google...

I didn't mean it as an analogy, but there are plenty of examples if you are looking for Google vs startup. Twitter/Buzz, Groupon/Google Offers, Facebook/(Whatever Google's Social Strategy is). 5 years to clone a product that Google already has the infrastructure for and is within Google's core mission seems excessively long.

How is this within Google's core mission? Their mission is not to provide IT services to other companies...

Re: Google Storage Now Available To Developers

#46
post #45

Earlier quoted context omitted.

I didn't mean it as an analogy, but there are plenty of examples if you are looking for Google vs startup. Twitter/Buzz, Groupon/Google Offers, Facebook/(Whatever Google's Social Strategy is). 5 years to clone a product that Google already has the infrastructure for and is within Google's core mission seems excessively long.

How is this within Google's core mission? Their mission is not to provide IT services to other companies...

I'll spell it out very clearly:

Google's mission is "to organize the world‘s information and make it universally accessible and useful."

Gmail helps my company organize our email and communication, and makes it accessible from any computer anywhere in the world.

S3 helps my company organize our information and distribute it around the world.

S3 helps dropbox organize their users information and make it accessible from any device.

An S3 clone is clearly within Google mission.

Re: Google Storage Now Available To Developers

#47
post #40

Earlier quoted context omitted.

I just wish either one would support SSL for CNAMEd buckets.

That is a limitation of SSL. If you don't like it, ask your browser vendor to support section 3.1 of RFC 3546.

It should be possible via a combination of Amazon's elastic IPs and the SSL offloading that their ELBs already do.

Re: Google Storage Now Available To Developers

#48

Earlier quoted context omitted.

To be fair to Google, most of the S3 REST API is pretty obvious. Even if you'd never seen S3, you'd likely come up with an API that was 80% similar.

not the openstack storage api..

What do you mean? I haven't looked into Openstack in great deal, but my impression of the storage API was that it was very similar to S3, aside from how it handles authentication.

Re: Google Storage Now Available To Developers

#49
post #45

Earlier quoted context omitted.

How is this within Google's core mission? Their mission is not to provide IT services to other companies...

I'll spell it out very clearly: Google's mission is "to organize the world‘s information and make it universally accessible and useful." Gmail helps my company organize our email and communication, and makes it accessible from any computer anywhere in the world. S3 helps my company organize our information and distribute it around the world. S3 helps dropbox organize their users information and make it accessible fro…

Gmail is a product, S3 is a piece of infrastructure used by other products.

Google's mission is also to make money, companies make money by focusing on their core strengths. I would rather have Google not clone other people's products, Microsoft did that and they failed over and over again.

S3 may help you organize your information, but that information is probably not public, and if it is then Google's services can access it anyway - they also aren't a charity - if you're looking for charity (i.e. products released for the betterment of the world only) then you need to search for non-profits.

Re: Google Storage Now Available To Developers

#50
post #32
post #30

Earlier quoted context omitted.

Another good reason for certain use cases is its support for resumable uploads: http://code.google.com/apis/storage/docs/developer-guide.htm... Afaik S3 can't do that.

No, S3 (essentially) can as well: http://aws.typepad.com/aws/2010/11/amazon-s3-multipart-uploa...

Multipart uploads only sort-of address this. For one thing, the minimum "part" size is 5MB, so you can only resume at 5MB boundaries (or whatever part size you use). You also have to manage more state yourself.
Post reply on HN