In this presentation, 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.
Gregor Hohpe is a software architect at Google, author of "Enterprise Integration Patterns" and a frequent speaker at conferences around the world.
JAOO is the premier European developer conference on software technology, methods and best practices. The conference presents in-depth presentations and tutorials by researchers, engineers and trend-setters in software engineering and technology.
WS-BPEL and WS-CDL should live together
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.
Is it possible to download this Presentation?
Re: WS-BPEL and WS-CDL should live together
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.