This document summarizes the evolution of SOA strategies and practices at IBT, an investment bank. It discusses how IBT initially took small steps with basic web services before embarking on a broader implementation of SOA across the organization. A key case study described how an early content management service provided centralized, standard access to document repositories while reducing costs.

1. Evolution of SOA Strategies & Practice at IBT Prashant Sarode Director SOA-Web Services Group Investors Bank & Trust Co. May 9, 2007

7. What’s a Service?: Evolution from Sub-Routine to Services Objects Piece of self-contained code with logic for a small part of the whole business area. Usually a module within a single language and single process space Example: A Pricing object knows about IBM price data. Components Code that gets re-used on application or system level. Usually modules that can be accessed in a distributed manner across languages but using proprietary protocols . Example: A logging library we use for all the Java applications. EJBs, CORBA objects, COM objects Services Active, running code that delivers business and system functions. Modules accessed in a distributed manner using standard protocols - SOAP, XML, HTTP Example: Content Management Service Sub-Routines Piece of self-contained code with logic for a small part of the whole business area. Usually a module within a single language and single process space. Typically free-form without object design patterns. 1958 – Invention of the subroutine for Fortran II 1960s on - Object Oriented Languages Smalltalk(1969)‏ 1970s – LANs 1980s – Network Objects 1998 – XML/ RPC submitted to W3C Key Driver of this evolution: How do we better encapsulate, share & maintain business logic?