Wachovia mini reference at industry analyst SOA on z conference
Wachovia is going end to end mainframe SOA.
The presentation was interesting- basically Wachovia had an ageing proprietary middleware infrastructure it chose to overhaul and pretty much completely replace... with a mainframe-based system running WebSphere tools. Really this can be seen as a "new" mainframe customer, in that respect.
Keith Harris, VP of retail architecture and integration, Wachovia:
Wachovia is the
4th largest bank in the US
has 3,900 financial centers
and is the 3rd biggest brokerage in the US (another best kept secret?
Core SOA services, such as: Authentication, logging services etc.
Wachovia has some aggressive uptime requirements. the SLA is 99.9% uptime including scheduled outages.
Keith said: "basically, It can't be down."
Results- 7 months since install
Wachovia has exceeded SLAs, and now runs millions of transactions a day
zAAP will provide 92% offload.
WebSphere on z gives: Proximity to data, Achievable SLAs.
Thanks for the info Keith...
|by James Governor||May 4, 2006 in Application Development |
TrackBack URL for this entry:
Listed below are links to weblogs that reference Wachovia mini reference at industry analyst SOA on z conference:
A 92% offload number is higher than most customers see. Around 75% is typical for an "average" enterprise WebSphere application. However, my understanding is that XML-heavy processing (using Java libraries) offloads better than average, so Wachovia's experience makes sense in that context. That also probably means that SOA-related projects benefit exceptionally from zAAP.
What's also exciting about zAAP is the rate of uptake. For example, the first customer went into production *before* GA of the required z/OS release!
Posted by: Timothy Sipples | May 8, 2006 11:03:06 AM
I think this is all good news and I am really happy to hear they are going in this direction. One slightly catty observation however; 99.9% availability is not a particularly impressive number - that's almost 2 minutes of downtime per day.
A properly configured -basic- sysplex ought to get 4-nines (99.99%) which is about one hour of down-time per year and -parallel- sysplex with data sharing and elimination of single points of failure ought to get 5-nines (99.999%) which is about 5 minutes a year.
If they're doing mainframe SOA and they are exploiting the platform's native capabilities, they ought to be hitting that 99.9% number out of the park.
Posted by: Chris Craddock | May 8, 2006 5:47:26 PM
come on - he was including *scheduled* maintenance and so on in the figure. while i agree mainframes can offer far in excess of 99.9% - if they had some batch windows to include in the numbers, he was just being unambiguous.
Posted by: James Governor | May 9, 2006 12:26:37 PM
James I was not sure how to interpret your response, so if the following is something you know anyway, please excuse me.
Those sysplex availability numbers include time for planned downtime as well as unplanned - the latter of which should be zero. That is what "rolling IPL" is about.
To make a change that requires an IPL, you just partition that system out of the plex and all of the work is picked up seamlessly by the other members. Then you re-IPL the image you just pulled out and it rejoins the plex and work flows back to it in the normal course of operation.
The key observation is that you actually had a system down for some period of time, but the users did not perceive any service disruption at all.
Posted by: Chris Craddock | May 10, 2006 10:25:26 AM
I can't believe any system has a 99.9% uptime.
Posted by: financial spread betting | Jun 27, 2010 2:56:29 AM
The comments to this entry are closed.