Haha, you don't give up. How about this. HSBC has nearly $3T dollars in
assets. They have integrated their mainframe with Amazons AWS cloud.
You've been pwned man, take a breather.
"For large financial institutions, it can be extremely hard to predict
when your architecture may need to scale to process millions of
financial transactions per day. HSBC addressed this challenge by
integrating its on-premises mainframe with AWS services such as AWS
Lambda, Amazon Kinesis, and Amazon DynamoDB."
https://www.slideshare.net/AmazonWebServices/how-hsbc-uses-serverless-to-process-millions-of-transactions-in-real-time-fsv305-aws-reinvent-2018
On 22/10/2021 7:51 pm, Bill Johnson wrote:
Australia’s largest bank is Commonwealth Bank of Australia with a little over 1
trillion in assets in Aussie dollars. ANZ banking group #2 at slightly over a
trillion in assets. Wetpac banking 3rd at around 900 billion in assets. Which
doesn’t put any of them in the top 20. The 20th bank in the real top 20 is
Group BPCE of France at approx 1.5 trillion. These numbers are as of October
10th, 2021.
Millions of transactions a day is comical. Millions per hour is what many banks
process. 1 billion credit card transactions happen daily. Just credit cards.
I look forward to seeing your proof of an Aussie bank in the top 20.
The link I provided was Australia's largest (and a world top 20) bank
with millions of transactions a day. They're not stupid, production
technology choices are critical which is probably why IBM have spent $$
making sure Kafka runs ok on z/OS.
Caching isn't a new idea. It's a common CICS design pattern using TS so
you don't have to make an expensive call to DB2 or IMS. The customer
solution is not call the mainframe for read transactions. It's not
uncommon, it starting to become pervasive. Writes are a different matter.
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).
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
