What users are saying about
24 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 7.5 out of 101
2 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 9 out of 101

Add comparison

Likelihood to Recommend

Apache Camel

In my experience, Apache Camel was very useful for the main use case that we leveraged it for, i.e. wiring up JMS messaging. I found the less-frequently-used handlers and endpoints to be either less reliable, maintainable, or easy to work with than just rolling my own data transfer logic. I would stick to straightforward use cases where the XML configuration conveys the intent in a very clear manner, and avoid using Apache Camel to do large portions of moving data around that involve business logic or custom intermediaries.
David McCann profile photo

InterSystems Ensemble

  • Best suited for fast development with a fundamental emphasis on object orientation
  • Prohibitive costs for very small integration projects
Nigel Timothy Bloom-Salm profile photo

Pros

  • Configuration of information routing via XML in a Sprint Context.
  • Robustness. Apache Camel is capable of handling many different information transfer protocols out-of-the-box.
  • Extensibility. Apache Camel also allows for custom routing handlers where needed.
David McCann profile photo
  • Fast Development.
  • Incredible performance especially in the realm of massive transactional based data systems.
  • Extensive and customizable adapter technologies for integration with just about any system/technology current IT development has need for in this day and age of developing single user interfaces to multiple data sources and/or applications.
  • One of the most secure database technologies available.
Nigel Timothy Bloom-Salm profile photo

Cons

  • Some of the documentation is a little sparse. In particular, its TCP-based routes use an underlying Netty server, and the interactions between Netty's decoder capabilities and Apache Camel's routing/handler capabilities can be a little muddy at times. In general it is clear which routes and endpoints are the more frequently used and which haven't been given as much attention.
David McCann profile photo
  • Given that Ensemble and Cache are one of if not the only true fully object orientated database/development technologies for massive transactional data systems its customizability is extensive and it just comes down to the creativity of the developer to get the products to pretty much do whatever they want to do with it. However, this is not necessarily obvious to newcomers to the technology.
  • The developer community could do with greater participation from the software developers/application specialists and engineers within InterSystems.
  • More extensive documentation and greater access to proven working solutions particularly in the realm of some of the lesser known or new and upcoming technologies.
Nigel Timothy Bloom-Salm profile photo

Usability

No score
No answers yet
No answers on this topic
InterSystems Ensemble9.0
Based on 1 answer
Nigel Timothy Bloom-Salm profile photo

Support

No score
No answers yet
No answers on this topic
InterSystems Ensemble9.0
Based on 1 answer
I have yet to raise an issue with InterSystems WRC that they have been unable to resolve to my satisfaction in the 20+ years that I have worked with their products.
Nigel Timothy Bloom-Salm profile photo

Alternatives Considered

We chose Apache Camel because it was lightweight, easy to get started with and because it had a groovy DSL since we were a grails shop when we started using it.
Akmal Muqeeth profile photo
There is just no comparison. Try it and see for yourself. Furthermore based on information from software houses I have interacted with over the years it far out paces products like WebSphere.
Nigel Timothy Bloom-Salm profile photo

Return on Investment

  • When we were looking to move to a service oriented architecture, Apache Camel got us started quickly. It continues to be the backbone of our integration.
Akmal Muqeeth profile photo
  • I was able to develop a fully functional integration engine linking pharmacy systems with pharmacy robotics in less than three months in comparison with the year that the previous software development company had taken to develop a solution that was incomplete and did not work using Microsoft technology.
  • The engine I developed was so stable and adaptable that it quickly replaced the equivalent engine supplied by the robot manufacturers own software development team.
  • It has proven to be so effective that it is now the product of choice for future developments within the organization replacing Microsoft technologies which were the previous company standard.
Nigel Timothy Bloom-Salm profile photo

Screenshots

Apache Camel
InterSystems Ensemble

Pricing Details

Apache Camel

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

InterSystems Ensemble

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