TrustRadius: an HG Insights company

Apache Camel vs. WSO2 Integration Platform

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Apache Camel

    Score7.4 out of 10
    N/AApache Camel is an open source integration platform.N/A

    WSO2 Integration Platform

    Score10 out of 10
    N/AWSO2 Integration Platform (WSO2 Integrator) is an AI-native integration engine that connects disparate systems, automates complex workflows, and supports real-time event streaming. The platform provides a centralized environment to orchestrate APIs, file-based transfers, and autonomous AI agents across the enterprise.N/A
    Pricing
    Apache CamelWSO2 Integration Platform
    Editions & Modules
    No answers on this topic
    No answers on this topic
    Offerings
    Pricing Offerings
    Apache CamelWSO2 Integration Platform
    Free Trial
    NoNo
    Free/Freemium Version
    NoNo
    Premium Consulting/Integration Services
    NoNo
    Entry-level Setup FeeNo setup feeNo setup fee
    Additional Details——
    More Pricing Information
    Best Alternatives
    Apache CamelWSO2 Integration Platform
    Small Businesses
    No answers on this topic
    Make
    Score9.3 out of 10
    Medium-sized Companies
    No answers on this topic
    IBM App Connect
    Score9 out of 10
    Enterprises
    TIBCO B2B Integration Solution
    Score8 out of 10
    Workato
    Score9.3 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    Apache CamelWSO2 Integration Platform
    Likelihood to Recommend
    7.9
    (11 ratings)
    10.0
    (1 ratings)
    User Testimonials
    Apache CamelWSO2 Integration Platform
    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
    WSO2
    The best-suited scenario is the service chain pattern or all patterns used in online mode. The less appropriate scenario is a batch service the duration time of the service is more than 10minutes because it is necessary to increase the HTTP timeout.
    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
    WSO2
    • Service chain pattern
    • Message transformation
    • Call more than one backend service
    • Call service with different protocoll as the client use
    • Use file as input
    • Use mail as input
    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
    WSO2
    • View deploy artifact in date time order
    • Easy way to map data
    • Easy way to manage payload
    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
    WSO2
    We can start with the community version and then when we moved into production we can buy the supported version. The supported and community version have the same code so we can do every test before deciding to buy the supported version.
    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
    WSO2
    • Reduce development time to the service integration
    • We can use junior developer
    • Clustered in easy way
    Read full review
    ScreenShots