You can't migrate that way. An Insurance company can do that (contracts usually last 1 year) but Banks can't.
It was more a suggestion of how to move to a new system at all.
What happens if the bank closes before those 50 years?
Also, you'll still have to write wrappers for the old tech (iPhone apps which access the COBOL core) in order to maintain feature parity with the other banks.
You mean "battle tested for 40+ years, totally solid 1970s tech"?
If anything, it's any crap they'd write now that would be MORE fragile.
You're right, of course, but the public is trained to trust the latest and greatest.
If 'battle tested' was the most salient selling point we'd be on Series 60 or QNX phones.
'We're putting new customers on the latest technology and keeping existing ones on our old systems' is not going to be an easy thing to message to the general public.
Actually, there are more Series 40 and Symbian phones sold today than iPhones - 350 million to 200 million (India / rest of Asia, Africa and Latin America are the main buyers). Many people here still miss the old Nokias. Of course, Android is the new Series 60.
http://gadgets.ndtv.com/mobiles/news/nokia-sold-35-million-f...
http://tech.firstpost.com/news-analysis/india-smartphone-shi...
But I don't see this ever really coming to consumer attention. They're never directly--or visibly--interacting with old mainframes. From their perspective, they're using the newest tech. The mainframe in the background doesn't exist to them. If they even think about it, it's just magic. The closest you might have gotten to the public talking about legacy systems was probably the healthcare.gov debacle, when a number of news articles mentioned integration issues as being an problem. Those were big issues in themselves, but they weren't the main problem behind the site's development nor were they ever a major discussion point.
0. http://www.pcworld.com/article/249951/computers/if-it-aint-b...
The canonical example when it comes to UK banking is the RBS outage, which meant that customers could not make payments for three weeks. RBS was hit with a £56m fine for that.
http://www.telegraph.co.uk/finance/newsbysector/epic/rbs/112...
Another commenter says there's no incentive for managers or execs to stick their necks out, but £56m is quite an incentive.
One could argue that legacy code makes that more likely because of unseen factors that predate the people actively working on it. It's hard to miss a landmine, after all, if you don't have any clue that it's there. But while a rewrite might eliminate that specific risk, it does so by inviting a lot of new ones to replace it. In some ways, the risks are probably greater as you need to figure out possibly decades of business logic and then re-implement everything. From a business decision perspective, the existence of legacy code on its own is an insufficient argument on its own. After all, the problems inherent in legacy code will eventually surface yet again in another 10-15 years anyhow. The better solution in most cases would be to identify specific problems and determine what can be done to hedge against them.
0. https://www.theguardian.com/business/2014/nov/20/royal-bank-...