Myth HassemPrag001 – Legacy systems cannot be refactored, rewired or ringfenced so they must be replaced
So we decided to play Mainframe Myth Busters. In this series we will begin to show you why we have “busted the myth or not”. As an organization you have invested millions if not billions on your mainframe, its people, systems and processes. So where does the legacy come from.
Many systems were written in COBOL to deliver business functionality over a period of time. Important that we understand that time is irrelevant as to when the system was written. What is important is that these systems were designed to manage scale and large volumes. Their underlying use of database technology made them horizontally scalable on the same mainframe or expand onto multiple mainframes if needed. So the real question is – can a system written in COBOL be refactored, reimagined, and reinvigorated using modern design practices? In our experiences, we have found that the investment needed to refactor, reimagine or reinvigorate is far cheaper than trying to replace the system fully. As an example, a core banking system replacement will cost north of R2Billion, whereas only around R200Million is required to modernize legacy systems.
The trick here is to spend the time to employ modern design practices featuring:
So chat to us on our unique CUBE lenses on experiences we have mastered.
Result – Myth Busted