W dniu 22.10.2021 o 03:12, David Crayford pisze:
On 21/10/2021 7:31 am, Bill Johnson wrote:
I do almost everything important via app with a mainframe on the back
end. Banking, health records, retail shopping, insurance claims,
investing. And with very high confidence the transactions are secure,
fast, & always available. Not sure how more modern the mainframe
could be actually.
Bill J
I would suggest that almost all of those companies (banks, retail,
insurance etc) that run mainframes run a significant portion of their
IT systems on distributed systems. I recently met a software architect
from a bank who told me that the explosion of internet banking app
usage has pushed up the TCO of their mainframe to unacceptable levels.
70% of those transactions were reads (folks checking their bank
balances on their phones). Their solution was use Apache Kafka to
replicate the data to Apache Cassandra and only hit the mainframe for
writes.
BTDT, but not on Kafka. Indeed, the "cache system" ran up to 40%
transaction.
Sounds good? Imagine: 40% less workload...
NO
There are light and heavy CICS transactions and cached ones were light.
Proof: some day the cache stopped working due to system failure. During
rush hours.
Observations from mainframe side: number of transactions per second blew
up. Average response time ...decreased a little bit.
I was really happy reporting it to management.
However the management was not happy because of that, just because they
want to switch the mainframe off. Nevermind, the new transaction system
has response times 35-140ms (compared to 4-5ms on mainframe).
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
