At the peak of the hype curve, the statements were;
- Don’t have to worry about (monitoring, operations, power, cooling, servers, infrastructure etc.. etc..)
- Infinite scalability and high availability
- Infrastructure is a commodity
Looking forward to the Redhat Summit next week in Boston with a theme of “Platform, Middleware, Virtualization, Cloud”. The cloud market is dominated by a lot of startups, with some goliath size companies still waiting in the wings. Depending your point of view, they are either lumbering dinosaurs unaware of the next evolutionary shift, or if you are like me, I think they are poised to strike.
- improved utilization (10% to 90%) enabled by virtualization/consolidation & elasticity
- the economies (power, operations, HW purchase etc..) of scale of multi-tenant cloud scale hosting
I have been asked this question a couple of times in a couple of days, so that always warrants a blog post.
The question first came up in a webinar I did with rackspace last week, it featured in regular conversation at Cloud Connect and then again on twitter from Adrian Cockcroft. The questions is framed like;
The Armada Group, Cloud Evaluation Framework (CEF) [left] is a tool to understand the value of deploying an application onto a cloud architecture. It includes six categories, one of which is Workload.
How do you get started?
At least some of the common attributes of cloud architectures (NIST Defn V15) are attractive to all IT Service Providers. How do you know what parts of your IT infrastructure should be considered for redeployment on a new architecture.