service oriented architecture:

Download Service Oriented Architecture:

Post on 20-May-2015

243 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

  • 1. Service Oriented Architecture: UWs Migration Strategya.k.a. What is it and how do we get one?
    • Jim Phelps
  • Sr. I.T. Architect,DoIT,UW-Madison
  • [email_address] http://arch.doit.wisc.edu/jim

2. What Ill Cover

  • Data vs. Service
  • Three Tiers (slides included FREE!)
  • Migration Strategy
  • Sticky Bits
  • Roadmap
  • Next Steps (2 years)
  • Summary

3. Integration is..

  • Complex: When systems change, interfaces need to be rebuilt
  • Brittle: When interfaces fail, people are unhappy (and often blame the wrong people)
  • Expensive:Garther - up to 50% of large enterprises IT budget is spent on interfaces and integration (1)

4. A Simple Use Case

  • eReserves:
  • Library has books on reserve for a course.
  • The Library checks those books out only to students in the course.

5. Data vs. Service SIS Course Roster Library CourseRoster Data 6. Data vs. Service Service SIS IsEnrolled Service Library Yes/No StudentID, CourseID SIS Course Roster Library CourseRoster Data 7. Reusability Service SIS IsEnrolled Service Library Yes/No StudentID, CourseID 8. Reusability Pointof Sales System Service SIS IsEnrolled Service Library Yes/No StudentID, CourseID 9. Reusability Pointof Sales System Portal StudentID CourseID Service SIS IsEnrolled Service Library Yes/No StudentID, CourseID 10. Service Data Replication of all data Pull as needed Opaque Transparent Disconnected Connected Point-to-Point One-to-ManyReusable Brittle Robust Composite Apps 11. Data vs. Service

  • Fundamental shift away from shipping data to providing services

12. Data vs. Service

  • Move to SOA to:
    • Reduce cost
    • Increase security
    • Reduce data duplication
    • Gain transparency
    • Reusability

13. Three Tiers

  • Lower Tier: Operations
    • No longer based on here is an app that runs on this server on this hard-drive

14. Three Tiers

  • Lower Tier: Operations
    • No longer based on here is an app that runs on this server on this hard-drive

SAN SAN Network Network App Server App Server App Server 15. Three Tiers

  • Lower Tier: Operations
    • No longer based on here is an app that runs on this server on this hard-drive

Network Service Compute Service Storage Service SAN SAN Network Network App Server App Server App Server 16.

  • Middle Tier: Application Architecture
    • Build Applications as a suite of reusable business objects
    • Architecture behind Fusion

Three Tiers Fusion IdM Edit Person CampusID create: first, last, middle Register 17.

  • Middle Tier: Application Architecture
    • Build Applications as a suite of reusable business objects
    • Architecture behind Fusion

Three Tiers Fusion IdM Edit Person CampusID create: first, last, middle New Hire 18. Three Tiers

  • Top Tier: System to System Integration
    • Based on Web Services
    • Basis of interoperability between systems

Service SIS IsEnrolled Service Library Yes/No StudentID, CourseID 19. Three Tiers

  • Top Tier: System to System Integration
    • Based on Web Services
    • Basis of interoperability between systems

Pointof Sales System Service SIS IsEnrolled Service Library Yes/No StudentID, CourseID 20. Three Tiers

  • Top Tier: System to System Integration
    • Based on Web Services
    • Basis of interoperability between systems

Pointof Sales System Portal StudentID CourseID Service SIS IsEnrolled Service Library Yes/No StudentID, CourseID 21. Migration Strategy - SOA

  • Process- business process analysis
  • Information- data definitions and standard schemas
  • Infrastructure- architecture and technical gaps
  • Vendors- helping hands
  • Organization - Change Management

22. Migration Strategy - SOA

  • Process - Business Process Analysis
    • Prioritization - Most Pain, Most Gain
    • Define/Document Business Process
    • Look for optimization opportunities
    • Use disruption to your advantage
    • Data needs (timeliness, availability, etc)

23. Migration Strategy - SOA

  • Information - Enterprise Data Definitions
    • Let the Business Process Analysis drive the data definition process
    • Dont build a complete dictionary
    • Start with the most needed definitions
    • Build on existing standards

24. Migration Strategy - SOA

  • Infrastructure - Architecture and Technology
    • Gap analysis - what pieces are missing
    • Do we have the right architecture in place?
    • Business Process Analysis and Data needs drive the effort.

25. Migration Strategy - SOA

  • Vendor - Evaluation to fill the gaps
    • Business Process Analysis
    • Enterprise Data Identification
    • Data Definitions / Standards Development
    • Service Design
    • Technology Gaps

26. Migration Strategy - SOA

  • Organization - Change Management
    • Culture shift from data to services
    • Staff training and support
    • New Expertise
      • Service Interface Designer(2)
      • Service Library Manager(2)
    • Integration Competency Centers (3)

27. People of the ICC

  • Project Manager
  • Services Architect
  • Interface Designers
  • Registry / Library manager
  • Schema experts

28. Migration Strategy - SOA 29. Building the ICC

  • Critical Success Factor
  • Centrally funded not a charge-back center
  • Unifying practices
  • Easier to enact and deploy standards
  • Manage the interface library (WS Registry a.k.a. UDDI Registry)

30. Organizational Change

  • New Skills and the ICC
  • Forces for Change
  • Misalignments
    • Funding models
    • Employee Evaluation

31. Who is the force for change? Pointof Sales System Portal StudentID CourseID1 ? ? ? ? Service SIS IsEnrolled Service Library Yes/NoStudentID,CourseID 32. Force 1: Architectural Purity Statement: It is good for the Enterprise.Model:We will all cooperate for the good of the whole. Never works. People dont act for the good of all when their project / budget / timeline / comfort is at risk. Service SIS IsEnrolled Service Library Yes/NoStudentID,CourseID Pointof Sales System Portal StudentID CourseID1 33. Force 2: Consumer Statement: We want a Web service for .. Model:The first Consumer will drive the change. Rarely works. Need an alignment of good will between the Consumer(s) and Service Provider. Service SIS IsEnrolled Service Library Yes/NoStudentID,CourseID Pointof Sales System Portal StudentID CourseID1 34. Force 3: Service Provider Statement: It is the new supported way Model:The Service Provider will set the standard Should work. Especially if the Service Provider can eliminate other feeds and if they impose costs on new feeds. Service SIS IsEnrolled Service Library Yes/NoStudentID,CourseID Pointof Sales System Portal StudentID CourseID1 35. How would this work Service Provider eliminates multiple flat-file feeds - replaces with single Web Service. 36. How would this work

  • Use Web Service
    • Agree to SLA
    • ICC establish Security and Policy
    • Register use in the WS Registry

Service Provider eliminates multiple flat-file feeds - replaces with single Web Service. Consumer can: 37. How would this work

  • Use Web Service
    • Agree to SLA
    • ICC would establish Security and Policy
    • Register use in the WS Registry
  • Request a Flat File
    • Go through review
    • Pay to build & maintain