Apache Camel vs. Red Hat JBoss Enterprise Application Platform

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apache Camel
Score 6.8 out of 10
N/A
Apache Camel is an open source integration platform.N/A
Red Hat JBoss EAP
Score 7.6 out of 10
N/A
N/AN/A
Pricing
Apache CamelRed Hat JBoss Enterprise Application Platform
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache CamelRed Hat JBoss EAP
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
Community Pulse
Apache CamelRed Hat JBoss Enterprise Application Platform
Top Pros
Top Cons
Features
Apache CamelRed Hat JBoss Enterprise Application Platform
Application Servers
Comparison of Application Servers features of Product A and Product B
Apache Camel
-
Ratings
Red Hat JBoss Enterprise Application Platform
8.6
8 Ratings
6% above category average
IDE support00 Ratings8.18 Ratings
Security management00 Ratings8.68 Ratings
Administration and management00 Ratings8.18 Ratings
Application server performance00 Ratings8.68 Ratings
Installation00 Ratings9.58 Ratings
Open-source standards compliance00 Ratings8.68 Ratings
Best Alternatives
Apache CamelRed Hat JBoss Enterprise Application Platform
Small Businesses

No answers on this topic

NGINX
NGINX
Score 9.0 out of 10
Medium-sized Companies
Anypoint Platform
Anypoint Platform
Score 8.3 out of 10
NGINX
NGINX
Score 9.0 out of 10
Enterprises
TIBCO B2B Integration Solution
TIBCO B2B Integration Solution
Score 8.2 out of 10
NGINX
NGINX
Score 9.0 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache CamelRed Hat JBoss Enterprise Application Platform
Likelihood to Recommend
7.7
(11 ratings)
8.1
(8 ratings)
Likelihood to Renew
-
(0 ratings)
5.0
(1 ratings)
Usability
-
(0 ratings)
8.5
(3 ratings)
Performance
-
(0 ratings)
8.7
(6 ratings)
Support Rating
-
(0 ratings)
5.2
(4 ratings)
Ease of integration
-
(0 ratings)
8.5
(3 ratings)
User Testimonials
Apache CamelRed Hat JBoss Enterprise Application 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.
Read full review
Red Hat
JBoss EAP is subscription based/open source platform. It's very reliable and great for deploying high transaction Java based enterprise applications. It integrates well with third party components like mod_cluster and supports popular Java EE web-based frameworks such as Spring, Angular JS, jQuery Mobile, and Google Web Toolkit.
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.
Read full review
Red Hat
  • MOD_CLUSTER integration. JBoss EAP integrates pretty well with mod_cluster. This is an intelligent load balancer especially useful in highly clustered environments.
  • Supports enterprise-grade features such as high availability clustering, distributed caching, messaging etc.
  • Supports deployment in on-premise, virtual and hybrid cloud environments.
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
Read full review
Red Hat
  • Jboss CLI is a great tool but we had trouble using it to get values that are displayed on Jboss GUI. It also has limitations parsing the applications.xml files and we had to use a mix of jboss-cli and linux bash commands to automate certain application administrative tasks.
  • JBoss doesn't really provides performance tuning recommendations. It would have been nice if it could learn from the current demand vs current settings for things like connection pool, server configurations, garbage collection etc.
Read full review
Likelihood to Renew
Apache
No answers on this topic
Red Hat
We are planning to migrate away from Jboss to Tomcat as Jboss has shown not interest in supporting OSGi which is heavily used at our shop
Read full review
Usability
Apache
No answers on this topic
Red Hat
JBoss overall is easy to use. The installation and deployment of applications are quick. Documentations and support are also readily available.
Read full review
Performance
Apache
No answers on this topic
Red Hat
Usually, Red Hat JBoss Enterprise Application Platform is good at performance and well suited for high traffic Java EE-based applications, but we have faced hard times performance tuning it for our specific needs. The product would be nicer if they would add a performance diagnostic and recommendations feature to it.
Read full review
Support Rating
Apache
No answers on this topic
Red Hat
Fast response.
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.
Read full review
Red Hat
We selected JBoss because of compatibility with EJB's. We currently are trying to reduce our footprint and will highly consider using Tomcat.
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.
Read full review
Red Hat
  • Improved delivery timelines due to easy out of the box setup.
  • It is a cheap subscription-based/open-source Java EE-based application server. This reduces the overall cost of delivery.
Read full review
ScreenShots