Cloud Computing Has To Be About Openness And Ease; Not Locking Developers In
from the let's-see-something-real dept
There was a ton of press coverage today over Microsoft's not-particularly-surprising announcement of Microsoft Azure, its attempt to get into the cloud computing business, competing with the likes of Amazon, Google's AppEngine and (now) Rackspace, among others. Microsoft entering this space isn't a surprise at all, so it's a bit disappointing to see the sheer lack of details surrounding the announcement. Amazon has succeeded in the space because of two main things: incredibly cheap prices and ridiculous ease-of-use.Amazon recognized early on that its "cloud computing" efforts were a true utility offering. It needed to be pure plug and play with very low, easy to understand pricing, and absolutely no hassle to get started. It was so easy and such a good deal, many developers couldn't come up with any reason not to use Amazon's web services. While I initially thought Google's AppEngine might provide serious competition for Amazon, today I'm less sure. Google is using AppEngine more as a way to get startups to build their technology to work on Google's tech platform. That's the same thing that Microsoft will clearly be doing with Azure. Yet, for Amazon, it was never about locking developers in to Amazon's platform: it was just about making use of spare computing cycles. The fact that it wasn't so tied to Amazon's core business may actually be a benefit here, in that it lets Amazon be a lot more open and free about how people can use it, keeping it super cheap and easy. Google and Microsoft, on the other hand, get too focused on using their cloud offerings to tie developers to their own tech stack. I agree that someone else could come in and create a cloud computing solution that beats Amazon by being even more open and easier -- I just don't see either Google or Microsoft being that company.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: azure, cloud computing, ease of use, lock in, openness
Companies: amazon, google, microsoft
Reader Comments
Subscribe: RSS
View by: Time | Thread
Wait. What?
Microsoft has stated that there cloud will be open to run many different languages - including "non-Microsoft" languages and IDE's. That said, I do want to point out that you're putting the cart before the horse. The point of utility computing is that it is "utility" - you determine the partner that best fits your needs, not pick a partner then shoe-horn your development into it.
I like what Amazon is doing, but I will certainly take a look at what Microsoft is doing here.
[ link to this | view in chronology ]
Re: Wait. What?
Maybe they will offer a truly open service this time, but surely you can forgive the seasoned industry watcher for being a little sceptical? Especially since this is another Microsoft "innovation" where they're merely following others and using their marketing muscle to push their own platform rather than interoperating directly with other standards and platforms.
[ link to this | view in chronology ]
Is It Just Me...
[ link to this | view in chronology ]
Re: Is It Just Me...
there are two ways to run computers: completely centralized (dumb terminals) and completely decentralized (peer to peer). there are myriad advantages and disadvantages to both. neither is more advanced than the other.
all developments in computing are a swing of the pendulum in either the centralized or decentralized direction.
[ link to this | view in chronology ]
Re: Is It Just Me...
[ link to this | view in chronology ]
Re: Re: Is It Just Me...
if your business critical applications are delivered via the internet, then that internet connection is also business critical and should be treated as such. instead of redundant internal servers, your resources would be focused on redundant internet connections. cloud computing doesn't eliminate the need for infrastructure, it just changes the nature of that infrastructure.
the idea that a modern office worker can continue to work during a network outage is largely a myth. a groupware, file server or other server outage will put most corporate types out of commission anyway and will still cost time and money.
[ link to this | view in chronology ]
hardly any vendor lock-in with aws
Amazons services are quite trivial, replacing them by some other solution should be relatively easy. S3 storage is much like webdav which could replace it. EC2 is exactly running Xen images. In communications Amazon is a bit cloudy, by using jargon like virtual cores, availability zones etc. Amazon webservices is quite easy to replace by own hardware or by someone who'd like to compete with them.
See also the section about vendor lock-in this interview with werner vogels
[ link to this | view in chronology ]
Client Server Rides Again
I'm not surprised Microsoft has turned its attention to leveraging its applications from servers for Internet users - networks are fast and robust enough for this to work well and 2) most of their biggest corporate clients do this already across their corporate networks so why wouldn't Microsft try to commoditise this?
[ link to this | view in chronology ]
[ link to this | view in chronology ]