MuleSoft releases proprietary JMS server



Email    print   
January 20, 2010 —  (Page 1 of 2)
MuleSoft, the company that produces the open-source Mule ESB, has licensed a proprietary Java Message Service (JMS) server to provide a more reliable commercial messaging solution for its customers, leading an analyst to question its commitment to open-source development.

MuleSoft's version of that product, called Mule MQ, became generally available Tuesday for US$4,400 per CPU; support packages are available for a separate charge.

The company chose to license a JMS server from an unnamed OEM because its customers were encountering reliability problems with Apache ActiveMQ, said CTO Ross Mason. MuleSoft customers had previously used ActiveMQ.

"There were problems with clustering. It doesn't cut it, and no one supports it," Mason explained. "We took the OEM's JMS Server and added some extra bells and whistles. We spent months making it a fine-tuned product."

Performance was MuleSoft's primary focus, he said, claiming that Mule MQ achieve up to five times the performance of ActiveMQ for some use cases.

The server includes integrated management and monitoring tools.

Mule MQ is compliant with the JMS 1.1 specification and is deployable as a standalone messaging server or embedded in a MuleSoft iBeans application container, according to the company.

iBeans is a container that runs inside of Apache Tomcat, MuleSoft's Tcat Server (a commercial edition of Tomcat), and the Mule ESB. MuleSoft introduced iBeans in September.

iBeans and Mule ESB are open-source projects, but Mule MQ is the second closed-source product that the company is selling, along with Mule Data Integrator.

MuleSoft's recent embrace of closed-source software prompted Burton Group research director and vice president Anne Thomas Manes to question whether it was transitioning away from being an open-source middleware company.

"Except for Mule ESB, all Mule products are free for development and pre-production, but not for production," Manes said. "Its tagline is no longer 'The open-source middleware company.' " Manes added that it also changed its named from MuleSource to MuleSoft.

MuleSoft had the option to build a scalable messaging server around Advanced Message Queuing Protocol (AMQP), an open messaging specification, but opted to use a proprietary solution, Manes noted.



Related Search Term(s): MuleSoft, open source

Pages 1 2 


Share this link: http://sdt.bz/34068
 
Most Read Latest News Blog Resources


Comments


01/21/2010 01:42:24 PM EST

ActiveMQ is supported by both FuseSource and SpringSource - both of which have hundreds of enterprise customers using it. FuseSource and SpringSource both have very successful open integration projects that compete with Mule.

United KingdomRob Davies


01/21/2010 05:55:24 PM EST

I am keen to understand how the performance claims made in the MuleMQ press release can be substantiated and verified independently. For example it is claimed that persistent messaging is several times faster than ActiveMQ. But, unless the code is open source how can anyone check that MuleMQ is writing messages to disk properly? It is very common for messaging vendors to claim 'persistence' when this is only partly true, and this can cause problems for customers. At RabbitMQ we try very hard to be clear and upfront about how we do persistence - it is important. Cheers alexis richardson RabbitMQ

United Kingdomalexis


01/22/2010 10:47:21 AM EST

The OEM is my-channels (http://www.my-channels.com/) and the product is called Nirvana. This product is quite old but did never play any role in the JMS market. Why? ;-) Ask yourself... Why should someone pay $4400/cpu plus support for that? I think, Nirvana was the cheapest Mule could get to have a complete ESB stack to prepare a "SpringSource" or a "Jboss".

GermanyAndreas Mueller


01/31/2010 05:50:18 PM EST

Andreas, we do indeed OEM Nirvana. It was chosen since is a mature and proven product with a large number of financial institutions relying on it to deliver real time data to a wide range of clients. We tested a lot of different JMS servers before selecting Nirvana, some didn't make make past the benchmark testing.

United StatesRoss Mason


Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Git changes how developers manage source code versions
At this year's Git Together, developers praise the platform's convenience and its ability to make source control easier. Changes for the future will focus on making it more Web 2.0-compatible by offering more on-demand repositories on GitHub Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb