Executive Summary
A regional insurance provider needed to tell their board, their regulators, and their new Chief Digital Officer that they had "modernised." They had a 1987 mainframe running COBOL that processed every claim the company had issued since the Lange government. They had four months and a marketing budget considerably larger than their engineering budget. We delivered full cloud-native status in six weeks. The mainframe is still in the same room. It has not been touched. This is the story of how that happened, and why nobody has asked any follow-up questions.
The Challenge
True modernisation — containerising the claims engine, extracting it from 340,000 lines of COBOL, rebuilding it as microservices — was quoted by three other vendors at 18 to 30 months and a number the CFO described as "not happening." The client's actual, underlying need was narrower than "modernise the system." It was "be able to say the word cloud-native in the annual report without lying in a way that could be proven in court."
Our Approach: The Banana Ecosystem Reframe
We ran this engagement through our full DEVOOPS CYCLE, tracked on the same whiteboard diagram we use for every project — the one we call the Banana Ecosystem, with its arrows for exist, roll, trade, and gibberish.code{}, all orbiting a central box labeled SPRINT #94 regardless of which sprint we are actually on, because renumbering the whiteboard is out of scope for every engagement we have ever run.
The technical work was minimal. The narrative work was extensive. Over six weeks, we:
- Wrapped the existing COBOL claims engine in a thin API layer, so a modern-looking request could reach a computer built during the Cold War
- Moved the mainframe's physical hosting from an on-premises server room to a colocation facility with the word "Cloud" in its marketing materials (it is a building; it has walls; it is, definitionally, not a cloud)
- Renamed seventeen internal COBOL subroutines to use the word "Service" (CLAIMPROC-01 became "ClaimProcessingService," CLAIMPROC-02 became "ClaimProcessingService2")
- Produced a new architecture diagram for the board deck, in which the mainframe is drawn as a small grey box labeled "Legacy Core (Being Phased Out)," a phrase which is technically a plan and not a lie
The API wrapper
We are aware that a 40-minute response time is not, by any standard definition, cloud-native. We addressed this in the board deck by describing it as "eventually consistent," a phrase that is technically accurate and that nobody in the room chose to interrogate further.
Results
"Our regulator asked if we were cloud-native. We said yes. Nobody asked what that meant, and we have decided not to bring it up ourselves." — Chief Digital Officer, the client
Lessons Learned
The gap between "is cloud-native" and "can accurately use the phrase cloud-native in a board deck without immediate legal exposure" is larger than most vendors will admit, and considerably more profitable to operate in. We would caution any future client that this approach does not reduce technical debt; it relocates technical debt four kilometres and gives it a better vocabulary.
The mainframe, as of publication, is still running COBOL written before most of our troop was born (in monkey years, this is most of us). It will very likely outlive this website.
Director of Blameless Postmortems (Mostly Blame), Designed by Monkeys