Try our new research platform with insights from 80,000+ expert users

Elastic Search vs StreamSets comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

ROI

Sentiment score
6.2
Organizations report increased efficiency and ROI from Elastic Search, with proper implementation and data integration being crucial.
Sentiment score
8.1
StreamSets speeds up data processing, boosts efficiency and revenue, simplifies tasks, enhances security, and reduces costs significantly.
It is stable, and we do not encounter critical issues like server downtime, which could result in data loss.
We have not purchased any licensed products, and our use of Elastic Search is purely open-source, contributing positively to our ROI.
 

Customer Service

Sentiment score
6.6
Elastic Search's customer service is supported by a strong community and resources, though response times can be slow.
Sentiment score
6.7
StreamSets support is responsive and knowledgeable, offering effective solutions, though response times and technical handling could improve.
IBM technical support sometimes transfers tickets between different teams due to shift changes, which can be frustrating.
 

Scalability Issues

Sentiment score
7.2
Elastic Search offers strong scalability and ease of use but may face challenges with large databases and complex indexes.
Sentiment score
7.6
StreamSets is scalable and flexible, favored for cloud use but could improve auto-scaling for large data migrations.
I would rate its scalability a ten.
I would rate the scalability of Elasticsearch as an eight.
I can actually add more storage and memory because I host it in the cloud.
 

Stability Issues

Sentiment score
7.7
Elastic Search is stable and reliable for enterprise use, with occasional issues in large-scale data or new releases.
Sentiment score
7.8
StreamSets is praised for stability and reliability, despite minor memory issues, with high user ratings and market competitiveness.
It was consistent and reliable in our usage.
The data transfer sometimes exceeded the bandwidth limits without proper notification, which caused issues.
 

Room For Improvement

Elastic Search users seek improved security, scalability, integration, and support, alongside better UI, onboarding, and licensing enhancements.
StreamSets struggles with integration, real-time processing, clarity in UI, memory issues, security, documentation, and cloud storage performance.
This can create problems for new developers because they have to quickly switch to another version.
The consistency and stability of Elasticsearch are commendable, and they should keep up the good work.
It is primarily based on Unix or Linux-based operating systems and cannot be easily configured in Windows systems.
It would be beneficial if StreamSets addressed any potential memory leak issues to prevent unnecessary upgrades.
 

Setup Cost

Elastic Search is cost-effective initially but can become expensive with additional nodes and premium features despite flexible licensing.
StreamSets provides flexible pricing models, with varied user satisfaction, favoring larger enterprises over smaller companies due to cost.
We used the open-source version of Elasticsearch, which was free.
 

Valuable Features

ELK offers fast search, scalable architecture, advanced analytics, and integration with Logstash, X-Pack, for flexible, cost-effective enterprise data management.
StreamSets offers intuitive interface, extensive connectors, and features accessible to non-technical users for seamless data integration and manipulation.
The most valuable feature of Elasticsearch was the quick search capability, allowing us to search by any criteria needed.
Elastic Search makes handling large data volumes efficient and supports complex search operations.
Configuring Elasticsearch is much easier compared to comprehending other SIEM tools like Splunk.
It allows a hybrid installation approach, rather than being completely cloud-based or on-premises.
 

Categories and Ranking

Elastic Search
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
69
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (11th), Search as a Service (1st), Vector Databases (2nd)
StreamSets
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
Data Integration (16th)
 

Featured Reviews

Anand_Kumar - PeerSpot reviewer
Captures data from all other sources and becomes a MOM aka monitoring of monitors
Scalability and ROI are the areas they have to improve. Their license terms are based on the number of cores. If you increase the number of cores, it becomes very difficult to manage at a large scale. For example, if I have a $3 million project, I won't sell it because if we're dealing with a 10 TB or 50 TB system, there are a lot of systems and applications to monitor, and I have to make an MOM (Mean of Max) for everything. This is because of the cost impact. Also, when you have horizontal scaling, it's like a multi-story building with only one elevator. You have to run around, and it's not efficient. Even the smallest task becomes difficult. That's the problem with horizontal scaling. They need to improve this because if they increase the cores and adjust the licensing accordingly, it would make more sense.
Karthik Rajamani - PeerSpot reviewer
Integrates with different enterprise systems and enables us to easily build data pipelines without knowing how to code
There are a few things that can be better. We create pipelines or jobs in StreamSets Control Hub. It is a great feature, but if there is a way to have a folder structure or organize the pipelines and jobs in Control Hub, it would be great. I submitted a ticket for this some time back. There are certain features that are only available at certain stages. For example, HTTP Client has some great features when it is used as a processor, but those features are not available in HTTP Client as a destination. There could be some improvements on the group side. Currently, if I want to know which users are a part of certain groups, it is not straightforward to see. You have to go to each and every user and check the groups he or she is a part of. They could improve it in that direction. Currently, we have to put in a manual effort. In case something goes wrong, we have to go to each and every user account to check whether he or she is a part of a certain group or not.
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
850,236 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
17%
Financial Services Firm
15%
Government
9%
Manufacturing Company
8%
Financial Services Firm
13%
Computer Software Company
11%
Manufacturing Company
10%
Insurance Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about ELK Elasticsearch?
Logsign provides us with the capability to execute multiple queries according to our requirements. The indexing is very high, making it effective for storing and retrieving logs. The real-time anal...
What is your experience regarding pricing and costs for ELK Elasticsearch?
I don't know about pricing. That is dealt with by the sales team and our account team. I was not involved with that.
What needs improvement with ELK Elasticsearch?
I found an issue with Elasticsearch in terms of aggregation. They are good, yet the rules written for this are not really good. There is a maximum of 10,000 entries, so the limitation means that if...
What do you like most about StreamSets?
The best thing about StreamSets is its plugins, which are very useful and work well with almost every data source. It's also easy to use, especially if you're comfortable with SQL. You can customiz...
What needs improvement with StreamSets?
One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infr...
What is your primary use case for StreamSets?
We are using StreamSets for batch loading.
 

Comparisons

 

Also Known As

Elastic Enterprise Search, Swiftype, Elastic Cloud
No data available
 

Overview

 

Sample Customers

T-Mobile, Adobe, Booking.com, BMW, Telegraph Media Group, Cisco, Karbon, Deezer, NORBr, Labelbox, Fingerprint, Relativity, NHS Hospital, Met Office, Proximus, Go1, Mentat, Bluestone Analytics, Humanz, Hutch, Auchan, Sitecore, Linklaters, Socren, Infotrack, Pfizer, Engadget, Airbus, Grab, Vimeo, Ticketmaster, Asana, Twilio, Blizzard, Comcast, RWE and many others.
Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Find out what your peers are saying about Elastic Search vs. StreamSets and other solutions. Updated: April 2025.
850,236 professionals have used our research since 2012.