MI703 Class 9 Agenda Service Oriented Architecture Service Oriented Architecture Zara Case Zara Case Project Time Project Time

Application Integration Review Tightly coupled integration within applications Tightly coupled integration within applications Loosely coupled integration between applications Loosely coupled integration between applications Sharing Sharing –Data –Functions

EAI Issues Tight coupling of data structures, functions Tight coupling of data structures, functions Location dependent linkages, static locations Location dependent linkages, static locations Focus on well-defined workflows with high elasticity Focus on well-defined workflows with high elasticity Flexibility limitations due to scope of data, functions, coupling Flexibility limitations due to scope of data, functions, coupling

Service Oriented Architecture Purpose: To provide dynamic discovery and execution of the components of a workflow process w/o a formal hierarchy Purpose: To provide dynamic discovery and execution of the components of a workflow process w/o a formal hierarchy Modular Structure Modular Structure –Web services are the components –No set access mechanism or protocol –Terms are “negotiated” at time of execution Compare to external marketplace versus internal workflow Compare to external marketplace versus internal workflow

SOA Terms / Aspects Standard for defining the service (WSDL) Standard for defining the service (WSDL) Web Services Registry (UDDI) Web Services Registry (UDDI) Standard for invoking the service (SOAP) Standard for invoking the service (SOAP) Standard for presenting data (XML) Standard for presenting data (XML)

SOA: Problems Solved JAVA issues JAVA issues –“Write once, use often” –“Context” – all functions must be present –Location of service fixed Strategic Development Strategic Development –Components can be built w/o fixed hierarchy –Possible multiple service providers –Applications are built by dynamic linking of the services –Linking to external services no harder, just a different URL and XML format

SOA: “Lines and Circles” Typical development model Typical development model –Hierarchy of functions –Context of processes –“Many servers” issue SOA makes linkage very inexpensive SOA makes linkage very inexpensive –“Liquid Computing” –“Write once, deploy once”

SOA: Opportunities SCM or “Channel” applications SCM or “Channel” applications –Service may be “bid” dynamically –Switching costs minimal –Invocation is programmed in, not dynamic Rapid Application Development Rapid Application Development –Bottom-up development –Focus on presentation, integration of services –Infrastructure changes do not require application changes Applications can move and be “discovered” Applications can move and be “discovered”

Case Study: Zara What are Inditex / Zara’s sustainable advantages? What might be the next barrier to attempt? What are Inditex / Zara’s sustainable advantages? What might be the next barrier to attempt? How important is in-house manufacturing to the advantage? Why? (cp outsourcing IT?) How important is in-house manufacturing to the advantage? Why? (cp outsourcing IT?) What is killing classic advertising as an asset? (think peer production) What is killing classic advertising as an asset? (think peer production)