1

I am trying to get a clear definition of Mule esb and have read a few places Mule is a messaging framework and a "highly distributed object broker".

What does it mean by that its an object broker? Is it that it can expose services over a network? Is camel an object broker too, or just a messaging framework? Can you expose services over a network with camel without a container? Is that what differentiates them?

jon lee
  • 887
  • 1
  • 15
  • 32
  • Could you maybe provide the links where you have read that? But in my eyes that seems like bullshit, Mule is an ESB. – Claus Ibsen May 03 '14 at 06:44
  • 1
    And to see what Apache Camel is, see this - http://stackoverflow.com/questions/8845186/what-exactly-is-apache-camel – Claus Ibsen May 03 '14 at 06:45

1 Answers1

3

This was the original tagline of Mule, way before Gartner has popularized the ESB term.

At this time (2005), Mule was built around the notion of Universal Message Objects (UMOs) and, as such, was positioning itself to become a scalable, distributed container for these UMOs. Hence the "highly distributed object broker" terminology.

After time, the object container aspect of Mule has become less important than its pure integration capacities.

Moreover, it's harder to sell an "object broker" to a C-level executive than an ESB. So this whole terminology has now been brought back in the shadow of history.

David Dossot
  • 33,403
  • 4
  • 38
  • 72