71 VIEWPOINT How to transition workloads to the cloud Cloud transformations can be a complicated process, but prioritising data is the key to success One of the most challenging efforts an IT organisation can undertake is transitioning workloads from the mainframe to the cloud. The traditional approach has centred around a small group of specific toolsets focused on translating common business-oriented language (COBOL) to a proprietary Java code base. While this approach is appropriate for shutting down a small existing footprint, it postpones the inevitable rewrite of core applications and, in some cases, can make the transition more difficult as the code has been converted into a proprietary form of Java. As a result, this methodology is ill-suited for largescale mainframe integration or migration to the cloud. Instead of concentrating solely on the existing apps, an organisation must focus on the entire ecosystem, including security, governance, performance, storage and resiliency. In fact, migrating from a mainframe should be considered as no less significant than moving from one cloud to another. With this approach in mind, taking a transitional journey is more appropriate than using the proven lift-and-shift method. Whilst there are different approaches to both mainframe and cloud technology, they share one core principle: it’s all about the data. Taking a data-centric migration approach allows a business to immediately expand access to information that may have traditionally been difficult to reach. Furthermore, focusing first on data means an organisation can immediately contextualise data and enable artificial intelligence apps without further complicating information sources. Following a mature agile development process and incorporating a strong systems integration methodology that includes data governance and security standards throughout the extended environment offers greater flexibility and faster time-to-market cycles. For example, some applications which may be slated for retirement and best suited for an actual lift-and-shift can be moved, while other applications can be completely rewritten, taking advantage of modern code bases. While moving workloads from a mainframe will always be challenging, using an expansive approach will allow for a more independent and diverse migration. This will unlock additional value more quickly while minimising risk. Marc Reed is an enterprise architect at Kyndryl MARC REED: KYNDRYL Photo: Unsplash/Windows
RkJQdWJsaXNoZXIy NzQ1NTk=