InfoQ

InfoQ

Presentation

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Recorded at:
Recorded at

Does My Bus Look Big in This?

Presented by Martin Fowler & Jim Webber on Jun 06, 2008 Length 00:42:20
Sections
Architecture & Design,
Enterprise Architecture
Topics
REST ,
SOA ,
ESB ,
Web Services
Tags
QCon London 2008 ,
QCon ,
SOA Appliance
The next QCon is in London March 5-9, Join us!
 

How would you like to view the presentation?

In case you are having issues watching this video, please follow these simple steps to help us investigate the issue:
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
Summary
In this presentation, recorded at QCon London 2008, ThoughtWorks' Chief Scientist Martin Fowler and Global Head of Architecture Jim Webber share their views of the typical corporate ESB, which in their view has grown too fat for its own good. Martin and Jim suggest the Web's architecture as a possible and more light-weight alternative, in line with their preference for agile approaches.

Bio
Dr. Jim Webber is the Global Head of Architecture for ThoughtWorks where he works with clients on delivering dependable service-oriented systems. Martin Fowler is a well-known author, speaker and consultant who pioneered object-oriented technology, refactoring, patterns, agile methodologies, domain modeling, the Unified Modeling Language (UML), and Extreme Programming.

About the conference
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community.QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
  • This article is part of a featured topic series on SOA

20 comments

Watch Thread Reply

One of the best presentations of the event by Sadek Drobi Posted
So, the solution for EAI is some ad hoc services? by Ronald Miura Posted
Re: So, the solution for EAI is some ad hoc services? by Michael Neale Posted
Brilliant! by Rickard Öberg Posted
Excellent Presentation! by siva prasanna kumar P Posted
Re: Excellent Presentation! by Jim Webber Posted
Re: Excellent Presentation! by Diana Plesa Posted
Re: Excellent Presentation! by siva prasanna kumar P Posted
Discussion "raging" elsewhere ... by Mark Little Posted
Facts? by Jean-Jacques Dubray Posted
Re: Facts? by Jim Webber Posted
Finally some sense of SOA by R R Posted
Re: Finally some sense of SOA by Stefan Tilkov Posted
Well Well...so SOA :) by Gaston Coco Posted
Very much in alignment... by Carlos Perez Posted
Out of Touch by Brett Huber Posted
Gorilla SOA by Eric Roch Posted
Re: Gorilla SOA by Brett Huber Posted
Re: Gorilla SOA by Eric Roch Posted
Vendors hijacking the principles by Alberto Brandolini Posted
  1. Back to top

    One of the best presentations of the event

    by Sadek Drobi

    I really enjoyed this one. In QCon london 2007 I really liked the presentation Dan North and Martin Fowler did by then. I consider this one as a continutation!

  2. Back to top

    So, the solution for EAI is some ad hoc services?

    by Ronald Miura

    Doesn't it lead to an ad hoc, spaghetti net of interdependencies between systems? It may work while it's small, but will it still work while it grows?

    It seems like 'I got it done, it works, but how to manage it in the long term is not my problem'.

    I don't think big, complex ESBs are the solution, but I'm not sure ad hoc services are, either.

  3. Back to top

    Re: So, the solution for EAI is some ad hoc services?

    by Michael Neale

    Shhhh... don't let reality interrupt the arm waving !

    Seriously though, yes web architectures can scale - but that implies behind the firewall there will have to be web style infrastructure - stuff like DNS servers and so on. The current view of using web based tech in enterprise forgets that the web actually has some pretty powerful "middleware" out there behind the scenes that most of the time Just Works, hence we forget about it. Replicating that in the enterprise would not be trivial.

  4. Back to top

    Brilliant!

    by Rickard Öberg

    Absolutely brilliant stuff! I listened to Jim's Guerilla SOA talk earlier this year, and was hoping to find a good online presentation to send around whenever these kinds of issues come up, and now I've got one. Excellent!

  5. Back to top

    Excellent Presentation!

    by siva prasanna kumar P

    Excellent way of presenting the SOA reality, Gureilla SOA seems promising but a practical example of implementing such a Guerilla SOA based system will be very very helpful.

    Every one(seem to) understand that pushing the complexity on to web is a good idea but how to do that is the Question? (Answer REST??)


    how can I use REST for building Business Processes? I have no idea how to ;) in fact I believe REST was not meant for that. (its ROA not SOA and R may not always S, inturn S can be using many R's, hope you got what I am pointing out!)

    Every one say REST!= CRUD they say internet is an example for that,is it justified? what are we doing on internet other than CR ??

    Hope I am not taking off this conversation, I felt Gureilla SOA will be a combination of SOA and REST.


    Again I am kind off biased with this article about REST style and SOAP Style.

    Thanks all, for such a nice community to share the thoughts.

  6. Back to top

    Discussion "raging" elsewhere ...

    by Mark Little

  7. Back to top

    Facts?

    by Jean-Jacques Dubray

    It would be good if Jim and Martin could get their facts right, and not just about historical constructions. Here is the history of the bridge they make fun of: en.wikipedia.org/wiki/Pont_Saint-B%C3%A9nezet. The reminder of the presentation is just as atrocious.

  8. Back to top

    Re: Excellent Presentation!

    by Jim Webber

    Hi Siva,

    I gave another talk at QCon last year called "A Couple of Ways to Skin an Internet-Scale Cat" which details how to do boring enterprise-y things like workflow using Web technologies. I don't know if that video will ever be released, but you can grab the slide deck from my Web site, jim.webber.name/presentations.html

    Jim

  9. Back to top

    Re: Facts?

    by Jim Webber

    Thank you for your input JJ. I feel it's a badge of honour to receive your validation.

    Jim

  10. Back to top

    Re: Excellent Presentation!

    by Diana Plesa

    Hi Jim


    Yes we have your presentation from QCon San Francisco on the scheduled as will be released the first week of August.


    Diana

  11. Back to top

    Re: Excellent Presentation!

    by siva prasanna kumar P

    Thanks for the reply Jim and Diana, looking forward for that presentation.

  12. Back to top

    Finally some sense of SOA

    by R R

    Having worked in SOA environment for a while, I will have to agree with this presentation completely. Nice work guys! It is very funny too. I am sure that this presentation does not impress the enterprise architects as it threatens thier monopoly. The fact is that it does not have to. I used to be in that camp but not any more. And I am glad that I made the switch to the reality.

  13. Back to top

    Well Well...so SOA :)

    by Gaston Coco

    hi, maybe Martin and Jim are wrong, We daily need to integrate different kinds of systems, different

    technologies...i don't think squid can do that (by the way...i have installed squid ;) ), today bussinesses

    are more than a simple WS that responds with data (in any format you like....but data) today bussinesses

    need integration stuff that i don't think you can do with a few WS-REST.


    My experience integrating different Enterprise Applications is that ESB can do a lot for you, maybe you

    can play with incremental services published inside the ESB.


    Martin and Jim are like those generals outside reality, please switch to the reality.


    Pd: How you can integrate a CICS with a J2EE application? come on...using WS-REST.

  14. Back to top

    Re: Finally some sense of SOA

    by Stefan Tilkov

    R R, thanks for your comment. Would you be nice enough to edit your profile and put in your real name? Although we haven’t published any restriction from using aliases, the intent for InfoQ discussions is to maintain a level of professionalism, in which using real names is an important factor. Thanks!

  15. Back to top

    Very much in alignment...

    by Carlos Perez

    with a couple of my thoughts:

    On the use of Squid as middleware:

    www.manageability.org/blog/stuff/cache-tier-arc...

    On the use of lean methodology for SOA:

    www.manageability.org/blog/stuff/why-soa-2-dot-0

    Carlos

  16. Back to top

    Out of Touch

    by Brett Huber

    This presentation clearly shows Martin is out of touch with the reality and technical trend and does not understand what SOA and ESB really mean and can do to business. The way they have been promoting can only work in a well defined/smaller project, which is not the case in larger business today, which has chaos of mixture of applications and data sources.

    And also very often, business refuses to accept "small things that work". They want us to deliver entire thing that work and bring the competitive advantages.

  17. Back to top

    Gorilla SOA

    by Eric Roch

    The presentation by the Agile gurus Jim Webber and Martin Fowler "Does My Bus Look Big in This?" was very disappointing in my opinion.

    I watched the presentation hoping to learn some new approaches to SOA. But the presentation says middleware is bad, big SOA projects are bad and Agile is still great so keep buying the books. Unfortunately some SOA projects really are big but SOA experts already know to decompose and iterate them as much as possible. I do agree with their points on iteration and continuous integration, which is fairly well accepted in the SOA community.

    Their good proxy diagram that replaces the bad middleware diagram this is just semantics. Isn't a proxy middleware too if it does anything to help the developer with integration problems? Also, middleware does not have to be expensive that only "stupid" CIOs buy. There is an open source SOA logo on the screen right behind the presenters. Middleware is becoming a commodity.

    The problem most companies face is not how to develop new application in an agile fashion. Most IT shops are buying ERP, CRM, SCM packages and maintaining legacy systems. SOA and middleware can help with integration problems and it does not have to be expensive or big bang.

    This just looks like an attempt to protect their Agile franchise from the threat of SOA.

    blogs.ittoolbox.com/eai/business/archives/goril...

  18. Back to top

    Vendors hijacking the principles

    by Alberto Brandolini

    Great presentation!

    It's interesting to notice that SOA implementation actually differs quite a lot from he original intentions. I bet big vendors played quite a role in that. To some customers, SOA was a chance to get rid of some nasty vendor lock in, but this turned into an opportunity for the same vendor to feed in some more tools, more or less useful.

    However the main struggle goin'on is about size. Agile principles aim for small but continuous increment, but SOA is too often sold as a "big plan" that will require "big operations" to be delivered in a "big bang" fashion or require a "big team" or adetailed "top-down" specification. It's somewhat hard to define "big" or "small" in a huge organization, but the way the whole stuff is "sold" really makes a difference.

    However, nobody wants to turn the ESB into a mess repository, ...but still looks like a good tool to deal with legacy systems.

  19. Back to top

    Re: Gorilla SOA

    by Brett Huber

    Agreed.

  20. Back to top

    Re: Gorilla SOA

    by Eric Roch

    Related article - mine.

    How to use ESBs for SOA

Educational Content

Questions for an Enterprise Architect

Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?

Wrap Your SQL Head Around Riak MapReduce

Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.

Polyglot Persistence for Java Developers - Moving Out of the Relational Comfort Zone

Chris Richardson shows how he ported a relational database to three NoSQL data stores: Redis, Cassandra and MongoDB.

The Golden Circle – Why How What

Jean Tabaka challenges the audience to reflect on what Agile practices they are employing, how they are using them, ending with the questions “Why have their organization chosen to go Agile?

The Web Platform as a Limitless Pool of Innovation, with Andreas Gal

Andreas talks about the benefits of the Open Web and how it compares to proprietary stacks. He also talks about various projects that push the envelope like Boot to Gecko, Broadway and pdf.js.

Hadoop and NoSQLin a Big Data Environment

Ron Bodkin discusses early adoption of Hadoop, NoSQL and describes MapReduce and related libraries and Frameworks. Other topics include Hive, Pig, multi tenancy, and security in a big data environment

Spring and Platform Interoperability

Stephen Bohlen explains how Spring helps with interoperability between Java and .NET, demoing it with the help of a sample application.

How to Stop Writing Next Year's Unsustainable Piece of Code

Guilherme Silveira mentions some of the turning points in project development that may affect the quality of the code offering advice on avoiding writing crappy code.