BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ
News Articles Presentations Podcasts Guides

Topics

Choose your language

QCon New York

Find real-world practical inspiration from the world’s most innovative software leaders. Attend in-person or online.
QCon San Francisco

Learn what's next in software from world-class leaders pushing the boundaries. Attend in-person or online.
The Software Architects' Newsletter

Your monthly guide to all the topics, technologies and techniques that every professional needs to know about. Subscribe for free.

InfoQ Homepage News Presentation: Gregor Hohpe on Conversations Between Loosely Coupled Services

QCon San Francisco (Oct 2-6, 2023): Find real-world practical inspiration from senior software engineers.

Presentation: Gregor Hohpe on Conversations Between Loosely Coupled Services

Bookmarks

Aug 08, 2007 less than one minute

Write for InfoQ

Join a community of experts. Increase your visibility.
Grow your career.Learn more
Interactions between loosely-coupled services are simple, as long as only two parties are involved, and their interaction is of the synchronous, blocking, request/reply variety. But concepts become more complex when long-running conversations and asynchronous interactions need to be supported.

In this new InfoQ presentation, recorded at JAOO, Google architect Gregor Hohpe introduces various concepts for to manage more complex interactions between services, including conversations, choreography, and orchestration. He provides a down-to-earth look at these concepts along with the associated Web services standards like WS-BPEL and WS-CDL, and identifies common patterns in service conversation.

Watch the full presentation.

Rate this Article

Adoption
Style

This content is in the Enterprise Architecture topic

Related Topics:

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • WS-BPEL and WS-CDL should live together

    by Paulo Michels,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I think WS-BPEL and WS-CDL can and should live together, each one giving its best. As Hohpe said, WS-BPEL is intended for process execution, but focus just on one side of the conversation and in my opinion that difficults modeling large and loosely coupled systems. WS-CDL can help on modeling those system by giving a whole view of the conversations and allowing the automatic generation of the endpoints, even BPEL as described by Hohpe.
    In my opinion WS-CDL is not yet enough mature and its xml syntax is not easily readable. For professional use we must get the help of tools like Pi4SOA.

    Nice presentation!

    Back to top
  • Is it possible to download this Presentation?

    by hower eisen,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Hi Floyd! The presentation system DOSE NOT works smoothly in my laptop with my ASL about 2M brandwidth. Is it possible to let us to watch InfoQ's presentation in off-portal style?

    Back to top
  • Re: WS-BPEL and WS-CDL should live together

    by Steve Ross-Talbot,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I agree completely. I would add three things specifically:

    1. The pi4soa tool suite from Pi4Tech is now pretty robust and much easier to use. It is open source so try it out.

    2. We have provided BPEL generation from WS-CDL for well over 1 year. Oddly enough few people seem to really want it, rather they generate Java directly or use UML generation.

    3. BPEL is not the only end point executable language but it is an important one to have under your belt.

    Gregor has done a great job in explaining what WS-CDL is for. I would say that it provides a standard-based language supported by formalism to ensure correctness and methodology to ensure that it fits in the grand scheme of things and that it is positioned as a means by which architects can describe their SOA in the large and realise the SOA through a number of executable language. All of this with formal type guarantees of correctness.

    Back to top

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT