What users are saying about

Apache Camel

24 Ratings

IBM MQ

19 Ratings

Apache Camel

24 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 7.4 out of 101

IBM MQ

19 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.2 out of 101

Add comparison

Likelihood to Recommend

Apache Camel

Message brokering across different systems, with transactionality and the ability to have fine tuned control over what happens using Java (or other languages), instead of a heavy, proprietary languages.One situation that it doesn't fit very well (as far as I have experienced) is when your workflow requires significant data mapping. While possible when using Java tooling, some other visual data mapping tools in other integration frameworks are easier to work with.
No photo available

IBM MQ

Advisable: Integration with other systems not alike, example of mainframe, establish SSL secured channels with providers/clients/etc.Not advisable: To perform intensive Data transformation (MQ Workflow was that tool though) , or to try to substitute SOAP/RMI for MQ
No photo available

Pros

  • Open source, which is vitally important
  • Great integration with Java frameworks such as Spring Boot, allowing it to be deployed however you need to deploy it
  • Wonderful testing tools as part of the framework
No photo available
  • Reliable: With properly written client code and queue managers set up correctly for the use-case, MQ will handle whatever you throw at it and just keep on going.
  • Mature: The product has been around for more than 20 years and has stood the test of time.
  • Easy of use: Administering MQ could be mastered with minimum effort.
Amanda Erlank profile photo

Cons

  • I find the "seda" endpoint to be less obvious that it is doing multi-threading than Spring Integration's executor mechanism.
  • Integration with Spring Beans is pretty good, but I believe SI's is a bit better (for obvious reasons, both being Spring products).
  • SI's use support is probably a bit better/faster and I believe the user base is larger so that there are most questions/answers for SI on StackOverflow
No photo available
  • Setting up security can be time-consuming and take some effort.
  • MQ Explorer on the client side could sometimes be a pain especially on Windows and during an upgrade.
  • IBM is not providing a good administration tool like MQMon included with the product.
Amanda Erlank profile photo

Alternatives Considered

We did a comparison of the two products with an example application that tested about 10 distinct EIP pattern. We wrote Camel in XML and Java DSL and SI in XML. This was about 3 years ago. At the time, I found the threading model in SI to be more intuitive and Camel's seda. However, Camel's documentation at the time was far and away more complete (Wiki pages for Camel vs looking through XML schema for SI). Since the SI has improved their documentation. The main factor that I believe still sets Camel apart is the Java DSL. Writing routes is complicated enough, but doing so in XML would be just painful.
No photo available
IBM MQ is the product for inter-business communication for security, flexibility and scalability.
Gregory Hanson profile photo

Return on Investment

  • Very fast time to market in that so many components are available to use immediately.
  • Error handling mechanisms and patterns of practice are robust and easy to use which in turn has made our application more robust from the start, so fewer bugs.
  • However, testing and debugging routes is more challenging than working is standard Java so that takes more time (less time than writing the components from scratch).
  • Most people don't know Camel coming in and many junior developers find it overwhelming and are not enthusiastic to learn it. So finding people that want to develop/maintain it is a challenge.
No photo available
  • Positive gains in data sharing. The time to market to set up new customers is relatively easy. Not touchless but easy.
  • Few maintenance costs. It just works.
  • Upgrades are painless so little money is spent on them, yielding positive ROIs.
Gregory Hanson profile photo

Pricing Details

Apache Camel

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details

IBM MQ

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details