InfoQ

InfoQ

News

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.

Interview: Mule Founder Ross Mason on ESBs

Posted by Floyd Marinescu on Jan 25, 2007

Sections
Enterprise Architecture
Topics
SOA ,
EAI ,
ESB
Tags
Mule
In this latest InfoQ video interview, Mule founder Ross Mason talks about the the role of the ESB, when to use and not to use ESBs, BPEL, and ESBs vs. integration brokers. Mule is an open source ESB whose professional open source backing company MuleSource recently received $4M of financing.

Watch Ross Mason on Mule and the role of ESBs (17 min)

Asked about how people should generally map requirements to services on a bus, Ross explained:
A requirement might be that's traditionally trades may be handled by back-office entering it manually, they enter it manually into an accounting system that has some sort of interface to the general ledger and it also goes to auditing and reporting. There's quite a lot of manual process involved. There's no consistent path for the information but yet is something that can be automated; once it is automated you can improve it, you can add more functionality, you can get better reporting statistics you can get more reliable and up-to-date information. The requirements are to really use your information more efficiently and free up your resources to be working on other things. How that maps to the actual architecture is the bus is that communications channel to get all those systems to talk to each other. That's the basic need.
Recently, the Mule team released version 1.3 in which they devoted a lot of time to performance improvements. While Mule has been known to handle over 1 million transactions a day, they rewrote the Http transport to be more efficient and to support message chunking. Similarly, they have improved the JMS system to manage receiver threads and session caching.   See also InfoQ's article on Mule: Evolutionary Integration with ESBs.   

In the interview, Ross also revealed that Mule got its name because it takes the donkey work out of integration projects.
  • This article is part of a featured topic series on SOA
Mule & ESB by JAVAID ASLAM Posted
  1. Back to top

    Mule & ESB

    by JAVAID ASLAM

    This interview presents nothing new, no depth.
    why should one choose Mule over any other ESB?

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.