Brian Roemmele on X: "What are the real costs and risks of replacing legacy COBOL systems with modern alternatives?

After spending a decade and $100 million to replace a legacy COBOL system, enterprises often find their modern cloud architecture slower than a 40-year-old mainframe.

COBOL systems on" / X<br>Post

Log inSign up

Post

Brian Roemmele on X: "What are the real costs and risks of replacing legacy COBOL systems with modern alternatives?

After spending a decade and $100 million to replace a legacy COBOL system, enterprises often find their modern cloud architecture slower than a 40-year-old mainframe.

COBOL systems on"

Brian Roemmele

@BrianRoemmele

What are the real costs and risks of replacing legacy COBOL systems with modern alternatives?

After spending a decade and $100 million to replace a legacy COBOL system, enterprises often find their modern cloud architecture slower than a 40-year-old mainframe.

COBOL systems on IBM mainframes process trillions of dollars in daily transactions for banks, insurers and governments extremely well. Over 40–60 years they have accumulated layers of patches, updates and custom logic.

The high financial and time costs of rip-and-replace migrations are a major barrier; enterprise overhauls often take 5–10 years, by which time the target architecture may already be obsolete.

The greatest risk is loss of undocumented business logic—the COBOL code is frequently the only documentation. Reverse-engineering decades of obscure patches can miss edge cases, such as a 1993 tax exemption, causing critical transaction failures.

Mainframe-to-cloud moves are rarely 1:1. Mainframes excel at high-volume batch processing and heavy I/O; distributed microservices introduce network latency that bottlenecks performance and raises costs.

There are AI approaches but none have been very successful thus far.

In fact I am working on a COBOL update for a client right now.

Consequently many enterprises abandon full replacement for in-place modernization—wrapping COBOL in APIs for modern apps or translating it to Java—while gradually updating the edges.

span:not(:empty)~span:not(:empty)]:before:content-['·'] [&>span:not(:empty)~span:not(:empty)]:before:px-1 [&>span:not(:empty)~span:not(:empty)]:before:shrink-0">2:59 AM · Jul 26, 202681.4KViews

215<br>181<br>1.3K<br>342

span:not(:empty)~span:not(:empty)]:before:content-['·'] [&>span:not(:empty)~span:not(:empty)]:before:px-1 [&>span:not(:empty)~span:not(:empty)]:before:shrink-0 min-w-0 overflow-hidden">Scott in AR

@barefooter64

Jul 26

Sometimes there's not even going to be source code that matches whats running for old systems that have been running for years.

We had an old CICS system that started crashing and we couldn't find the matching source. Ended up working with one of the well known experienced Show more

120<br>4.5K

span:not(:empty)~span:not(:empty)]:before:content-['·'] [&>span:not(:empty)~span:not(:empty)]:before:px-1 [&>span:not(:empty)~span:not(:empty)]:before:shrink-0 min-w-0 overflow-hidden">Paul Mangione

@paul__mangione

Jul 26

67<br>1.2K

span:not(:empty)~span:not(:empty)]:before:content-['·'] [&>span:not(:empty)~span:not(:empty)]:before:px-1 [&>span:not(:empty)~span:not(:empty)]:before:shrink-0 min-w-0 overflow-hidden">BowTiedVernacular

@BtVernacular

Jul 26

I know you know this, but COBOL itself isn't the problem, it's a good language. The 50 years of poorly documented spaghetti code spanning three generations of coding styles, mergers, policy changes, etc.. is the problem.

It's still considered the gold standard because every Show more

58<br>2.4K

Log in or sign up for X<br>See what’s happening and join the conversation<br>Continue with phoneContinue with AppleContinue with Google<br>or<br>Log in with username or email

Relevant people

Brian Roemmele@BrianRoemmeleFollow<br>we can only see what we think is possible...

Trending now