In our case, everything ‘core’: checking and savings accounts, loans and credits, credit and debit cards… anything requiring a sub-second response time while being bombarded with tens of thousands of transactions per second AND requiring strict ACID transactions end to end AND 24x7 availability with quick recovery in case of disaster.
Secondary stuff is being moved to other architectures. And new core stuff is being written in Java… and ran on the mainframe.
I can search it, but do you have a description of what type of finance transaction are being processed this way still?
Banking IT engineer here.
In our case, everything ‘core’: checking and savings accounts, loans and credits, credit and debit cards… anything requiring a sub-second response time while being bombarded with tens of thousands of transactions per second AND requiring strict ACID transactions end to end AND 24x7 availability with quick recovery in case of disaster.
Secondary stuff is being moved to other architectures. And new core stuff is being written in Java… and ran on the mainframe.
Credit card transactions and many banks too. Source: https://www.precisely.com/blog/mainframe/9-mainframe-statistics