If your company is doing a partial or complete cloud migration, you’ve probably reached that point when there’s something in your current infrastructure that you’re not satisfied with. There are many challenges present in environments that have mixed legacy and cloud applications, even if that state is just temporary. There are many challenges in these hybrid, mixed environments, including rationalizing the different languages, tools, schemas and formats, and databases, and the parts of the infrastructure that use these mixed pools of data and infrastructure.
Cloud migrations provide a great opportunity to do a culture shift. Devops and automation are compelling goals that become suddenly viable. You can’t just expect your devops engineers to do the whole lift, but you certainly can drive improvement by having devops involved in the process and having devops learn the requirements of the applications that are migrating from one form to the other. Even if you don’t manage to acquire devops nirvana on the way up, you possibly can acquire a lot of value out of this opportunity, especially if you’re coming from an old-fashioned enterprise environment.
A cloud migration gives an enterprise the opportunity to make the cultural shift because operations will need to interface more with developers, and they will be working intimately with them to move applications that are highly customized. In fact, they are probably a big part of the company’s intellectual property.
Tool chain changes
You need to understand what you’re moving and how you’re going to do it, and it gets tricky because you are likely moving something that previously wasn’t in a container into a container. For example, you may be moving something that previously wasn’t in Kubernetes into Kubernetes. You may also be trying to create a hybrid cloud environment with multiple public cloud providers and a private cloud. The devops tool chain plays a big role there.