From Legacy To Cloud

 
 

Would you like to infinitely scale operations depending on user load and have real-time analytics and reporting? You’re not alone…

thumbnail-elevator-to-the-cloud02.jpg

The software industry races to the cloud

Software companies are fighting each other on the stairs to the cloud while falling into common pitfalls. The fall is often rough, resulting in delayed projects, exceeded budgets and a lot of wasted time.

Cloud providers, such as Amazon Web Services, Microsoft Azure and Google Cloud Platform are fueling this race by decreasing the entry threshold. This may seem positive, but often ends is precipitate actions. I bet you don’t know the exact difference between these three cloud providers.

That’s why it’s important to prepare yourself thoroughly and to avoid common pitfalls. That way, you can skip the stairs and step straight in the elevator to the promised cloud.

In OUR experience…

We’ve noticed a common 4-step pattern in legacy to cloud migrations.

  1. Initially, software companies start by implementing Continuous Delivery. A software development strategy that strives to automatically build, test and deploy software. After a while, your organisation feels and realizes how much time you wasted in the past. This insight sparks an unstoppable movement that fuels the next innovations.

  2. While getting your hands dirty with Continuous Delivery pipelines you generate insight in cloud migrations. You’ll figure that the cloud is just better at infrastructure and that renewing server subscriptions is expensive and ineffective. Since you’ve already build a Continuous Delivery pipeline, the switch to the cloud is easily made.

  3. You’ll start with virtual-machines, as they don’t differ that much from your previous infrastructure setup. Yet over time, you generate interest for containerization with Docker. Creating small containers of your environment and being able to release them on any platform is just too useful to ignore.

  4. While playing with these containers, you’ll realize their potential and start to research microservices. Microservice architecture and orchestration with Kubernetes is tough. Therefore I suggest to tackle this phase in an agile manner, awarding value in every step. Start with the stand-alone services and work your way up from there.

Common pitfalls…

Moving to the cloud at the wrong pace accumulates technical debt. You should start today and build a proper foundation before moving to the next phase. It simply doesn’t make any sense to work with microservices without a proper Continuous Delivery pipeline.

Secondly, technical problems aren’t the only problems you’ll face. I’ve seen myself, how a handful of people migrated from legacy to cloud while leaving the majority behind. In such case, operations froze and chaos arose. Without the proper mindset you cannot evolve into a cloud-native operation.

Every cloud migration is unique…

That’s why you need the right people. You need cloud experts with the proper skill set to give you insight in your upcoming challenges.

A cloud solution tailored to your legacy application.

In case this sounds interesting to you, I suggest you take a look at our programs or take the direct approach and contact us through the form below.

 
CloudStijn Dautzenberg