Scribd Logo
Upload

Welcome to Scribd!

  • Web Languages: Part II - Advanced Topics

    Uploaded by

    ernestohp7
    18 views18 pages
    This document discusses advanced topics in web languages, including approaches to designing service-oriented systems, properties of interactions, policies, coordination, business protocols, transactions, service buses, and composition and mashups. It encourages developing a useful service by combining building blocks, publishing them as web services, and adopting an interface-first approach. It emphasizes writing clear and maintainable interfaces and code according to principles like simplicity, readability, and minimizing dependencies. It also provides statistics on growth in the number of APIs and mashups available.

    Original Description:

    web

    Original Title

    Lesson 3 Intro Part II

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document discusses advanced topics in web languages, including approaches to designing service-oriented systems, properties of interactions, policies, coordination, business protocols, transactions, service buses, and composition and mashups. It encourages developing a useful service by combining building blocks, publishing them as web services, and adopting an interface-first approach. It emphasizes writing clear and maintainable interfaces and code according to principles like simplicity, readability, and minimizing dependencies. It also provides statistics on growth in the number of APIs and mashups available.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    18 views18 pages

    Web Languages: Part II - Advanced Topics

    Uploaded by

    ernestohp7
    This document discusses advanced topics in web languages, including approaches to designing service-oriented systems, properties of interactions, policies, coordination, business protocols, transactions, service buses, and composition and mashups. It encourages developing a useful service by combining building blocks, publishing them as web services, and adopting an interface-first approach. It emphasizes writing clear and maintainable interfaces and code according to principles like simplicity, readability, and minimizing dependencies. It also provides statistics on growth in the number of APIs and mashups available.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 18

    Web Languages

    Part II Advanced Topics

    The Journey till now


    WSDL interfaces customer supplier

    SOAP-based middleware

    SOAP messages (invoke)

    SOAPbasedmiddleware

    UDDI registry

    SOAP messages (bind)

    SOAP-based middleware

    SOAP messages (publish)

    Part II
    Approach to designing service-oriented systems Properties of the interaction Secure Reliable Routing

    Policies
    Coordination Business Protocols Transactions Service Bus Composition and Mashups

    Part II - Project
    Develop a useful service combining building

    blocks

    Publish them as web services and make them

    available as Web pages

    Adopt interface-first approach BPEL

    A note on interfaces
    The art of KISSing

    Quality of code (and of interfaces)


    http://www.osnews.com/story/19266/WTFs_m

    good code (and interfaces)


    Despite deadlines, take time to write good

    code.

    Good code does not help only for doing

    maintenance next year, it will help you doing maintenance in a couple of hours.
    LeBlancs law: later equals never Robert Martin: Take the time to go fast Poor code will slow you down even before the

    deadline

    Characteristics of good code


    Stroustrup: elegant, straightforward (make it hard for

    bugs to hide)

    Thomas: can be read and enhanced by somebody

    else. Includes testing. Minimal dependencies, Minimal API

    Featers: looks like written by someone who cares Booch: reads like well-written prose
    (from Clean Code, by Robert Martin. Read also effective java, by Joshua Bloch)

    Google Big Table

    What about Web services interfaces


    The same, but with MORE emphasis on simplicity SERVICE DESCRIPTION AND INTERFACES SPECS

    ARE WRITTEN FOR OTHERS TO READ. THINK ABOUT THE READER

    If the specs are not clear, its your fault If the specs are not clear, your service does not

    get used

    REMEMBER THE HOW TO

    Dynamics of the ecosystem


    Constant growth since programmableweb.com went online (over 600 days) [by Michael Weiss, Carleton University]
    Number of APIs Number of mashups

    Some figures (programmableweb.com)


    Most popular categories of mashups

    Most popular

    web APIs

    Protocol usage by APIs

    Composition and Mashups

    Choreography vs Composition
    A B

    Service composition
    .net WAS

    Web service

    Web service
    Business Process

    Web service

    Web service
    Legacy integration

    CICS

    WS-BPEL defines a model and a grammar for describing the behavior of a business process based on interactions between the process and its partners. 17 each partner occurs through Web Service interfaces. The interaction with

    (Enterprise) Application Integration


    .net WAS

    Business Process

    SOAP

    RMI/IIO P Legacy integration MQSeries

    CICS
    MQSeries

    Delivery channels
    18

    You might also like