First, let’s define what a win is. A win is a very relative term. Everyone’s definition of win is different. For some people, a win might be initializing a blog in AWS EC2 instance however, for others, it might be maintaining high availability to serve traffic to their site for millions of users. There might even be others who are running simulations and advanced analytics that requires a lot of effort in managing infrastructures on demand and at scale.
The implementation curve between those wins is drastic. While creating an EC2 instance might be simple, it takes a lot to get to a point where you are creating an application and a supporting infrastructure that can scale to millions of people and run advanced analytics and simulations on them.
The question here is, how can you make it happen and are you prepared to go through the challenging aspect of implementing it?
With the cloud adoption moving at an accelerating pace, everyone can easily talk cloud because of FOMO. But, is your organization strategically making the decision to move to the cloud? Are you prepared and capable to support the applications while the transition is happening? Have you considered the budget for maintaining two infrastructures in parallel when the initial proof-of-concept is being developed? Do you have the right talent? These are some of the very hard questions you have to ask yourself to even start a conversation around migrating to the cloud. And migrating towards cloud isn’t simply picking AWS or Azure or Google Cloud. It’s about identifying the benefits cloud brings to your organization in the long run and carving a path forward towards its adoption by putting an amalgam of processes around its success.
For a startup with fresh ideas and evolving technologies, it’s probably a lot easier to just start with cloud. However, for an established business who has a monolithic application that’s running in bare metal servers for years, it’s going to be a gruesome task. But not impossible with careful tactics.
With proper planning, talent and the right execution, you will be able to make it and win. But, how to create that plan to migrate to the cloud? This comes down to the kind of tech-shop you are operating under and the application itself. It’s infrastructure requirements, the data, persistence, retention, and SLAs. So, now that you have all that information in hand and your Enterprise Architect has no idea how to proceed. That’s when you start formalizing the process and do your cost and risk analysis. Everything is a risk. To be able to make a calculated risk is what’s important. With due-diligence and identifying if the cloud and it’s flexibility to spin up instances is going to help you cut down costs on bare-metal servers, it carves the path forward for cloud-adoption. Identify your applications and break it down to smaller components so that, you can leverage the flexibility and ease a cloud gives you. Start small and create proofs of concepts with your microservices and slowly migrate applications. This way, you won’t halt your business even if something goes wrong. That’s the agile way of doing things anyway. And that way, you can get a WIN.


Leave a Reply

Your email address will not be published. Required fields are marked *