Companies and individuals implementing cloud computing these days are doing some things correctly and many other things incorrectly. Here are the top three mistakes I'm seeing and how you can avoid them.
1. Not considering a public cloud
You love cloud computing and you love your server farm. Thus, you're moving directly to private clouds and not considering public clouds. While private clouds are great solutions in many instances, not considering public clouds as an architectural option could mean you're missing opportunities to leverage on-demand and inexpensive capacity.
[ Get the no-nonsense explanations and advice you need to take real advantage of cloud computing in the InfoWorld editors' 21-page Cloud Computing Deep Dive PDF special report, featuring an exclusive excerpt from David Linthicum's new book on cloud architecture. | Stay up on the cloud with InfoWorld's Cloud Computing Report newsletter. ]
The fact is public clouds provide elastic scaling -- and can do so on a pay-per-server-instances basis. Thus, if there is processing that occurs a few days a month or on a seasonal schedule (holiday shopping), the use of a public cloud, if only to provide additional capacity at certain times, can be a good fit.
2. Security and governance as afterthoughts
Although you should consider both security and governance to be systemic to the architecture, many organizations look at security and governance only after deploying their cloud computing solution, whether private, public, or hybrid. The problem is that you just can't layer security and governance on top of your clouds; they must be accounted for in the architecture and planning from Day 1.