Credit Suisse Case Study

1
Credit Suisse Case Study

• Jesse Jackson
• Chapter 16

2
Project Scope

• Credit Suisse IT infrastructure is around 600
  applications
• 12 million lines of code
• IBM, UNIX, and Windows platforms
• Currently todays applications are built with Java

3
SOA infrastructure

• Multi-channel banking
• Online trading
• Consolidation of the core-business
• Centralized administration and management
• 24-7 operations
• Support for thousands of concurrent users
• High throughput
• Sub-second response time

4
5 Major Goals

• Technical integration
• Logical integration
• Process and desktop integration
• Integration of purchased software
• B2B integration

5
Foundation for Landscape

• 3 different types of complementary integration
  infrastructures
• Credit Suisse Information Bus
• Event Bus Infrastructure
• Bulk Integration Infrastructure

6
Implementation

• A few main problems
• Complexity
• Too much overhead
• Too resource-intensive

7
Development

• Engineering the require middleware
• Supporting developers using the technology
• Both supported by integration architects

8
Key Steps

• Set up processes and structures accompanying the
  SOA introduction
• Educate and support developers from the different
  business units
• Quality Assurance
• A lot of the relevant info was stored in a
  repository

9
Credit Suisse Information Bus

• Synchronous Integration
• CSG started with an initial structuring for the
  application
• Partitioned into 20 domains
• First used with the COBRA technology

10
Event Bus Integration

• Asynchronous Integration
• Addressed backend-to-backend application
  integration
• CSIB and EBI share the same service
  implementations
• Message based integration solution

11
Bulk Integration

• Reuses the same methodology as both the
  information and event buses
• Currently under development
• Uses point-to-point file transfer
• The goal is to establish a file broker to support
  a centralized control of the various transfers.

12
Repository

• Service Interface
• Properties
• Planning
• Contact Info
• Implementation details
• Service conditions
• Exceptions
• Service level
• Parameter descriptions

13
Keys to Success

• Lessons learned
• Reuse of services
• More efficient application development
• Increase of collaboration

14
Main SOA aspects for success

• Interfaces
• Processes
• Management commitment
• Solid technology