MI703 Class 9 Agenda Service Oriented Architecture Service Oriented Architecture Zara Case Zara Case...

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

Transcript of MI703 Class 9 Agenda Service Oriented Architecture Service Oriented Architecture Zara Case Zara Case...

Page 1: MI703 Class 9 Agenda Service Oriented Architecture Service Oriented Architecture Zara Case Zara Case Project Time Project Time.

MI703 Class 9 AgendaMI703 Class 9 Agenda

Service Oriented ArchitectureService Oriented Architecture

Zara CaseZara Case

Project TimeProject Time

Page 2: MI703 Class 9 Agenda Service Oriented Architecture Service Oriented Architecture Zara Case Zara Case Project Time Project Time.

Application Integration Application Integration ReviewReview Tightly coupled integration within Tightly coupled integration within

applicationsapplications Loosely coupled integration between Loosely coupled integration between

applicationsapplications Sharing Sharing

– DataData– FunctionsFunctions

Page 3: MI703 Class 9 Agenda Service Oriented Architecture Service Oriented Architecture Zara Case Zara Case Project Time Project Time.

EAI IssuesEAI Issues

Tight coupling of data structures, Tight coupling of data structures, functionsfunctions

Location dependent linkages, static Location dependent linkages, static locationslocations

Focus on well-defined workflows Focus on well-defined workflows with high elasticitywith high elasticity

Flexibility limitations due to scope of Flexibility limitations due to scope of data, functions, couplingdata, functions, coupling

Page 4: MI703 Class 9 Agenda Service Oriented Architecture Service Oriented Architecture Zara Case Zara Case Project Time Project Time.

Service Oriented ArchitectureService Oriented Architecture

Purpose: To provide dynamic discovery and Purpose: To provide dynamic discovery and execution of the components of a workflow execution of the components of a workflow process w/o a formal hierarchyprocess w/o a formal hierarchy

Modular StructureModular Structure– Web services are the componentsWeb services are the components– No set access mechanism or protocolNo set access mechanism or protocol– Terms are “negotiated” at time of executionTerms are “negotiated” at time of execution

Compare to external marketplace versus Compare to external marketplace versus internal workflowinternal workflow

Page 5: MI703 Class 9 Agenda Service Oriented Architecture Service Oriented Architecture Zara Case Zara Case Project Time Project Time.

SOA Terms / AspectsSOA 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)

Page 6: MI703 Class 9 Agenda Service Oriented Architecture Service Oriented Architecture Zara Case Zara Case Project Time Project Time.

SOA: Problems SolvedSOA: Problems Solved

JAVA issuesJAVA issues– ““Write once, use often”Write once, use often”– ““Context” – all functions must be presentContext” – all functions must be present– Location of service fixedLocation of service fixed

Strategic DevelopmentStrategic Development– Components can be built w/o fixed hierarchyComponents can be built w/o fixed hierarchy– Possible multiple service providersPossible multiple service providers– Applications are built by dynamic linking of the Applications are built by dynamic linking of the

servicesservices– Linking to external services no harder, just a Linking to external services no harder, just a

different URL and XML formatdifferent URL and XML format

Page 7: MI703 Class 9 Agenda Service Oriented Architecture Service Oriented Architecture Zara Case Zara Case Project Time Project Time.

SOA: “Lines and Circles”SOA: “Lines and Circles”

Typical development modelTypical development model– Hierarchy of functionsHierarchy of functions– Context of processesContext of processes– ““Many servers” issueMany servers” issue

SOA makes linkage very SOA makes linkage very inexpensiveinexpensive– ““Liquid Computing”Liquid Computing”– ““Write once, deploy once”Write once, deploy once”

Page 8: MI703 Class 9 Agenda Service Oriented Architecture Service Oriented Architecture Zara Case Zara Case Project Time Project Time.

SOA: OpportunitiesSOA: Opportunities

SCM or “Channel” applicationsSCM or “Channel” applications– Service may be “bid” dynamicallyService may be “bid” dynamically– Switching costs minimalSwitching costs minimal– Invocation is programmed in, not dynamicInvocation is programmed in, not dynamic

Rapid Application DevelopmentRapid Application Development– Bottom-up developmentBottom-up development– Focus on presentation, integration of servicesFocus on presentation, integration of services– Infrastructure changes do not require application Infrastructure changes do not require application

changeschanges Applications can move and be “discovered”Applications can move and be “discovered”

Page 9: MI703 Class 9 Agenda Service Oriented Architecture Service Oriented Architecture Zara Case Zara Case Project Time Project Time.

Case Study: Zara Case Study: Zara

What are Inditex / Zara’s sustainable What are Inditex / Zara’s sustainable advantages? What might be the next advantages? What might be the next barrier to attempt?barrier to attempt?

How important is in-house How important is in-house manufacturing to the advantage? Why? manufacturing to the advantage? Why? (cp outsourcing IT?)(cp outsourcing IT?)

What is killing classic advertising as an What is killing classic advertising as an asset? (think peer production)asset? (think peer production)