TrustRadius: an HG Insights company

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

    Elasticsearch

    Score8.6 out of 10
    N/AElasticsearch is an enterprise search tool from Elastic in Mountain View, California.

    $16

    per month

    Pricing
    Apache KafkaElasticsearch
    Editions & Modules
    No answers on this topic
    Standard
    $16.00
    per month
    Gold
    $19.00
    per month
    Platinum
    $22.00
    per month
    Enterprise
    Contact Sales
    Offerings
    Pricing Offerings
    Apache KafkaElasticsearch
    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 KafkaElasticsearch
    Considered Both Products
    Apache
    No answer on this topic
    Elastic
    Chose Elasticsearch
    Elasticsearch is relatedly cheaper the splunk. OpenSearch is good and we migrated some data into it but the critical data stays in elasticsearch as it has formal support.
    Incentivized
    Chose Elasticsearch
    They all have their specific pros and cons. Elastic was actually initially brought in to provide less expensive functionality to Splunk, and Splunk use cases. Grafana was brought in to provide less expensive visualizations compared to Splunk and Elastic...I would recommend …
    Incentivized
    Chose Elasticsearch
    Elasticsearch is widely popular and it's mostly free. Its ecosystem, ability to scale, ease to set up, integration with other systems, highly usable API make it really great compared to its competition.
    Incentivized
    Key User Insights
    Would buy again
    94%
    Would buy again
    16 Answers
    82%
    Would buy again
    14 Answers
    Delivers good value for the price
    94%
    Delivers good value for the price
    16 Answers
    100%
    Delivers good value for the price
    16 Answers
    Happy with the feature set
    94%
    Happy with the feature set
    16 Answers
    100%
    Happy with the feature set
    17 Answers
    Lived up to sales and marketing promises
    100%
    Lived up to sales and marketing promises
    13 Answers
    100%
    Lived up to sales and marketing promises
    13 Answers
    Implementation went as expected
    100%
    Implementation went as expected
    17 Answers
    87%
    Implementation went as expected
    13 Answers
    Best Alternatives
    Apache KafkaElasticsearch
    Small Businesses
    No answers on this topic
    Apache Solr
    Score9 out of 10
    Medium-sized Companies
    IBM MQ
    Score9.6 out of 10
    Algolia
    Score8.7 out of 10
    Enterprises
    TIBCO Messaging
    Score7.7 out of 10
    Algolia
    Score8.7 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    Apache KafkaElasticsearch
    Likelihood to Recommend
    8.0
    (19 ratings)
    9.0
    (48 ratings)
    Likelihood to Renew
    9.0
    (2 ratings)
    10.0
    (1 ratings)
    Usability
    8.0
    (2 ratings)
    10.0
    (1 ratings)
    Support Rating
    8.4
    (4 ratings)
    7.8
    (9 ratings)
    Implementation Rating
    -
    (0 ratings)
    9.0
    (1 ratings)
    User Testimonials
    Apache KafkaElasticsearch
    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
    Elastic
    Elasticsearch is a really scalable solution that can fit a lot of needs, but the bigger and/or those needs become, the more understanding & infrastructure you will need for your instance to be running correctly. Elasticsearch is not problem-free - you can get yourself in a lot of trouble if you are not following good practices and/or if are not managing the cluster correctly. Licensing is a big decision point here as Elasticsearch is a middleware component - be sure to read the licensing agreement of the version you want to try before you commit to it. Same goes for long-term support - be sure to keep yourself in the know for this aspect you may end up stuck with an unpatched version for years.
    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
    Elastic
    • As I mentioned before, Elasticsearch's flexible data model is unparalleled. You can nest fields as deeply as you want, have as many fields as you want, but whatever you want in those fields (as long as it stays the same type), and all of it will be searchable and you don't need to even declare a schema beforehand!
    • Elastic, the company behind Elasticsearch, is super strong financially and they have a great team of devs and product managers working on Elasticsearch. When I first started using ES 3 years ago, I was 90% impressed and knew it would be a good fit. 3 years later, I am 200% impressed and blown away by how far it has come and gotten even better. If there are features that are missing or you don't think it's fast enough right now, I bet it'll be suitable next year because the team behind it is so dang fast!
    • Elasticsearch is really, really stable. It takes a lot to bring down a cluster. It's self-balancing algorithms, leader-election system, self-healing properties are state of the art. We've never seen network failures or hard-drive corruption or CPU bugs bring down an ES cluster.
    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
    Elastic
    • Joining data requires duplicate de-normalized documents that make parent child relationships. It is hard and requires a lot of synchronizations
    • Tracking errors in the data in the logs can be hard, and sometimes recurring errors blow up the error logs
    • Schema changes require complete reindexing of an index
    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
    Elastic
    We're pretty heavily invested in ElasticSearch at this point, and there aren't any obvious negatives that would make us reconsider this decision.
    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
    Elastic
    To get started with Elasticsearch, you don't have to get very involved in configuring what really is an incredibly complex system under the hood. You simply install the package, run the service, and you're immediately able to begin using it. You don't need to learn any sort of query language to add data to Elasticsearch or perform some basic searching. If you're used to any sort of RESTful API, getting started with Elasticsearch is a breeze. If you've never interacted with a RESTful API directly, the journey may be a little more bumpy. Overall, though, it's incredibly simple to use for what it's doing under the covers.
    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
    Elastic
    We've only used it as an opensource tooling. We did not purchase any additional support to roll out the elasticsearch software. When rolling out the application on our platform we've used the documentation which was available online. During our test phases we did not experience any bugs or issues so we did not rely on support at all.
    Incentivized
    Read full review
    Implementation Rating
    Apache
    No answers on this topic
    Elastic
    Do not mix data and master roles. Dedicate at least 3 nodes just for Master
    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
    Elastic
    As far as we are concerned, Elasticsearch is the gold standard and we have barely evaluated any alternatives. You could consider it an alternative to a relational or NoSQL database, so in cases where those suffice, you don't need Elasticsearch. But if you want powerful text-based search capabilities across large data sets, Elasticsearch is the way to go.
    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
    Elastic
    • We have had great luck with implementing Elasticsearch for our search and analytics use cases.
    • While the operational burden is not minimal, operating a cluster of servers, using a custom query language, writing Elasticsearch-specific bulk insert code, the performance and the relative operational ease of Elasticsearch are unparalleled.
    • We've easily saved hundreds of thousands of dollars implementing Elasticsearch vs. RDBMS vs. other no-SQL solutions for our specific set of problems.
    Incentivized
    Read full review
    ScreenShots