TrustRadius: an HG Insights company

Apache Kafka vs. Red Hat JBoss Enterprise Application Platform

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Apache Kafka

    Score7.7 out of 10
    N/AApache Kafka is an open-source stream processing platform developed by the Apache Software Foundation written in Scala and Java. The Kafka event streaming platform is used by thousands of companies for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications.N/A

    Red Hat JBoss EAP

    Score7.3 out of 10
    N/AN/AN/A
    Pricing
    Apache KafkaRed Hat JBoss EAP
    Editions & Modules
    No answers on this topic
    No answers on this topic
    Offerings
    Pricing Offerings
    Apache KafkaRed 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 KafkaRed Hat JBoss EAP
    Considered Both Products
    Apache
    No answer on this topic
    Red Hat
    Chose Red Hat JBoss EAP
    We decided to use Red Hat JBoss EAP as it lowers our overall cost, supports all the features that we are looking for including clustering, distributed caching and web services.
    JBoss EAP is modular and has cloud-ready architecture.
    Incentivized
    Key User Insights
    Would buy again
    94%
    Would buy again
    16 Answers
    No answers on this topic
    Delivers good value for the price
    94%
    Delivers good value for the price
    16 Answers
    No answers on this topic
    Happy with the feature set
    94%
    Happy with the feature set
    16 Answers
    No answers on this topic
    Lived up to sales and marketing promises
    100%
    Lived up to sales and marketing promises
    13 Answers
    No answers on this topic
    Implementation went as expected
    100%
    Implementation went as expected
    17 Answers
    No answers on this topic
    Features
    Apache KafkaRed Hat JBoss EAP
    Application Servers
    Comparison of Application Servers features of Apache Kafka and Red Hat JBoss Enterprise Application Platform
    Feature
    Apache Kafka
    -
    Ratings
    Red Hat JBoss Enterprise Application Platform
    8.6
    8 Ratings
    8% 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 KafkaRed Hat JBoss EAP
    Small Businesses
    No answers on this topic
    NGINX
    Score9.2 out of 10
    Medium-sized Companies
    IBM MQ
    Score9.6 out of 10
    Oracle WebLogic Server
    Score7.5 out of 10
    Enterprises
    TIBCO Messaging
    Score7.7 out of 10
    NGINX
    Score9.2 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    Apache KafkaRed Hat JBoss EAP
    Likelihood to Recommend
    8.0
    (19 ratings)
    8.1
    (8 ratings)
    Likelihood to Renew
    9.0
    (2 ratings)
    5.0
    (1 ratings)
    Usability
    8.0
    (2 ratings)
    8.5
    (3 ratings)
    Performance
    -
    (0 ratings)
    8.7
    (3 ratings)
    Support Rating
    8.4
    (4 ratings)
    5.2
    (2 ratings)
    Ease of integration
    -
    (0 ratings)
    8.5
    (3 ratings)
    User Testimonials
    Apache KafkaRed Hat JBoss EAP
    Likelihood to Recommend
    Apache
    Apache Kafka is well-suited for most data-streaming use cases. Amazon Kinesis and Azure EventHubs, unless you have a specific use case where using those cloud PaAS for your data lakes, once set up well, Apache Kafka will take care of everything else in the background. Azure EventHubs, is good for cross-cloud use cases, and Amazon Kinesis - I have no real-world experience. But I believe it is the same.
    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.
    Incentivized
    Read full review
    Pros
    Apache
    • Really easy to configure. I've used other message brokers such as RabbitMQ and compared to them, Kafka's configurations are very easy to understand and tweak.
    • Very scalable: easily configured to run on multiple nodes allowing for ease of parallelism (assuming your queues/topics don't have to be consumed in the exact same order the messages were delivered)
    • Not exactly a feature, but I trust Kafka will be around for at least another decade because active development has continued to be strong and there's a lot of financial backing from Confluent and LinkedIn, and probably many other companies who are using it (which, anecdotally, is many).
    Incentivized
    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.
    Incentivized
    Read full review
    Cons
    Apache
    • Sometimes it becomes difficult to monitor our Kafka deployments. We've been able to overcome it largely using AWS MSK, a managed service for Apache Kafka, but a separate monitoring dashboard would have been great.
    • Simplify the process for local deployment of Kafka and provide a user interface to get visibility into the different topics and the messages being processed.
    • Learning curve around creation of broker and topics could be simplified
    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.
    Incentivized
    Read full review
    Likelihood to Renew
    Apache
    Kafka is quickly becoming core product of the organization, indeed it is replacing older messaging systems. No better alternatives found yet
    Incentivized
    Read full review
    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
    Incentivized
    Read full review
    Usability
    Apache
    Apache Kafka is highly recommended to develop loosely coupled, real-time processing applications. Also, Apache Kafka provides property based configuration. Producer, Consumer and broker contain their own separate property file
    Incentivized
    Read full review
    Red Hat
    JBoss overall is easy to use. The installation and deployment of applications are quick. Documentations and support are also readily available.
    Incentivized
    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.
    Incentivized
    Read full review
    Support Rating
    Apache
    Support for Apache Kafka (if willing to pay) is available from Confluent that includes the same time that created Kafka at Linkedin so they know this software in and out. Moreover, Apache Kafka is well known and best practices documents and deployment scenarios are easily available for download. For example, from eBay, Linkedin, Uber, and NYTimes.
    Incentivized
    Read full review
    Red Hat
    Fast response.
    Incentivized
    Read full review
    Alternatives Considered
    Apache
    I used other messaging/queue solutions that are a lot more basic than Confluent Kafka, as well as another solution that is no longer in the market called Xively, which was bought and "buried" by Google. In comparison, these solutions offer way fewer functionalities and respond to other needs.
    Incentivized
    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.
    Incentivized
    Read full review
    Return on Investment
    Apache
    • Positive: Get a quick and reliable pub/sub model implemented - data across components flows easily.
    • Positive: it's scalable so we can develop small and scale for real-world scenarios
    • Negative: it's easy to get into a confusing situation if you are not experienced yet or something strange has happened (rare, but it does). Troubleshooting such situations can take time and effort.
    Incentivized
    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.
    Incentivized
    Read full review
    ScreenShots