Service Oriented Computing

  • 630 views
Uploaded on

 

More in: Technology , Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
630
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
29
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

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