Share this post:
As an IBM Cloud Adoption Leader, I spend a lot of time with clients who are implementing projects in the IBM Cloud.
Typically, but not always, I get involved when there’s something blocking the project or otherwise hindering progress. These tend to fall into a small number of common categories:
1. The tools are not right for the job
The IBM Cloud platform has a wide range of tools and services on offer. Selecting the right one, with the appropriate pricing plan, can be daunting, but is important.
To avoid mistakes, it’s important to first understand the functionality of the application being implemented and its required qualities and matching those to the right IBM Cloud platform service. For example, consider whether a bare metal server would make sense if the application needs raw horsepower. Might containers score over virtual machines for your application?
2. Public cloud may not be the right place
While many organizations have successfully migrated applications to the public cloud, not every system is a good fit, and a bad fit can lead to serious problems. Areas such as integration, performance requirements and even software licensing should be considered. Sometimes private cloud or transitioning to another application based on software as a service (SaaS) could be a more effective option.
Trying to move an application that has a low affinity to the cloud can be beset with problems. Sometimes, it may even be better to deconstruct an application and run parts of it in the cloud and other parts on premises, accessed through APIs.
3. Repeating what was done last time
A trap that many customers fall into when deploying solutions to the cloud is to take what they have previously done on premises and expect that to be successful in the cloud. What many quickly realize is that this approach doesn’t often work or can be expensive.
The cloud requires some different thinking. For example, application availability is architected in a different way in the cloud, where redundancy is built into many services or where services must be provisioned and deployed across different availability zones. It’s a case of knowing what to provision and where. This is compared to the more traditional approach, where entire redundant infrastructures are built at great expense. I have still seen this approach taken, without real need, in the cloud.
The key to any cloud adoption is to understand the application that is being delivered and to understand the cloud platform that is being used in the delivery. Like other IBM Adoption Leaders across the globe, I’m able to bring my depth of knowledge and experience of the IBM Cloud to customers’ projects. Once I have a good understanding of the project goals, I can advise and give pointers on the best approach towards success.
The causes of problems with cloud deployments often start out small. Don’t let these stop your cloud adoption.
Learn more about IBM Cloud Adoption Services.