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

Elastic Search vs WhereScape RED 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.0
Organizations report increased efficiency and ROI from Elastic Search, with proper implementation and data integration being crucial.
Sentiment score
7.0
WhereScape RED offers varied returns, with some users experiencing quick ROI, efficient development, and substantial gains.
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
8.3
Customer service is often excellent and prompt, although some feel support wanes post-purchase and seems money-driven.
 

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
6.6
WhereScape RED efficiently scales with large data, improves ETL processing, and enhances speeds using ELT and SQL features.
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
6.6
WhereScape RED's stability varies; it's praised for maturity and speed, yet some report resource and debugging challenges.
 

Room For Improvement

Elastic Search users seek improved security, scalability, integration, and support, alongside better UI, onboarding, and licensing enhancements.
WhereScape RED suffers from scalability issues, lacking performance efficiency, enhanced documentation, better GUI, and improved support for multi-database environments.
This can create problems for new developers because they have to quickly switch to another version.
 

Setup Cost

Elastic Search is cost-effective initially but can become expensive with additional nodes and premium features despite flexible licensing.
WhereScape RED's flexible developer-based licensing and native SQL code provide cost-effective, vendor-independent data warehousing solutions with quick ROI potential.
 

Valuable Features

ELK offers fast search, scalable architecture, advanced analytics, and integration with Logstash, X-Pack, for flexible, cost-effective enterprise data management.
WhereScape RED streamlines data warehousing with automation, agile support, user-friendly interface, and compatibility with leading methodologies.
Elastic Search makes handling large data volumes efficient and supports complex search operations.
Aggregation is faster than querying directly from a database, like Postgres or Vertica.
 

Categories and Ranking

Elastic Search
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
67
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (9th), Search as a Service (1st), Vector Databases (2nd)
WhereScape RED
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
15
Ranking in other categories
Data Integration (48th)
 

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.
it_user584544 - PeerSpot reviewer
The ​architecture is based on metadata and documentation is automated.
I would love to see a GUI interface for defining dependencies between build processes. RED provides a spreadsheet like interface for defining the dependencies between builds. Once the dependencies are defined, RED can produce a nice dependency diagram to give a visualization of the dependency tree. It would be easier to define complex dependency relationships if the dependency diagram were interactive. Our legacy ETL tool provided this GUI dependency definition via a drag and drop diagram which was very useful. The solution provided by WhereScape does work, and the dependency diagrams generated are helpful. It would just be nice to have the ability to define dependencies via a diagram, since dependencies relationships are much easier to understand via a diagram.
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
850,028 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
17%
Computer Software Company
10%
Insurance Company
8%
Healthcare Company
8%
 

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...
Ask a question
Earn 20 points
 

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.
British American Tobacco, Cornell University, Allianz Benelux, Finnair, Solarwinds and many more.
Find out what your peers are saying about Elastic Search vs. WhereScape RED and other solutions. Updated: April 2025.
850,028 professionals have used our research since 2012.