Posts Tagged IaaS
A little furore erupted over Gartner’s famous and influential Magic Quadrant dissing the Amazon cloud in response to the report that Gartner published placing Amazon high on vision and low on execution. This was followed by the Gartner Analyst, Lydia Leong, trying to ‘splain herself.
The simple fact is that Gartner decided, when analysing the cloud industry, to lump Cloud IaaS AND Web Hosting (emphasis theirs) together. This is obscure and reflects quite badly on Gartner’s understanding about cloud computing. Very few cloud computing specialists will throw IaaS and web hosting together – in fact we spend most of our time trying to differentiate the two. It is shocking that Gartner has defined cloud computing so poorly and they definitely lose some credibility with that kind of definition.
Gartner’s target market does need to be considered when figuring out what this all means. Their market is enterprise CIO’s – you know the kind of people that have the money to spend on their misguided and overpriced opinion. This does not even include business owners in enterprises who are kept in the dark about Gartner reports, lest the CIO looses some power through sharing of said information. (Never mind the rest of us that have access to the Internet and blogs and tweets of well respected thinkers in order to come to our own opinion on the market leaders). Gartner is not for the rest of us and in the context of the Enterprise CIO, it makes perfect sense, after all, enterprise CIO’s are the ones confusing cloud computing and traditional web hosting.
Gartner magic quadrants are maybe useful for determining the market leaders of 90’s technology such as, say, whether SAP HR is better than Peoplesoft. Gartner has illustrated that their grasp of cloud computing is tenuous and irrelevant – it is just a shame that people pay attention to them.
Microsoft has quietly released the November 2010 SDK, without being accompanied the fanfare at it’s PDC launch. One of the big changes to Windows Azure is the VM Role which allows you to upload and run a Windows Server VHD. Although it smells like IaaS, it is not – as described by Microsoft’s Steve Plank,
The way to look at the VM Role is that the entire thing is a Windows Azure application. You don’t send a .cspkg file, but instead, the package is a .vhd file. Now, because these files are likely to be huge in comparison to a .cscfg, Windows Azure has created a method of updating with differencing disks, but that’s just an implementation detail. You can think of a VM Role application package as the .vhd file.
One of the best features about Windows Azure is (was?) that it implemented a PaaS model and forced you to build systems that were architected for the cloud from the ground up. Legacy doesn’t scale and Windows Azure made it difficult to lift and shift legacy apps, while at the same time allowing for a lot of re-use of existing code, skills and even, with SQL Azure, data access and storage.
The VM Role was probably quite easy to implement, after all, web and worker roles are VM’s anyway and was done, apparently, in response to demands from customers. I question whether or not those customers actually understood what they were asking for and now have the option, not just to lift and shift legacy applications, but to build legacy applications from scratch – and that is a problem for cloud computing.
AWS, on the other hand, is unashamedly IaaS and seems to have created an environment for cloud architectures to flourish with all the cloud frameworks that people are enthusiastically building on top of AWS. I don’t think Windows Azure will be able to pull the same stunt – after all you can’t run a Linux instance in the same datacentre as your Azure application.
With the VM role Windows Azure hasn’t built a good IaaS offering, they have taken a good PaaS offering and injected confusion, removed their product differentiation, encouraged bad architectures and corrupted the fundamental DNA of their PaaS offering. Microsoft is really battling to sell Windows Azure and convince people to use the platform – the VM role may seem to be good in the short term, but it does break the product.