Useful Cloud Advice, Part Two. Applications
This is the second part of this series talking about things you need to consider, and where cloud usage makes sense given the current state of cloud evolution. The first one, Cloud Storage, can be found here. The point of the series is to help you figure out what you can do now, and what you have to consider when moving to the cloud. This will hopefully help you to consider your options when pressure from the business or management to “do something” mounts. Once again, our definition of cloud is Infrastructure as a Service (IaaS) - “VM containers”, not SOA or other variants of Cloud. For our purposes, we’ll also assume “public cloud”. The reasoning here is simple, if you’re implementing internal cloud, you’re likely already very virtualized, and you don’t have the external vendor issues, so you don’t terribly need this advice – though some of it will still apply to you, so read on anyway.
Related Articles and Blogs
- Maybe Ubuntu Enterprise Cloud Makes Cloud Computing Too Easy
- Cloud Balancing, Cloud Bursting, and Intercloud
- Bursting the Cloud
- The Impossibility of CAP and Cloud
- Amazon Makes the Cloud Sticky
- Cloud, Standards, and Pants
- The Inevitable Eventual Consistency of Cloud Computing
- Infrastructure 2.0 + Cloud + IT as a Service = An Architectural ...
- Cloud Computing Makes Servers Obsolete
- Cloud Computing's Other Achilles' Heel: Software Licensing