ANZ cloud computing lead architect at IBM, Simon Kaye, on common ‘gotchas’ associated with cloud computing:
1 Don’t assume or have the illusion that infinite computing resources are available on demand. Capacity planning is still a key discipline.
2 If you chose to buy capacity and resources on a short-term basis as needed, make sure you have the processes within the enterprise to request and agree on the removal of these resources when they are no longer needed.
3 Be careful that your choice of cloud provider does not limit your options or ability to create on open and standard environment. Know where the software developers want to take your applications.
4 Be clear on the fundamental latency limits of getting into and out of the cloud and ensure that your outcomes are not impacted by this. Applications that require microsecond precision may not be the best suited to certain cloud solutions.
<5> In making the decision about whether to move an existing service to the cloud, additionally examine the expected average and peak resource utilisation, especially if the application may have highly variable spikes in resource demand; the practical limits on real-world utilisation of purchased equipment; and various operation-al costs that vary de-pending on the type of cloud environment being considered.
6 Know ahead of time how your software vendor will price a cloud solution. This is an area that could well erode some of the savings you might otherwise receive.