Google to launch Amazon, Microsoft cloud competitor at Google I/O 2012
gigaom.com
gigaom.com
Hopefully it will not be just a half-assed experiment again.
Amazon is pretty unique in that they make a lot of their internals available as products, but even before that, the infrastructure was still impressive. What other online store do you use? :)
But of course, i probably use Amazon for 80% of my online shopping needs, they rock!
MS seems to use Dell (only link i could find): http://www.datacenterknowledge.com/archives/2008/10/28/dell-...
That's like saying that the Wii was produced by a card-game company, or that a wood pulp paper making company makes the Lumia 900.
Companies evolve; Amazon were experienced in managing a lot of servers, and where looking for ways to make money on that expertise (and on the less than 100% used server capacity, although I remember hearing somewhere that within 3 months of introduction, AWS required more server capacity than Amazon-the-store had at the time)
Google has plenty of horsepower to spare, sure, but their usage pattern is much more planned for and expected, so launching a cloud required carving out resources for it, while Amazon just had to make use of excess resources it couldn't find a better use for.
I think you cannot deny that Amazon had "less to work with" when they started then Google has today. In terms of experience.
I was criticizing your expression. Amazon had A9 search and other ventures before AWS - they were far from being "an internet shop" even back then.
> I think you cannot deny that Amazon had "less to work with" when they started then Google has today. In terms of experience.
Indeed, but there was also less expectation. There wasn't any real competition, so they could get away with a hell of a lot less than Google can get with today.
I couldn't find the original, so this is a copy on Google+. It discusses the difference in how Google and Amazon approach platforms.
Cloud computing is all about creating a good blend of technology and business. If you don't get the business off the ground, you won't have the stamina to seriously invest in the technology, particularly in terms of building lean, scalable operations. Building scalable systems is perhaps 1% inspiration (distributed algorithms), and 99% transpiration (cost-effective operations). If you don't get it right, you'll be looking at this big red number below the line and will have to kill it. The fact that Google is already huge does not matter that much, it's not being big that's hard, it's growing fast and staying afloat.
Indeed, Amazon is an Internet shop. They'll sell anything to anyone, anywhere, and they do so for ridiculously low margins. That's a mighty competitor to be up against. Google on the other hand has never been very successful outside of advertising, and have only been a high margin business.
Not saying that Google won't be successful in this space. If they're willing to lose money on it they could achieve a sizeable market share comparable to Microsoft's. They lack Microsoft's gigantic sales network, but make up for in developer goodwill. However, catching up with the lean operations machine of Amazon seems infeasible at this point. What they could do is focus on their core strengths and open up their massive data sets and tools for all to use. So far they have been very reluctant to do so however, afraid to harm their core business.
Android is the most widely-used mobile OS in the world. Shouldn't that count as a success?
Google had build a highly customized, scaling environment based on their own software layer instead of mere "linux boxes". And clearly it worked great for them. So that's basically what they offered with GAE.
But the problem in the market was that GAE was this weird custom thing, while Amazon was selling a "cloudy" version of the same environment all the developers were already using. So Amazon won -- the market wants linux boxes, even if they aren't as scalable or efficient uses of hardware as Google's stuff.
The point is: Amazon won by circumstance. They happened to have an internal product already that they could sell, and they did. Google had an internal product too, but for reasons beyond the control of its designers, it wasn't a good fit for the market. I don't think either of these has anything to do with being "great at doing business".
The thought of dealing with Amazon customer service fills me with warmth. The thought of dealing with Google customer service fills me with dread.
I love Google as long as everything is working, but they (still) really suck when you need to interact with them. And before anyone mentions it, yes, I know this is because "I am Google's product", not their customer, but ultimately that viewpoint seems to have become part of Google's culture and in many ways that does actually make them lesser than Amazon at "doing business", IMO.
They're going to need to turn this around if they want to compete with Amazon, who have been very accommodating and helpful to us, even going so far as to send engineers to our offices to help us with aspect of our architecture.
I wasn't making a GAE vs. AWS comparison though. GAE is not in direct competition with AWS. It's a product with a niche market and I wouldn't see it as a failure. It's just something else entirely than building an AWS competitor.
The argument I was making is that Google wouldn't necessarily have the experience in building a lean, scalable business operation that could successfully compete with Amazon Web Services. As a case in point, Google has been running an exact duplicate of Amazon S3 for a while now, but it has yet to really take off. http://cloud.google.com/products/cloud-storage.html
EC2 and S3 today are virtually identical to the services they launched with. I don't think reality bears out your contention.
You're right that they had to add EBS later, but I think if anything that supports my point: the ephemeral "instance store" model was too weird, and customers really wanted something that acted like a virtual hard drive with persistent storage.
+1, no one ever seems to realize how important this aspect is. "Cloud" providers aren't competing with some fat margin software corp. AWS is a billion dollar business who's used to 1% margin, sinks 100s of millions in infrastructure, and is insulated from a lot of business pressures. Oh, and they control the vast majority of your market. That sounds like a pretty scary competitor.
And that sentiment is _exactly_ why I won't trust my business to whatever they come up with. There's no knowing how seriously and committed they are. Sure, Amazon could do an about face, but they don't have that history, so I'm more comfortable trusting them.
I have to guess that it's that people are comfortable with EC2 (I am -- great service) and almost want to hope-away anything that degrades the value of the thing that they do know.
An absence of competition is a near certain way to gain market share, but the easy way is not the only way. If you have a good enough product you can steal business from the competion and even grow the size of the total market (as was the case with the ipod and iphone).
People still think the same sorts of thoughts today, as we've seen, and they are no more correct.
I really hate how confident tech people about shit they've never done and/or just read about on blogs. I understand that apparent confidence is a currency but it's not the only one.
You can do DNS based failover (short TTL), manually or automatically, and it's the easiest to set up using entirely your own infrastructure. This works great if you can tolerate a variable length outage for customers, or where you're not using it to deal with outage, but rather just migrating load -- say provider A suddenly gets expensive, you can migrate away, but don't need to hard kill provider A, at least until any DNS cache has expired.
You can do IP based failover (various techniques -- anycast, which doesn't really work for most apps, making your own announcements of the same netblock, IP address failover below the BGP level/internal to a network, arp stealing on a subnet (not useful across providers but good for HA), etc.
You can use a smart proxy in front of your app (an F5 "Global Load Balancer", something you've developed yourself, nginx with minimal state, or an inexpensive service like Cloudflare or their 1000x more expensive Prolexic competition).
You can do the best thing for non-web apps, a smart client, which knows to go down a list of servers (randomly?) and find the closest or best one. More intelligence in the client = more better.
I've set up all of these except Anycast (which I'd actually love to do sometime, but RIPE jacked my /24) and Prolexic (because I don't want to spend $30-100k/mo). Which is the best really expends, but IMO at least having a plan (even if it takes a week) to switch hosting providers is worthwhile for everyone.
And yes, being more precise is necessary when you are critiquing someone.
Yes, certainly there are other options that increase the complexity, but why not start there? While the impact to users on shitty ISPs or behind proxies is unfortunate, it is relatively easy to implement and low-cost.
Going beyond that increases the complexity and cost exponentially and is certainly not easy.
Unfortunately some stupid resolvers cache a single answer set for a long time, but for some applications, you're willing to accept 1/x of attempts fail during an outage (just hit reload, or come back in a bit), since this costs ~nothing to implement.
The basic concept works great for NS, MX, and other protocols where they're designed to retry.
The best system today is probably to host at a facility with great transport to Amazon Direct Connect nodes (e.g. SV1/SV5 in Silicon Valley -- I'm setting this up now), so you've got fast cheap ways to keep your databases replicated between AWS and the free world/your own colo.
For inbound traffic, for $20/mo, I'd just do Cloudflare; for higher end, you'd have a lot of choices to make. (I haven't tried the higher end cloudflare offerings yet; they do seem to address most of the shortcomings, and are still pretty cheap).
App Engine is often criticized for being expensive compared to AWS, but putting together a production ready setup (i.e., automatic failover in the case of data center failure) on AWS isn't cheap since you need at least two of everything: multiple EC2 instances sitting behind a load balancer (ELB) and redundant databases (i.e., RDS Multi-AZ). I know because I'm setting up exactly this configuration right now for my DNS hosting service (http://slickdns.com).
But if Google's IaaS offering could fix all the fiddly bits that App Engine currently doesn't do (e.g., custom SSL, native binaries) it would surpass AWS in terms of functionality.
Selling bandwidth and white-label servers is easy. Building a production ready arbitrarily scalable web platform is much harder.
Google's customer service, in contrast, has a raison d'etre of avoiding customers. As a customer, the feeling you get is mild disdain. This is necessary -- one support call for Google.com can wipe out the profits from thousands of people. This translate into how they handle the enterprise market. I use Google Apps for my organization. I needed to enable Google+ for a social presence. This required applying into a black hole which, for a long time, did nothing. Support e-mails went to someone who clearly was in the business of neither having nor giving out information.
Here's an experiment for you: Pretend you want to try Google App Engine, but your cell is not on one of the providers Google supports (I've been there). You just a credit card, and a willingness to spend a bit of cash. Try to buy some service. See how far you get.
I use Google internal to my organization for things like Google Apps; if it has issues, employees will deal, and it saves a big chunk of work and cash. For anything customer-facing, I really do want a partner whom I can talk to if there are issues, not a black box designed to reject support requests.
Do they mean azure? That's IaaS, right?
GAE forces profound vendor lock-in relative to AWS, which is itself already guilty of this compared to a normal infrastructure solution.
Myself, I prefer something like gondor.io, that looks very much like a dedicated server but also has zero setup/administration.
If price is an issue, you can't beat an actual dedicated server, though.
"their java/python..."
Yes, Google's version of Java. Not JDK/JEE.
If they are expanding their offerings it might go more towards Box(.net) than vs Amazon
By that also the App Engine etc fit into the picture - we'll know next week
"It's the system that manages machines. If you want to run a program that uses x CPU and y memory on 100 machines, you don't specify which machines to run it on. Instead, you request 100 machines using a Borg library."
Also, the rest of the time.
That's a tall-order. $40/mo for a 1gb VPS is attractive.
I think the parent post has a valid point. It is harder to enter market now than it was 4 years ago. Not impossible but much much harder.
No-one needs persuading that they need cloud servers now. If Google can produce a a)better, b)cheaper or even c)different service then they've got customers.
There's an even bigger problem as well. Google hurt their reputation as a hosting provider when they significantly raised their rates without advanced notice. Companies want to know what their costs will be, and want to know that someone will answer their questions if they have support issues. Google has a negative reputation in both areas.
Google has enough resources to enter a market like this and have some instant credibility. We've seen it with Gmail, Google Maps, and many of their other services.
Dropbox may be popular but it's still not mainstream.
Heroku's market is still very young.
AWS is probably used by just half of the startups I know. But Linode & Rackspace are pretty big too.
AWS is morphing very quickly into a true end to end PaaS. Big difference. And it's hard to see who can compete with them.
With other aspects of PaaS, Amazon is still gaining ground. SendGrid is probably the leader in mail services.
The market as a whole is still very young. It's very short-sighted to say that Google won't be able to compete with Amazon. And besides, do you actually have full knowledge of what Google is going to release?
Cloud services like EC2/EBS and (to a lesser extent) S3 are really fungible. It's comparatively easy to move between providers, or even to your own hardware if you want. If someone were to come along and offer a comparably performant and reliable service to AWS at half the price, Amazon's customers would flee like rats. Obviously the devil is in the details, but it seems to me like Google is better positioned to offer that kind of value proposition (c.f. Google Drive, whose retail price is already cheaper than S3) than Microsoft or Rackspace.
Basically: linux boxes are a commodity. You can't compete in this market on features. That makes Amazon's (admittedly) dominant position more precarious than it looks.
For example, press a button and get dedicated vps hosting for your cloud images, press another button and get dedicated physical hosting, press another button and you buy the hardware and switch to a colo relationship, press another button and you get your physical hardware overnighted to anywhere.
If the big players (hi, Amazon) don't do it, then set up IaaS as a Service:
• Push a button and my cloud images move from Amazon to Microsoft Azure to whatever Google's thing is (since that's ostensibly the discussion today). Include RackSpace, Linode, etc. as well for bonus points.
• Pay the bills for me. If Amazon won't handle migrating my images, I'll pay you 1% on top to take my money, pay the bills, and manage the change in billing when I switch providers. Here's your chance to advertise when you negotiate better deals with a competitor: show me how much money I could be saving.
• If I push the button, and there are really obvious things about my cloud images that won't work where I'm going - i.e. things you've tried to move and it didn't work for somebody else - detect that and say "nope, here's what you need to fix." It's not going to catch everything, but kind of like a virus database it should be constantly updated as you hit problems.
• I'm not asking you to do the migration for free. Well, if I want a free migration, I have to accept that it won't transfer perfectly and I'll have to debug it. Or, I can pay you an hourly rate to do the migration and set up a test environment on the new platform, and identify any problems.
I wish somebody would do that.
AWS also includes SQS, IAM, SWF, SimpleDB, DynamoDB etc all of which are proprietary with very Amazon specific APIs. As each new developer starts to use these it "locks" them into the platform as a whole. And since many of these are core services I just don't see customers moving to a competitor unless there is a massive difference in price/features.
Also don't forget: NOBODY offers the complete range of unified services that AWS does right now AFAIK.
That's where the money is. Yes, Amazon offers that other stuff. I'm sure someone buys it. I refuse to believe it's a significant fraction of AWS revenue without evidence. Huge numbers of successful sites are built on the core stuff. Are any large sites using the Amazon lock-in features? I'm certainly not aware of any.
But people ARE starting to look at them and it is an area (PaaS) that is going to become more and more compelling for businesses in the future. And Amazon is right now is the only player I know of in that space. And every new user they attract could well be locked in for life.
IaaS is immediately useful to anyone who needs a Linux box. PaaS needs longer lead times for people to adapt to a new platform.
Amazon's approach to the PaaS market is probably a lot better than Google's.
Google went: here's a new set of APIs, write custom apps to use them.
Amazon let you host standard LAMP apps, and then slowly started offering parts of the stack as a service (oh, you need a database? Here, use our managed one. You need search? We have that. Load balancing? Just use ours, it's easier than doing it yourself.)
Same with DynamoDB: the only reason I'd use it is because EC2 instances don't come with SSDs. Otherwise, meh.
Amazon has a unique advantage here because the systems and technologies needed to run the retail website are very much identical to what's needed to serve up a commercially viable PaaS offering to the public. So much so that amazon is moving rapidly toward self-hosting the web store on aws (a lot of it is already on aws today).
In contrast the way google runs their own services is very different (though in some ways more advanced) and not generally suitable to morphing into commercial cloud services, so they don't have that self-hosting advantage. They certainly have the know how to put out a decent offering though, especially now that the market has spoken so clearly on exactly what it wants.
Monkeybagel was great. I laughed pretty hard at it when it came out.
You can have all the money in the world and all the world class runners you want, but your team will still lose if you run even just on a slightly wrong track.