TrustRadius: an HG Insights company

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Apache Camel

    Score7.5 out of 10
    N/AApache Camel is an open source integration platform.N/A
    Pricing
    Apache Camel
    Editions & Modules
    No answers on this topic
    Offerings
    Pricing Offerings
    Apache Camel
    Free Trial
    No
    Free/Freemium Version
    No
    Premium Consulting/Integration Services
    No
    Entry-level Setup FeeNo setup fee
    Additional Details
    More Pricing Information
    Community Pulse
    Apache Camel
    Considered Both Products
    Apache
    Chose Apache Camel
    Easier to use, better routing system, but perhaps too basic dependant on business needs?
    Incentivized
    Chose Apache Camel
    If you are looking for a Java-based open source low cost equivalent to webMethods or Azure Logic Apps, Apache Camel is an excellent choice as it is mature and widely deployed, and included in many vendored Java application servers too such as Redhat JBoss EAP. Apache Camel is …
    Incentivized
    Chose Apache Camel
    working with Apache's TomCat server, our developer found it most easy given the UI of Camel to perform integration and data processing tasks. when compared to the other two softwares they felt the need to learn new tools outside of Apache family can be avoided and with kafka, …
    Incentivized
    Chose Apache Camel
    WebSphere Message Broker - Expensive, old, hard to use, bad connectors
    Mulesoft - Very similar to Camel, but expensive and buggy
    Incentivized
    Chose Apache Camel
    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. …
    Incentivized
    Chose Apache Camel
    Akka or Spring Integration/ XD are alternatives to Apache Camel and very good frameworks on their own (especially Akka which provides a single threaded illusion).
    Incentivized
    Chose Apache Camel
    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.
    Incentivized
    Chose Apache Camel
    Apache Camel has been the integration framework of choice, but I was not the person to make the decision to use it. Compared to other competing products like Tibco Business Works, etc., it is free and open source and its licensing policy is acceptable to the management of Cox.
    Incentivized
    Chose Apache Camel
    Esper is only similar in that they both are involved in complex even processing, however Esper's aim is a little more complex and specialized. In general however I found Apache Camel to be much easier to understand, implement and debug, whereas Esper's DSL can get very …
    Incentivized
    Key User Insights
    Would buy again
    No answers on this topic
    Delivers good value for the price
    No answers on this topic
    Happy with the feature set
    No answers on this topic
    Lived up to sales and marketing promises
    No answers on this topic
    Implementation went as expected
    No answers on this topic
    Best Alternatives
    Apache Camel
    Small Businesses
    No answers on this topic
    Medium-sized Companies
    No answers on this topic
    Enterprises
    TIBCO B2B Integration Solution
    Score8 out of 10
    All AlternativesView all alternatives
    User Ratings
    Apache Camel
    Likelihood to Recommend
    7.9
    (11 ratings)
    User Testimonials
    Apache Camel
    Likelihood to Recommend
    Apache
    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.
    Incentivized
    Read full review
    Pros
    Apache
    • Camel has an easy learning curve. It is fairly well documented and there are about 5-6 books on Camel.
    • There is a large user group and blogs devoted to all things Camel and the developers of Camel provide quick answers and have also been very quick to patch Camel, when bugs are reported.
    • Camel integrates well with well known frameworks like Spring, and other middleware products like Apache Karaf and Servicemix.
    • There are over 150 components for the Camel framework that help integrate with diverse software platforms.
    • Camel is also good for creating microservices.
    Incentivized
    Read full review
    Cons
    Apache
    • didn't work well when our developers tried to transform heavy data sets
    • Apache Camel's whole logic is based on java so team needs to have a great skill set in java
    • if there are a handful of workflows then Apache Camel's full potential can't be realized
    Incentivized
    Read full review
    Alternatives Considered
    Apache
    If you are looking for a Java-based open source low cost equivalent to webMethods or Azure Logic Apps, Apache Camel is an excellent choice as it is mature and widely deployed, and included in many vendored Java application servers too such as Redhat JBoss EAP. Apache Camel is lacking on the GUI tooling side compared to commercial products such as webMethods or Azure Logic Apps.
    Incentivized
    Read full review
    Return on Investment
    Apache
    • 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.
    Incentivized
    Read full review
    ScreenShots