JPM isn’t replacing their mainframe either. No banks that want security, uptime, and transaction processing AWS can’t match are. Wait til IBM’s 2nm chip becomes the norm.
Sent from Yahoo Mail for iPhone On Friday, October 22, 2021, 10:12 PM, David Crayford <[email protected]> wrote: How about JPMorgan Chase who also use AWS in their enterprise https://aws.amazon.com/solutions/case-studies/jpmorgan-chase/. It's the tip of the iceberg. You have obviously been out of the industry for a while. The typical enterprise IT system these days is heterogeneous. It's all about integration. CICS have recently added support for correlation tokens so a transaction can be tracked to the source of origin on distributed systems. On 23/10/2021 9:58 am, Bill Johnson wrote: > HSBC is one poorly run bank. Since 2000 to today the stock has been cut in > half. 60 to 30. So, I wouldn’t be touting their decision making. Also, the > AWS signing was so they could layoff thousands of employees. A move that > wreaks of desperation. > > > Sent from Yahoo Mail for iPhone > > > On Friday, October 22, 2021, 9:39 PM, David Crayford <[email protected]> > wrote: > > On 23/10/2021 9:04 am, Bill Johnson wrote: >> No bank needs AWS to process millions of transactions an hour. Every major >> bank does it on the mainframe without the outages AWS injects into the >> process. > Well, obviously HSBC do and they're the 6th biggest bank in the world. > AWS offers 99.999% uptime SLAs so if HSBC suffered an outage it's going > to be expensive for Amazon. > > Talking about outages a few years ago my bank suffered a catastrophic > outage when a batch job was incorrectly restarted from the wrong step. > Wages and pensions were not processed. RBS had a CA7 maintenance error > which caused weeks of chaos which was blamed on lack of skills after > outsourcing their operations to Hyberbad. They were find £57M by the UK > government. Air New Zealand suffered a catastrophic mainframe failure > caused by the incompetence of IBM global services carrying out a DR > test. Customers couldn't board their planes. It doesn't matter how solid > your IT platforms are when humans can make errors. > > >> >> Sent from Yahoo Mail for iPhone >> >> >> On Friday, October 22, 2021, 7:38 PM, David Crayford <[email protected]> >> wrote: >> >> 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 [email protected] with the message: INFO IBM-MAIN >>> >>> >>> >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO IBM-MAIN >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> >> >> >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
