Guest contributor |
Kyndryl’s 2024 State of Mainframe Modernization Report found that 96 per cent of organisations are moving, on average, at least 36 per cent of their workloads to the cloud.
A hybrid approach allows organisations to take advantage of the performance and security of mainframes while enjoying the flexibility offered by the cloud. However, modernising or moving mission-critical workloads to a cloud platform can be challenging as these have strict performance and security requirements.
Even if you plan to move an entire mainframe to the cloud, the migration will likely be done in stages. Since workloads and data will be in a hybrid environment during this process, firms need to take extra steps to help ensure ongoing access to data, security and fast connectivity.
One of the key decisions developers will have to make when migrating is whether to refactor, replace or replatform applications.
Refactoring app code is like renovating a kitchen. However, instead of changing out obsolete fixtures, restructuring existing code optimises app performance.
This approach makes sense when an app’s original code is generally well written but needs to be updated to a newer programming language. For example, converting COBOL to .NET or Java. Although the refactored app functions much like the original, the updated code should improve overall efficiency, quality and maintenance.
Refactoring can take longer than other migration approaches because IT teams need to fully understand the original code and business logic before converting it. However, refactored apps are often easier to maintain because there are more developers available with skills in modern languages to update the software.
Our team is refining commercial processes to refactor apps at scale on Microsoft Azure. We use a portfolio analyser tool to identify data dependencies on the overall mainframe landscape before converting the original code. To help detect and reduce errors, we also run apps on both the mainframe and the cloud throughout the migration phase. Once converted to the new language, refactored apps function like .NET containers running on Azure. This approach enables software enhancements while keeping the existing business logic intact.
Out with the old and in with the new is the premise behind the replacement approach. It entails completely discarding old apps and starting from scratch with software-as-a-service or off-the-shelf products.
Replacing apps may be viable when older technology can no longer meet business needs or has become too complex to support. This method eliminates the need to rework existing software and maintain custom code, making it a popular choice when developers lack the time or expertise to refactor older software. But replacement can be expensive, and IT teams must embrace new ways of working when deploying and learning to use the technology.
In November 2021, Kyndryl’s chief information officer replaced existing systems with standardised apps and platforms whenever possible. The goal was to reduce IT complexity, technical debt and the total cost of ownership.
Over two years, we downsized our app portfolio from more than 1,800 business apps to fewer than 360. Ultimately, this technology transformation will play a significant role in lowering Kyndryl’s selling, general and administrative expenses by $200 million.
Often called ‘lift and shift’, replatforming involves modifying older software to work in the cloud without rewriting its core architecture or drastically altering its functionality.
Replatforming is often the easiest way to move apps because it requires minimal changes to the underlying architecture and data. Although this approach reduces overall risk, long-term maintenance costs may be higher than replacing or refactoring an app.
We’re currently helping a global communications provider control its infrastructure costs and derive richer insights from its data by moving critical mainframe apps and data to Azure. The cloud-based apps will connect to the customer’s service management platform and support its artificial intelligence for IT operations estate model. Software that remains on the mainframe will integrate with data from a more comprehensive set of systems for analytics.
By 2026, we project replatforming will reduce an organisation’s mainframe operating costs and energy consumption by 70 per cent, leading to savings worth more than $22 million annually.
Regardless of how a company approaches modernising mainframe apps, the overarching goal should be to put the right workload on the right platform. By aligning technology strategy and budget with long-term business objectives, organisations can choose a path that optimises performance and efficiency now and in the future.
Ken Gambon is director and principal of global engineering in Kyndryl’s applications, data and AI practice
Discover more insights like this in the Winter 2024 issue of Technology Record. Don’t miss out – subscribe for free today and get future issues delivered straight to your inbox.