InfoQ

News

Interview: Jim Webber on "Guerilla SOA"

Posted by Stefan Tilkov on Aug 24, 2007 04:56 AM

Community
SOA
Topics
WS Standards ,
Web Services ,
REST
Tags
WSDL ,
SSDL ,
MEST
In this interview Jim Webber, Service-oriented Systems Practice Lead at ThoughtWorks, explains his ideas behind "Guerilla SOA" – a somewhat agile approach to SOA that relies on small steps instead of a large-middleware-centric route towards service-enabling an enterprise. Jim also advocates MEST (MESsage Transfer), an architectural style that focuses on messages the same way REST focuses on resources. In Jim's opinion, the problem with most current Web services stacks are rooted in WSDL's notion of operations, which he deems to be the wrong abstraction for SOA.

Watch the full interview (24 minutes).
RE: MEST by Jan Vegt Posted Aug 25, 2007 4:43 PM
Links to references by Joshua Graham Posted Aug 28, 2007 3:22 PM
Seems not that new by Stefano Pogliani Posted Sep 8, 2007 6:22 PM
A different approach with difference strenghts and weaknesses by Johannes Brodwall Posted Sep 13, 2008 7:56 PM
  1. Back to top

    RE: MEST

    Aug 25, 2007 4:43 PM by Jan Vegt

    Based on experiences in SOA projects for the past few years as a Business/EAI/Data architect I am very impressed with the MEST idea. In the excellent interview with Anne Thomas Manes a few weeks ago here on InfoQ almost everything she said made a lot sense (in reference to my own experience) apart from one thing: this central notion and importance of type. Personally I think the MEST approach is a convincing answer. Thanks very much for publishing this interview, Jan ( Jan Vegt, 42, The Netherlands )

  2. Back to top

    Links to references

    Aug 28, 2007 3:22 PM by Joshua Graham

    My blog entry about this interview includes links to some of the sites and people Jim mentioned. http://grahamis.com/blog/2007/08/25/soa-101/

  3. Back to top

    Seems not that new

    Sep 8, 2007 6:22 PM by Stefano Pogliani

    What you describe here resembles very much to: 1. ebXML, for the message-oriented framework with Business Messages focus 2. WSCI, as a way to describe long-running conversations Where are the differences between what you describve here and what I pointed out? Thanks a lot Regards /Stefano

  4. RPC is highly coupled and often unrobust. On the other hand, message style requires a lot of work to do simple things. The design of a web system that uses a message-oriented style to query a data oriented services is not pretty.

    The danger of RPC style is that we use it to integrate systems that should be decoupled. The danger of messaging style is if we use it to distribute things that really should be colocated. Fowler's first law of distributed computing will always be relevant. Let's stop using shining new tools as an excuse to ignore it.

Educational Content

Bindings, Platforms, and Innovation

This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.

Orchestrating Long Running Activities with JBoss / JBPM

This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.

Neo4j - The Benefits of Graph Databases

This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.

Realistic about Risk: Software development with Real Options

This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.

Communication Flexibility Using Bindings

This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.

Writing DSLs in Groovy

After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.

Scaling Agile with C/ALM (Collaborative Application Lifecycle Management)

IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.

Concurrent Programming with Microsoft F#

Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.