Public 15 Years of Service Oriented Architecture at Credit Suisse Lessons Learned – Remaining Challenges Keynote SATURN 2013 – Minneapolis, USA Stephan Murer, Senior Advisor, KG 97 May 1, 2013
Information Technology at Credit Suisse What we do Information Technology is committed to fueling Credit Suisse’s growth. Our objective in IT is to partner closely with the business to deliver innovative and cost- efficient results. In today’s competitive environment, IT drives performance and revenue growth. By directly aligning our IT initiatives with the bank’s overall business objectives, Information Technology helps provide Credit Suisse with a distinct competitive advantage. Who we are Investment Banking and Client Channels Technology IT: Partners with the Investment Banking Division to deliver integrated and innovative technology solutions Private Banking & Wealth Management and Shared Services IT: Partners with Private Banking & Wealth Management and all Shared Services divisions to provide exceptional technology to our clients and employees Technology Infrastructure Services: Provides our business partners global, standardized information technology infrastructure and systems KG 97/13-002104 May 1, 2013 2
Information Technology Facts and Figures 1 66,400 supported users in 550 locations 4 main hub Production – Disaster Recovery pairs of data centers consuming 14.1 MW 2 of power Hardware – 85,500 workstations/laptops – 21,710 physical servers with more than 43 petabytes of storage – 4 host/mainframe CPUs with 83,200 MIPS 3 provided Software – ~6,021 applications Email – 67,541 email accounts – 5.5 m emails/day Helpdesk – 416,760 tickets (2012) Print Center – 198 million pages (2012) 1 As of March 2013 2 MW = Mega Watt 3 MIPS = Million Instructions per Second KG 97/13-002104 May 1, 2013 3
Convergence to More Agile and Standardized Operating Model to Improve Our Capabilities Shared components Consistent client Client Single sources of experience reference data Single sign-on Channel Common Service One portal, multiple Oriented Architecture solutions Common Services Securities (SOA) Banking Product processing Common domain OTC … Processing Shared, legal entity- and business services agnostic global model processing platforms Common infrastructure Common infrastructure Risk management Risk based on consistent and financial control architectural standards Unified risk and finance Finance that support our systems platforms, based on in a scalable, agile, agreed front-office data Infrastructure and cost-efficient manner KG 97/13-002104 May 1, 2013 4
Managed Evolution of Very Large Systems Requires Stable Interfaces Hard to replace a very large information system as a whole – High cost (> CHF 1 bn, estimate for Swiss platform) – Development time too high (> 5 years) – High risk, as both technical and business prerequisites shift over time Managed evolution is the only feasible approach – Stepwise transformation of landscape, renewing component after component – Multi-year effort which gradually implements the target architecture Well encapsulated components exposing managed interfaces are a prerequisite for managed evolution – Technically renew components, without affecting clients – Consolidate redundant data and functionality behind common interfaces and simplify – Seamlessly operate a technically heterogeneous system resulting from the evolutionary approach KG 97/13-002104 May 1, 2013 5
Service Oriented Architecture (SOA) Principles and Benefits Service interfaces and contracts Loose coupling Service abstraction Principles Principles Benefits Reusability Discoverability Interoperability Reduced integration expense Increased asset reuse Increased business agility Benefits Benefits Benefits Reduction of business risk KG 97/13-002104 May 1, 2013 6
Credit Suisse eXchange Bus (CSXB) User Group Specific Portals IFMS: Interface Management System CSXB Portal Integration OBPM: OneBank BPM Platform Interfaces Interfaces Application Application Application Interfaces Application Application Interfaces Interfaces Interfaces Application Domains, Domains, Divisions, Regions Divisions, Regions CSXB Service Integration Bulk Synchronous Asynchronous store-and-forward file transfer remote call (RPC) Design Runtime Repository Environment KG 97/13-002104 May 1, 2013 7
SOA Experience @ Credit Suisse Three Case Studies Credit Suisse Information Bus Opening the mainframe for modern front-ends Global PB SOA Wrap diverse international banking backends Workflow as shared service Flexible business processes 1998 2013 KG 97/13-002104 May 1, 2013 8
Case 1: Credit Suisse Information Bus (CSIB) Started in 1998. More than 1,200 services built up to now. All applications on the Swiss Platform offer and/or consume services today Principles Facts Enable Managed Evolution of Mainframe Platform Component architecture for the Swiss Platform Principles Objectives Reuse of core data&functionality (mainly) residing on the mainframe for modern front-ends Orbix – CORBA for synchronous services, migrating to WebServices WebSphere MessageBroker/MQ for messaging Principles Technology Ftps for files (“Bulk Services”), “File Broker” for flow control, transformation, etc. About 1,400 public services, 70 message publishers 400 mn CORBA calls and 120 mn messages delivered per month Principles Footprint KG 97/13-002104 May 1, 2013 9
Different Life Cycles in Different Application Layers Core system, GUI, presentation, Application logic, close to operational data, channel specific product specific generic for the bank 2+ years 10+ years 30+ years KG 97/13-002104 May 1, 2013 10
Measure Progress Build services as they are needed Gradually decouple domains Services Built as Needed Use existing functionalities KG 97/13-002104 May 1, 2013 11
Measure Progress Use of Services Follows Availability 200 600 800 900 1,100 Wide use of services follows Service services services services services services a critical mass of available Calls per available available available available available services Year * 10 9 Today ~5 billion service calls a year in Switzerland Fully decoupled platform some years ahead Core banking system on mainframe completely decoupled from remainder of platform KG 97/13-002104 May 1, 2013 12
Governance Bottom-up Requests, Top Down QA Project Initialization Design Implementation Service IDL/WSDL Development 2. Quality Check Specification Request Service Extended 3. Quality Check Change Design Request for reuse Complete Service Definition Generate Basic Service Private service Request Documentation/ 1. Quality Check Reuse existing service Code KG 97/13-002104 May 1, 2013 13
Re-use Is Very Uneven Measure Re-use 100 10 20 30 40 50 60 70 80 90 0 CIF Average re-use degree is 4 – 4 different client applications using a service About half of the services are reused Re-use of services varies based on type of service. Reference Data Services have the highest re-use. CIFRelations OE_Data DI_CurrencyRate OE_Search CRE_Documents KG 97/13-002104 AZ_Polist RiskClass CIFS_DepositsForCifs IVN_TisControl RTT_PMProfile_Update ADAC_ReportingChecks EBVV_Service_Update IPC_Cluster PI_GetData RTT_Manage_Changes ZV_ScanningMis AZ_OrderWithPayments CRE_Autolombard DBH_SafekeepingAccounts EBVV_Customer_Update IPC_Request KAUF_CreditPayments OE_FunctionHolder_Update PROK_ProductRelations RTT_Pool_Order_Update ACCT_Prompt ADAC_RepoItemStructure CAS_ATMBooking_Update CAS_CashService CRE_Balance DADMIN_Order EBVV_History_Update ED_Deal_OutputRepeat HYP_Balance HYP_KEHAccount KAUF_Collateral KOSA_OrderStatus_Update NZV_PayPathPendSegUpd PARS_Partner2 PROK_PriceCompRelations RRA_Account RRA_Request_Update TFR_TradeFinance May 1, 2013 14
Governance Interface Management System Searchable Service Catalog Data type repository with UM/ WSDL integration Governance workflows Lifecycle management Extensible code generator (MDA) Integration with other tools, like application repository or accounting KG 97/13-002104 May 1, 2013 15
Case 1: Credit Suisse Information Bus Experiences Well-accepted, high proliferation, good re-use of services Solid middleware foundation Principles Strengths Governance: Combination of bottom-up approach and top-down QA works Management becomes difficult because of size (> 1,000 services) Business object model (BOM) required as a framework in which to manage Principles Challenges the service landscape (currently in development) Long term migration towards Web Services, without compromising performance Strong governance is essential Organization needs time to learn (years for large organization) Bottom-up approach helped in gaining critical mass, but... ...supporting service design with common data model would greatly improve Lessons service quality and simplify QA Principles Learned Need improved interface management system (IFMS), market didn’t deliver Formal service descriptions could be the basis for code generation Business rationale necessary – Architectural beauty not good enough! KG 97/13-002104 May 1, 2013 16
Recommend
More recommend
