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

Elastic Search vs Red Hat OpenShift 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.4
Elastic Search offers high ROI, efficiency, and cost-effectiveness, with significant time-saving and security benefits despite some licensing costs.
Sentiment score
7.8
Red Hat OpenShift improves productivity, offers cost savings, enhances system stability, and provides 15% ROI, especially in privacy-focused sectors.
We have not purchased any licensed products, and our use of Elastic Search is purely open-source, contributing positively to our ROI.
It is stable, and we do not encounter critical issues like server downtime, which could result in data loss.
The main benefits observed from using Elastic Search include improvements in operational efficiency, along with cost, time, and resource savings.
With OpenShift combined with IBM Cloud App integration, I can spin an integration server in a second as compared to traditional methods, which could take days or weeks.
Moving to OpenShift resulted in increased system stability and reduced downtime, which contributed to operational efficiency.
It is always advisable to get the bare minimum that you need, and then add more when necessary.
 

Customer Service

Sentiment score
6.5
Elastic Search's customer service is praised for responsiveness and knowledge, but complex issue support may require improvement.
Sentiment score
6.8
Red Hat OpenShift support is mixed, praised for expertise but criticized for slow responses and varying experiences based on subscription.
I would rate technical support from Elastic Search as three out of ten.
Red Hat's technical support is responsive and effective.
I have been pretty happy in the past with getting support from Red Hat.
Red Hat's technical support is good, and I would rate it a nine out of ten.
 

Scalability Issues

Sentiment score
7.3
Elastic Search is scalable and integrates well, but challenges exist with large datasets and disaster recovery under rapid scaling.
Sentiment score
7.5
Red Hat OpenShift offers efficient scalability with automated features, easy deployment, and adaptability, despite cost and infrastructure considerations.
I would rate its scalability a ten.
I can actually add more storage and memory because I host it in the cloud.
I would rate the scalability of Elasticsearch as an eight.
The on-demand provisioning of pods and auto-scaling, whether horizontal or vertical, is the best part.
OpenShift's horizontal pod scaling is more effective and efficient than that used in Kubernetes, making it a superior choice for scalability.
Red Hat OpenShift scales excellently, with a rating of ten out of ten.
 

Stability Issues

Sentiment score
7.7
Elastic Search is stable and reliable, though version updates and data management can affect performance under stress.
Sentiment score
7.7
Red Hat OpenShift is praised for stability, reliability, and features like Blue-Green deployment, with minor issues quickly resolved.
The data transfer sometimes exceeded the bandwidth limits without proper notification, which caused issues.
The stability of Elasticsearch was very high.
It provides better performance yet requires more resources compared to vanilla Kubernetes.
I've had my cluster running for over four years.
It performs well under load, providing the desired output.
 

Room For Improvement

Elastic Search needs improvements in security, scalability, usability, stability, integration, support, and enhanced features for a better user experience.
Red Hat OpenShift needs better documentation, improved usability, and enhancements in security, integration, technical support, and installation processes.
This can create problems for new developers because they have to quickly switch to another version.
It is primarily based on Unix or Linux-based operating systems and cannot be easily configured in Windows systems.
The consistency and stability of Elasticsearch are commendable, and they should keep up the good work.
Learning OpenShift requires complex infrastructure, needing vCenter integration, more advanced answers, active directory, and more expensive hardware.
Red Hat OpenShift's biggest disadvantage is they do not provide any private cloud setup where we can host on our site using their services.
We should aim to include VMware-like capabilities to be competitive, especially considering cost factors.
 

Setup Cost

Elastic Search's free open-source version can incur back-end costs for advanced features, expertise, and premium support.
Red Hat OpenShift pricing is high but potentially cost-effective for large enterprises, offering comprehensive support and enterprise capabilities.
We used the open-source version of Elasticsearch, which was free.
Initially, licensing was per CPU, with a memory cap, but the price has doubled, making it difficult to justify for clients with smaller compute needs.
Red Hat can improve on the pricing part by making it more flexible and possibly on the lower side.
The cost of OpenShift is very high, particularly with the OpenShift Plus package, which includes many products and services.
 

Valuable Features

Elastic Search is valued for scalability, fast indexing, powerful analysis, security features, cloud readiness, and strong community support.
Red Hat OpenShift is valued for its security, scalability, automation, multi-cloud flexibility, and efficient management interface.
Elastic Search makes handling large data volumes efficient and supports complex search operations.
The most valuable feature of Elasticsearch was the quick search capability, allowing us to search by any criteria needed.
Aggregation is faster than querying directly from a database, like Postgres or Vertica.
Because it was centrally managed in our company, many metrics that we had to write code for were available out of the box, including utilization, CPU utilization, memory, and similar metrics.
The concept of containers and scaling on demand is a feature I appreciate the most about Red Hat OpenShift.
A valuable feature of Red Hat OpenShift is its ability to handle increased loads by automatically adding nodes.
 

Categories and Ranking

Elastic Search
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
71
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (9th), Search as a Service (1st), Vector Databases (3rd)
Red Hat OpenShift
Average Rating
8.4
Reviews Sentiment
7.1
Number of Reviews
62
Ranking in other categories
PaaS Clouds (3rd), Server Virtualization Software (9th), Container Management (12th), Hybrid Cloud Computing Platforms (6th), Agile and DevOps Services (1st)
 

Mindshare comparison

Elastic Search and Red Hat OpenShift aren’t in the same category and serve different purposes. Elastic Search is designed for Indexing and Search and holds a mindshare of 23.7%, down 27.2% compared to last year.
Red Hat OpenShift, on the other hand, focuses on Hybrid Cloud Computing Platforms, holds 3.1% mindshare.
Indexing and Search
Hybrid Cloud Computing Platforms
 

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.
Pratul Shukla - PeerSpot reviewer
Adopting a flexible and efficient approach with noticeable improvements in operational costs and continued challenges in job management
Currently, one of the biggest challenges we face is with services and jobs. For spawning batches, although it has crons, it is not easy to integrate with enterprise systems such as Autosys. The entire company uses Autosys, but we are not able to integrate it effectively. We need intermediate servers to run OC utility commands and initiate the cron job. We have to do a lot of modifications to ensure our batches work properly. With physical or virtual servers, even in AWS, we are able to write and manage multiple jobs. Managing batches in Red Hat OpenShift has been a significant challenge. Integrating third parties is a challenge with Red Hat OpenShift. For example, with Elasticsearch, onboarding itself was difficult, running file beats and dealing with routing issues. It is not straightforward, especially since we have some components in AWS as. AWS has many capabilities that come out of the box and are easier to work with compared to Red Hat OpenShift. Red Hat OpenShift's biggest disadvantage is they do not provide any private cloud setup where we can host on our site using their services. The main reason we went with Red Hat OpenShift was because it is a private cloud, and we have regulatory requirements that prevent us from using public cloud.
report
Use our free recommendation engine to learn which Indexing and Search solutions are best for your needs.
856,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
16%
Financial Services Firm
15%
Government
9%
Manufacturing Company
8%
Financial Services Firm
30%
Manufacturing Company
9%
Computer Software Company
9%
Insurance Company
7%
 

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?
We used the open-source version of Elasticsearch, which was free.
What needs improvement with ELK Elasticsearch?
It would be useful if a feature for renaming indices could be added without affecting the performance of other features. However, overall, the consistency and stability of Elasticsearch are already...
How does OpenShift compare with Amazon AWS?
Open Shift makes managing infrastructure easy because of self-healing and automatic scaling. There is also a wonderful dashboard mechanism to alert us in case the application is over-committing or ...
Which would you recommend - Pivotal Cloud Foundry or OpenShift?
Pivotal Cloud Foundry is a cloud-native application platform to simplify app delivery. It is efficient and effective. The best feature is how easy it is to handle external services such as database...
What do you like most about OpenShift?
OpenShift facilitates DevOps practices and improves CI/CD workflows in terms of stability compared to Jenkins.
 

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.
UPS, Cathay Pacific, Hilton
Find out what your peers are saying about Elastic, Luigi's Box, OpenText and others in Indexing and Search. Updated: May 2025.
856,873 professionals have used our research since 2012.