Service Oriented Computing


Published on

Published in: Technology, Education
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Service Oriented Computing

  1. 1. Service-Oriented Computing:State of the Art and Research Challenges<br />Aiesa bin Saad, 4209A126-2<br />Nakazato Lab<br />
  2. 2. Paper background<br />Author:<br />Micheal P. Papazoglou, Tilburg University<br />Paolo Traverso, Instituto per la Ricerca Scientifica e Technologica<br />Schahram Dustdar, Vienna University of Technology<br />Frank Leymann, University of Stuttgart<br />The First International Conference on Service Oriented Computing 15-18 December 2003, Trento - Italy<br />2<br />
  3. 3. What is SOC?<br />Promotes the idea of assembling application components into a network of services to create applications.<br />Uses “services-oriented” programming to develop application by using network-available services.<br />Web services are currently the most promising SOC-based technology. Uses internet-based standards:<br />Simple Object Access Protocol (SOAP)<br />Web Services Description Language (WSDL)<br />Business Process Execution Language for Web Services (BPEL4WS)<br />3<br />
  4. 4. What is SOC?<br />SOC vision: it will be possible to easily assemble application components into a loosely coupled network of services.<br />These services is used to create dynamic business process and agile applications across organizations and computing platforms.<br />Key to achieve this vision: Service-oriented Architecture (SOA):<br />Logical way of designing a software system;<br />Provide services either to end-user applications or other services distributed in a network;<br />Published and discoverable interfaces.<br />4<br />
  5. 5. SOC Research Roadmap<br />Role actions<br />Performs<br />Publishes<br />Uses<br />Become <br />Management <br />and monitoring<br />Managed services<br />Service operator<br />Metrics<br />State management<br />Load balancing<br />Change management<br />Service characteristic:<br /><ul><li> Semantics
  6. 6. Nonfunctional characteristics
  7. 7. Quality of Service (QoS)</li></ul>Composite services<br />Coordination<br />Conformance<br />Transaction <br />Composition<br />Basic services<br />Service provider<br />Publication<br />Foundation<br />(service-oriented middleware and basic functions)<br />Discovery<br />Selection<br />Binding<br />Capability<br />Interface<br />Behavior<br />Service client<br />Service aggregator<br />5<br />
  8. 8. SERVICE FOUNDATION<br />Consists of service-oriented middleware backbone.<br />Basic service funcionality definition: description, publishing, finding and binding of services.<br />Typical service-based scenario:<br />Provider hosts network-accessible software module, defines a service description and publish the service and make it discoverable.<br />Client discovers a service, retrieve the service description.<br />Client use service desc. to bind to the provider and invoke the service.<br />Service aggregators group services by other providers and can also act as providers.<br />6<br />
  9. 9. SERVICE FOUNDATION<br />The concept of enterprise services bus – a capable and manageable integration infrastructure for web services and SOA.<br />Two objectives of ESB:<br />Loosely couple the systems taking part in the integration, and<br />Break up the integration logic into distinct, easily manageable pieces.<br />Open-standards-based message backbone.<br />Using middleware technology to enable SOA and alleviate disparity problems<br />State of the art<br />7<br />
  10. 10. SERVICE FOUNDATION<br />State of the art<br />8<br />Enterprise service bus. The ESB connects diverse applications and technologies<br />
  11. 11. SERVICE FOUNDATION<br />Dynamically reconfigurable runtime architecture.<br />End-to-end security solutions.<br />Infrastructure support for data and process integration.<br />Semantically enhanced service discovery.<br />Research challenges<br />9<br />
  12. 12. SERVICE COMPOSITION<br />Aggregating multiple services into single composite service.<br />Resulting composite services:<br />used as a basic service for further composition, or<br />Offered as complete applications<br />Service aggregators become service providers – publishing the service descriptions of the composite service they create.<br />Aggregators also enforce policies on aggregate service invocations.<br />10<br />
  13. 13. SERVICE COMPOSITION<br />Developers use the term:<br />Orchestration: Describes how service interact at the message level. Achieved via BPEL4WS and other XML-based process.<br />Choreography: Public message exchange, rules of interaction and agreements that occur between multiple business-process end points. Achieved via the Web Services Choreography Description Language (WS-CDL).<br />to describe business interaction protocols that coordinate and control collaborating services.<br />State of the art<br />11<br />
  14. 14. SERVICE COMPOSITION<br />Compatibility analysis for replaceability, compatibility, and process conformance.<br />Dynamic and adaptive processes.<br />QoS-aware service compositions.<br />Business-driven automated compositions.<br />Research challenges<br />12<br />
  15. 15. SERVICE MANAGEMENT AND MONITORING<br />Service management: A range of activities, from installation and configuration to collecting metrics and tuning, to ensure responsive service execution.<br />Service monitoring: Monitoring events or information produced by the services and processes; viewing process-instance statistics; viewing the status of selected process instances; and suspending, resuming or terminating selected process instances.<br />13<br />
  16. 16. SERVICE MANAGEMENT AND MONITORING<br />State of the art<br />14<br />Web service management architecture. The architecture provides a continuous connection between the application and management channels. The application comprises business processes that integrate basic services originating from two collaborating enterprises.<br />
  17. 17. SERVICE MANAGEMENT AND MONITORING<br />Self-configuring management services.<br />Self-adapting management services.<br />Self-healing management services.<br />Self-optimizing management services.<br />Self-protecting management services.<br />Research challenges<br />15<br />
  18. 18. SERVICE DESIGN AND DEVELOPMENT<br />Well-constructed SOA provides flexible infrastructure and processing environments to business entity.<br />Provisioning independent, reuseable automated business processes as services and providing a foundation for leveraging these services.<br />SOAs must rely on an evolutionary software engineering approach.<br />Partly builds upon earlier processes including component-based development and business process modeling.<br />16<br />
  19. 19. SERVICE DESIGN AND DEVELOPMENT<br />SOA’s key element (services, information flows, and components realizing services) has to be address in software development.<br />Currently developers use SOAP/WDSL/UDDI atop existing applications or components that implement the Web services.<br />They port existing components to Web services by creating wrappers and leaving the underlying component untouched – focus on interface.<br />This is insufficient and properly delivering components’ functionality through a Web service takes serious redesign effort.<br />* older software development paradigm for object-oriented and component-based development cannot be blindly applied to SOA and Web services.<br />State of the art<br />17<br />
  20. 20. SERVICE DESIGN AND DEVELOPMENT<br />Engineering of service applications.<br />Flexible gap-analysis techniques.<br />Service versioning and adaptavity.<br />Service governance.<br />Research challenges<br />18<br />
  21. 21. 19<br />Opera Unite <br />