How to Use "Minimum Viable Refactoring" to Achieve Post-Migration Operational Excellence

Level: 300

For enterprise customers with the goal of moving hundreds or thousands of applications to the cloud, a "lift and shift" migration strategy can sound beneficial. Move your apps to the cloud now, get the additional reliability and scalability, and use the cost savings to modernize over time. This strategy has paid off for many large organizations. But there is a caveat. Some enterprise workloads need a small amount of adjustment in order to meet governance, security and compliance requirements in the cloud. "Minimum viable refactoring", sometimes referred to as the "two week rule", is the process of doing the minimum amount of modernization possible to workloads prior to migration to ensure security and compliance without slowing down large-scale projects. So what is the minimum amount of refactoring possible to maintain operational excellence after migration? In this tech talk, our experts will share common customer issues and specific patterns for addressing them quickly and effectively.