• Save
Services oriented architecture
Upcoming SlideShare
Loading in...5
×
 

Services oriented architecture

on

  • 2,092 views

 

Statistics

Views

Total Views
2,092
Views on SlideShare
2,084
Embed Views
8

Actions

Likes
2
Downloads
0
Comments
0

4 Embeds 8

http://www.slideshare.net 5
http://localhost 1
http://static.slidesharecdn.com 1
http://www.linkedin.com 1

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Services oriented architecture Services oriented architecture Presentation Transcript

    • SOA Presentatie Door : Richard Claassens IT Architect Regie SNS Bank Voor : Regie Datum : 6 oktober 2008 Services Oriented Architecture
    • Financiële bedrijven die SOA toepassen en daarover naar buiten treden ..realized $2M savings in the First year through company wide increase in productivity.. Peltz, Wells Fargo: “The SOA approach has been a big win for Wells Fargo.We can now break down traditional application silos and design the user experience around their workflows. We’re adding new capabilities and making modifications continually. We wouldn’t have that flexibility if we had to start from scratch with every project. We’ve become very agile.” Service-oriented architecture can provide a bank with the robust, resilient IT architecture it needs to grow, achieve speed-to-market and optimize customer service. It also provides a platform to help meet compliance requirements and assure security and integrity of information assets. Hinrich Voelcker, Global Head of Payments Processing IT, Deutsche Bank (New York) “ The primary benefit of SOA we realize is significant reuse of services across the integration solution space,” Petrey says. That’s resulting in a substantial reduction in service development time and the creation of higher-quality services that require less debugging and testing, he says. ING Drives Business Efficiencies With SOA Architecture, best practice,Ricardo Arruda, Forrester, 31 May 2006 How to Navigate a Sea of SOA Standards, Bob Violino, CIO, 13 April 2007 The business benefits began to reveal themselves quickly. By the end of 2005, Nationale-Nederlanden had achieved a 25% cost reduction and a 40% reduction in manual processing as a result of the new policy administration solution. BPM and SOA, Linda Grigs, ACS Service Oriented Computing, December 2007 The Benefits of a Service-Oriented Architecture, Peggy Bresnick Kendler, Bank Systems & Technology, 31 maart 2005 Customer Case Study: Wells Fargo Enhancing Service Delivery and Growing Revenue Through Shared Services. BEA Systems, January 2006 *) Participant SOA Consortium *) **) Member BIAN – Banking Industry Architecture Network **)
      • Results: Enterprise SOA Value Delivered
      • Improved customer management (e.g. cross selling, loyalty management through 360º view on customers)
      • Reduced processes complexity by referring only to one central source of customer data “one version of truth”
      • Increased stability, adaptiveness and control in changing banking processes
      SOA Consortium Promoting Business-Driven SOA “Executive Suite SOA” Case Study Summary, Amit Sinha – SAP, Fillmore Bowen - IBM, 28 Juni 2007 of South Africa **) *) ***) Winner of the The Gartner CRM Excellence Awards, at the CRM Summit 2008 in London ***)
    • SOA
      • Waar is het goed voor ?
      • Wat is het ?
      • Welke voordelen kunnen we er mee bereiken ?
      • Wat moet worden geregeld om de voordelen te kunnen behalen ?
    • Legacy Problem area 1: Business today is limited by software silos Root cause: Stand-alone stovepipe monolithic applications have redundant logic and data. HR Finance CRM ERP
    • Paralyses Ability to Deliver Agility Change Requests (Source: Enterprise SOA: Service Oriented Architecture Best Practices by Dirk Krafzig, Karl Banke, and Dirk Slama, Prentice Hall 2004) Problem area 2: change requests reduces the agility over time Enterprise Application Landscape
      • Disorder
      • Reduced agility
      • Reduces efficiency
      • Order
      • - Increased agility
      • Increased efficiency
      Change and expand functionality Refactoring Software architects use refactoring to fight the constant increase in system complexity
    • Greenfield Agony Renovation Paralyses Ability to Deliver Agility Pre-SOA transition SOA Enterprise IT Renovation ROAD Enterprise IT Renovation ROAD (Source: Enterprise SOA: Service Oriented Architecture Best Practices by Dirk Krafzig, Karl Banke, and Dirk Slama, Prentice Hall 2004) Change requests reduces the agility over time Change Requests Service-Oriented Architecture is a key element of an enterprise renovation roadmap
    • Paralyses Ability to Deliver Enterprise IT Road of startups Variant op : Enterprise IT Renovation ROAD In een Greenfield-situate is er geen renovatie noodzakelijk. Hierdoor kunnen de voordelen van SOA gemakkelijk worden behaald en eerder worden bereikt. Voorbeelden van bedrijven waarvoor dit geldt: Amazon,ING Direct , Dell, BOL.COM, … Agility Greenfield
    • Theory: SOA applications can share common services (a service provider component typically includes logic and data). Promises Cost savings Risk Mitigation Adequate Business infrastructure More efficient Development process Feedback At different levels Reuse Independence From technology SOA Evolutionary approach Agility (Source: Enterprise SOA: Service Oriented Architecture Best Practices by Dirk Krafzig, Karl Banke, and Dirk Slama, Prentice Hall 2004)
    • Enterprise Standards Based on strict norms and specifications that are imposed globally Enterprise Architecture Technology independent blueprint, which allows for local application structuring and flexible, global integration DBMS Application Logic Middleware Frontends 2000s: Service-Oriented Architecture 1980s: Enterprise Data Model 1990s: Enterprise Software Bus Enterprise Data Models and Software Buses were popular approaches to the challenges of enterprise computing in the 1980s and 1990s (Source: Enterprise SOA: Service Oriented Architecture Best Practices by Dirk Krafzig, Karl Banke, and Dirk Slama, Prentice Hall 2004) SOA is an architectural style (or approach)
      • Service Oriented Architecture (SOA)
      • is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains.
      • SOA reflects the reality of ownership boundaries
      • SOA is task oriented
      • SOA is inspired by human organizations
      Service Oriented Computing (SoC) = Software engineering approach Web Services standards (WS*) = Open technical standards
      • Kan niet als product worden ingekocht maar bestaat uit principes, richtlijnen en standaarden voor:
      • Het opdelen van processen in componenten (stukjes functionaliteit)
      • Het kunnen samenstellen van processen uit componenten
      Maakt gebruik van open, platform neutrale, technische standaarden Maakt gebruik van technieken waarmee gedistribueerde applicaties mogelijk zijn Herbruikbare business functionaliteit Technische interoperabiliteit Kwaliteit van de dienstverlening SOA is an architecture style, using Web Services standards Architectural styles classify architecture in terms of form, techniques, materials, … A bridge analogy
    • SOA Sleutelprincipes van service oriënteerde ontwerpen
      • Waar is het goed voor ?
      • Wat is het ?
      • Welke voordelen kunnen we er mee bereiken ?
      • Wat moet worden geregeld om de voordelen te kunnen behalen ?
    • Sleutelprincipes van service oriënteerde ontwerpen
      • Autonomie
          • welafgebakende, autonoom functionerende componenten ..
      • Servicecontracten
          • die op basis van een dienstgeoriënteerde architectuur ..
      • Losse koppelingen
          • Onderling en met externe componenten interopereren via open standaarden ..
      • Samenstelbaar
          • zodat een maximale flexibiliteit bestaat
            • om andere componenten aan te sluiten
            • om componenten toe te voegen
            • om componenten te vervangen door andere componenten ..
      • Herbruikbaar
            • om componenten te hergebruiken voor andere doeleinden ..
      • Vindbaar
      • Zonder geheugen
          • zonder impact op de bestaande componenten ..
      • Abstractie
          • in functie van
            • de evoluerende behoeften
            • de evoluerende technologische mogelijkheden
          • met beroep op open concurrentie voor de uitbouw van de aan te sluiten, toe te voegen of te vervangen componenten.
      Gebaseerd op Erl., T. (2007).SOA Princeples,www.soaprinciples .com
    • A service provider (commonly a remote server) performs some task at the request of a service consumer (the client). 1) Autonomie Service A Service description for service B Service B Self governing message 2) Servicecontracten 1) Requires work 3) Delivers result 2) Does work Service provider role Service consumer role Sleutelprincipes van service oriënteerde ontwerpen
    • Service consumers Service provider 3) Losse koppelingen 4) Samenstelbaar Data Business Process Application Infrastructure Business Process Application Data Business Process Application Data Business Process Application Infrastructure Check Status Verify Postal Code Client Name Highly Available System 5) Herbruikbaar 6) Vindbaar Enterprise Repository Sleutelprincipes van service oriënteerde ontwerpen Time Protocol Format Language Platform Location Contract
    • Sleutelprincipes van service oriënteerde ontwerpen 8) Abstractie 7) Zonder geheugen Vendor-Agnostic Context How can a technology architecture be designed to avoid inhibiting dependencies on proprietary vendor platforms? Stateless and state full stages a service passes through while processing a message Message A Send Stateless (unaware of message A) State full Receive message A Interpret message A Process message A Forward message A Message A Send Stateless (unaware of message A) Process Abstraction How can non-agnostic process logic be separated and governed independently? Entity Abstraction How can agnostic business logic be separated, reused, and governed independently? Utility Abstraction How can common utility logic be separated, reused, and independently governed?
    • SOA
      • Waar is het goed voor ?
      • Wat is het ?
      • Welke voordelen kunnen we er mee bereiken ?
      • Wat moet worden geregeld om de voordelen te kunnen behalen ?
      • Architectural Partitioning
        • Divers life cycle “speeds”
        • Synergy of different technologies
        • Optimal tech skills allocation
        • Greater maintability
        • Easier outsourcing/offshoring
      • Incremental Deployment/Maintenance
        • Gradual migration
        • Cost “spreading” across projects
        • Reduce maintenance cost
      • Reuse of Services
        • Faster time to deployment
        • Lower development cost
        • Greater adaptability of applications
      Benefits
      • Higher Upfront Costs
        • Cultural change
        • Infrastructure (SOA Backplane)
        • More formal methodology
        • Longer design time for services
        • Testing (unit/end-to-end)
      • More Distributed Infrastructure
        • Extensive use of middleware
        • Transaction management
        • Debugging/troubleshooting
        • End-to-end management
        • More granular security
        • Metering/logging
      • Tighter Management/Governance
        • Ownership/accountability
        • Cost allocation
        • Prioritization/conflict resolution
      Drawbacks Benefits and Drawbacks ? Service-Oriented Architecture Maturity Model: Where Do You Stand and Where Do You Go?, Gartner Enterprise Integration Summit, Application Integration, Web Services, SOA & BPM, Benoit Theroux, 18-19 April 2006
    • Maturity of SOA Scope of Business Integration Intra departmental Cross departmental Cross Business unit Simple B2B Complex Processes integration Maintainability Flexibility Agility Fundamental Networked Process enabled Not feasible Not cost-effective Intra-enterprise Cross-enterprise The maturity of SOA With respect to expansion stages often correlates to an enlargement of the scope of business integration Agility is the ability to detect opportunities for innovation and seize those competitive market opportunities by assembling requisite assets, knowledge, and relationships with speed and surprise (D’Aveni 1994; Goldman et al. 1995).
      • Workflow Applications
        • STP
        • Claims processing
      • Event-Based Applications
        • Risk management
        • Fraud detection
        • Real-time supply chain
        • Near-real-time data consistency integration
      • Batch Oriented Processing
        • Bill/statement printing
        • Data warehouse loading
      • “ Monitoring "Applications
        • BAM
        • Indoor positioning
        • Industrial processes
      • EDI-style B2B
      Require SOA, BPM and Events
      • Multichannel Applications
        • E-commerce
        • Internet banking
        • On-line trading
        • E-ticketing
      • Self-Service Portals
        • Customers
        • Suppliers
        • Citizens (e-government)
      • Composite Applications
        • Contact center
        • Branch operations
        • Single view of “something”
      • “ Real Time”B2B
      Fit for “pure” SOA SOA fits well with multi-channel, user-centric processes based on client/server-style, composite applications. For other classes of applications, SOA must work in combination with event-driven, BPM or batch architectures. Service-Oriented Architecture Maturity Model: Where Do You Stand and Where Do You Go?, Gartner Enterprise Integration Summit, Application Integration, Web Services, SOA & BPM, Benoit Theroux, 18-19 April 2006 Not All Applications Can Be Service-Oriented Only
    • BPM foundation standards and technologies BPM SOA Business-driven IT-driven Top-down process approach Bottom-up architectural approach Reuses process model Reuses service implementation Project-oriented Enterprise infrastructure-oriented Success measured by business metrics and Key Performance Indicators Success measured by architectural metrics, logical consistency, ease of integration, and cost of change Differences between SOA and BPM
      • UDDI
      • RSS
      • BPEL4WS
      • BPML
      • BPMN
      • ESB
      • UML
      • BPDM
      • XPDL
      SOA foundation
      • UDDI
      • SOAP
      • JCA
      • J2EE
      • BPEL
      • ESB
      • WSDL
      • XML
      • JDBC
    • BPM and SOA Unify Two Architecture Halves Into One Strategy Business Strategy Environment Technology Infrastructure Business Viewpoint Information Viewpoint Technology Viewpoint Business Context Conceptual Logical Implementation √ BPM √ SOA BPM Tames the SOA Beast: Keys to Success, Daryl Plummer, Enterprise Integration Summit, April 16-17, 2008
      • “… SOA and BPM initiatives…are more successful and the benefits are compounded when they are united”
      • “ Organizations that align their BPM and SOA initiatives in 2007 will double their likelihood of becoming an industry leader by 2011”
      • Source: BPM and SOA, Better Together, Paolo Malinverno, Janelle B. Hill, Gartner, Feb 2007.
    • Multiple reasons for BPM becoming more dynamic Business Agility Faster reactive and proactive time to market Shatter complacent business cultures based on past IT limitations Decision Making Test rule-based scenarios a lower cost Revenue Opportunities Greater product, pricing and service flexibility, allowing incremental revenue streams Customer Satisfaction More-customizable product and service offerings Regulatory Compliance Greater visibility to regulator bodies and easier change processes
    • Dynamic BPM: Where SOA, Processes, Rules and Events Come Together Inputs Selecting scenarios and Taking corrective actions Outputs What is the significance of the events/data? How do I get the process To the condition I want? In what conditioning is the process? Respond Detect Rules Events Data Optimize Model Events Condition Or State Process- and knowledge-based models enable reasoning
      • Detect
      • Diagnose
      • Explain
      • Model
      • Respond with scenario-driven rules sets
      Dynamic BPM: Where SOA, Rules, Processes and Events Come Together , Daryl Plummer Symposium/ITxpo 2008, May 12-15, 2008, Palau de Congressos de Catalunya Barcelona, Spain Diagnose and Explain Process
    • Internet The future of SOA: Were will I Source my Business Services From ? 1) On Demand Services (SaaS) 2) Purchased Services ( Packaged Applications) 3) Custom -built Services 5. Composite Process ( Packaged / Custom ) Application 4) Composite Application ( Packaged / Custom ) Services: Moving towards Enterprise SOA: How do you do that?, Massimo Pezzini, Gartner,19-06-2007 Business Impact of Services Differentiation TCO
    • Domain1 Domain2 Domain3 Reality: A larger enterprise will have disparate versions of certain SOA services in multiple business units/external parties and applications Realiteit: meerdere SOA domeinen moeten aan elkaar worden gekoppeld
      • Data integration techniques need to support multiple modes of delivery of data, including:
        • traditional batch/bulk oriented data movement,
        • creation of in-memory federated views of data,
        • low-latency capture and propagation of events and changed data.
        • Organizations need to recognize that across their environment they have data integration requirements best addressed by each of these styles.
      Master Data Management (MDM) ensures the consistency, accuracy, stewardship and accountability for the core information of the enterprise, thus enabling organizations to eliminate endless debates about "who's data is right." No "Single Version of the Truth" Problem: Solution: External party
    • SOA
      • Waar is het goed voor ?
      • Wat is het ?
      • Welke voordelen kunnen we er mee bereiken ?
      • Wat moet worden geregeld om de voordelen te kunnen behalen ?
    • Immature standards More Complex Application infrastructure Lack of governance Conflicting Packaged apps Vendors’ SOA strategy Cultural change IT cost reduction Escalating Integration needs (A2A, B2B, SaaS) BPM popularity Lowering cost and growing maturity of Enabling technology Availability of best practices Quest for Greater Business agility Packaged Application Vendor pressure Problem : Irresistible Forces Push Organizations Towards SOA Adaptation Moving towards Enterprise SOA: How do you do that?, Massimo Pezzini, Gartner,19-06-2007 Core banking vendors are upgrading architectures to meet the needs of a demanding banking market searching for flexibility. Banks should be aware of the impact of service-oriented architectures and how core banking vendors are progressing to meet that demand. Gartner, Banks and Core Banking Vendors Tap SOA for Business Growth and Efficiency, 19 July 2006
    • First SOA Project Single-Domain SOA Multi-Domain SOA Enterprise wide SOA Risk of SOA Project Failures More Risk Less Risk Time Technology Risk Lack of Governance Risk Why SOA Initiatives Fail: Technology or Governance? Moving towards Enterprise SOA: How do you do that?, Massimo Pezzini, Gartner,19-06-2007
    • SOA Basic Web Services Service-Oriented Business Applications Hype Cycle for Emerging Technologies, Gartner, July 2008 As of July 2008 Web 2.0 Emerging Technologies Hype Cycle which assesses the maturity, impact and adoption speed of key technologies and trends during the next ten years SOA Maturity Type A Type B Type C Recommended Adoption Time frame Technology Trigger Peak of Inflated Expectations Trough of Disillusionment Slope of Enlightenment Plateau of Productivity time visibility Years to mainstream adoption: less than 2 years 2 to 5 years 5 to 10 years more than 10 years obsolete before plateau
    • Experimental Mainstream Leading Edge Stages of SOA adaptation Business Goals Stage 1 Introduction Stage 2 Spreading Stage 3 Exploitation Stage 4 Plateau Address Specific Pain (e.g. Customer Portal) Process Integration (e.g. B2B) Process Flexibility (e.g. Time to Market) Continuous Adaptation & Evolution IT Goals Proof of Concept Establish Technology Platform Leverage Services Reuse Scale Up Scope Single Application Multiple Applications (Single BU) Multiple Applications (Cross BUs) Virtual Enterprise # of Published Services <25 <100 <500 >500 # of Published Consumers <5 <25 <50 >50 # of Service Call/Day <10.000 <100.000 <1.000.000 >1.000.000 # of Service Developers <10 <20 <100 >100 Enabling Technology Application Server, Portal, Adapters ESB, WSM Integration Suite , B2B SOA Reg./Rep. BPM Enterprise SOA Backplane (Source: SOA and SOBA: Becoming Mainstream and Growing Up, Gartner Teleconference, Application Integration & Middleware, Charles Abrams and Roy Schulte, Gartner,29 January 2007)
    • 3 2 1 Head of Development or Head of Integration CTO/ Head-of Architecture Head of IT Operations CIO/Business Units CEO Basic Middleware Web Services Integration Middleware Service-Oriented Development of Applications (SODA) Business Process Management Business Operations Management SOA Center of Excellence Service Life Cycle Management Service Design Methodology Planning Control and Quality Management Service Reuse Methodology Operation Management Domains Cost Allocation Schema Consistent Enterprise wide Governance Processes Enterprise wide SOA Backplane Stage 1 Introduction Stage 2 Spreading Stage 3 Exploitation Stage 4 Plateau √ √ √ √ # √ √ √ # √ √ # √ √ # # √ √ √ √ √ √ √ √ √ # √ √ √ # # √ # √ √ # √ √ # √ √ √ # √ √ # √ √ # √ √ # √ √ # √ √ # √ # √ # √ # √ Required Management Buy-in Required Skills Required Organizational Capabilities 1 2 3 4 5 1 2 3 4 5 6 1 2 3 4 5 6 7 8 9 10 √ = Imperative # = Recommended SOA Best Practices
    • Success Requires Business and IT Collaboration Achieving the benefits of SOA requires significant changes for both IT and business executives Business Strategy Business Requirements Business Process Business Architecture IT Strategy IT Solution IT Portfolio Before SOA Business Strategy IT Strategy Business Architecture Enterprise Architecture Portfolio Planning Business Solution Delivery “ Enterprise Architecture Discipline” With SOA Making the SOA Leap, Richard Mark Soley, SOA Consortium, 18 juli 2006 1+3.4+3.9
    • SOA architectuur, betekent een andere manier applicatieontwikkeling Business expertise Technische expertise Beperkte Overlap Business analisten definiëren/optimaliseren bedrijfsprocessen Applicatie ontwikkelaars applicatieontwikkeling met behulp van kerntechnologieën 1) Traditionele applicatie ontwikkeling 2) Service georiënteerde ontwikkeling Applicatie ontwikkelaars (nieuwe stijl) omzetten van bedrijfsprocessen in applicatie door de assemblage en configuratie van bouwmodules Grote Overlap Service ontwikkelaars Ontwikkelen van modules, patronen, templates en componenten met behulp van kerntechnologieën Technische expertise Business expertise Gebaseerd op de presentatie: Service Oriented Architecture, C. Mohan, Ph.D., IBM Corporation Business analisten definiëren/optimaliseren bedrijfsprocessen 2+3.1+3.3
    • How do you enforce reuse of services ?
      • #Service / #Consumers >>20
      • Percent of reused services < 10%
      • Too fine services granularity
      • Duplicated services
      • Over-specified SOA
      Service Definition Process Application Reuse-Oriented Chargeback Schema Service Registry Application Application “ Bad” SOA “ Good” SOA 3.3+3.6+3.8 Process (1) (2) (3)
    • Transformation and Routing Orchestration Administration HTTP SOAP MQSeries Proprietary Message Bus Adapter Application Web Service POX Service Registry- Repository Adapter Application Design Tooling Management Tooling Data Mapping Process Design Management Analytic's Monitoring Services Integration Suites = Messaging Infrastructure + Sophisticated Tooling Understanding ESBs and Other SOA Infrastructure Alternatives, Enterprise Integration Summit, Gartner, Jess Thompson, April 16-17, 2008 2+3.10 Tooling Infrastructure
      • Standards support
      • MOM qualities of services (=MQseries)
      • Security, Compliance, Administration
      • Extensibility via plug-in feature
      POX is een voorbeeld van een Web2.0 “standaard”
    • IS Agility Building Activity Environmental Change Factors Internal Change Factors Rate of Changes in Business Requirements Business Requirements Process Discrepancy Rate of changes in IS IS Inertia IS Appropriateness Pressure to Change IS Business Performance Business Agility Rate of changes in Core Business Process Business Appropriateness Organizational Inertia Migration Cost projection Requirement of Business Process Transparency Standardization Technology Technology Appropriateness Pressure to Change Business Competence Diffusion of Emerging Technology Pressure to adopt Emerging Technology Process and Service Complexity Security Requirements Systems performance Requirements Skill Gaps Need to expand Skill sets Training Turnover Recruit Contract Business Agility Building Activity Skills Set - - Value = Agility Skill Management Skill obsolesce + - + + - + - + - + + + + + + - - - + - - + + - + - - - - IT-Business Discrepancy + + - Adaptation + - - - + + Business-Technology Value Model Business Driven Strategy for Service-Oriented Architecture: A Systems Dynamics Approach, Jae Choi, Proceedings of IBM PhD Student Symposium at ICSOC 200 7, September 2007, pp. 19-24 3.4+3.8 IS Agility SOA
    • A Framework guides the examination of business benefits of SOA Bron: IBM Institute for Business Value “The Business Value of Service Oriented Architecture” 2006 Cost en Benefit analyses Focus Area’s 3.4+3.8 Reduced Operational Risk Improved flexibility Improved ability for compliance Ease of Integration New product Development enabeld Improved Ability to Change Increased reuse Reduced time–to- market Reduced Integration Reduced Integration cost Reduced maintenance cost Reduced processing time Reduced errors Reduced systems downtime Existing Revenue Increased New revenue generated Existing Revenue Protected Increased revenue Decreased Costs = Flexibility value drivers = Profitability drivers Increased Profitability
    • SOA
      • Waar is het goed voor ?
      • Wat is het ?
      • Welke voordelen kunnen we er mee bereiken ?
      • Wat moet worden geregeld om de voordelen te kunnen behalen ?
    • SOA Geraadpleegde boeken : Enterprise SOA: Service Oriented Architecture Best Practices by Dirk Krafzig, Karl Banke, and Dirk Slama, Prentice Hall 2004). Service-Oriented Architecture (SOA): Concepts, Technology, and Design (Prentice Hall Service-Oriented Computing Series from Thomas Erl), Thomas Erl, 2005. The New Language of Business: SOA & Web 2.0, Sandy Carter, IBM Press, 2007. Geraadpleegde internetpagina’s: http://www.diigo.com/list/richardclaassens/soa