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

Elastic Search vs Oracle Endeca [EOL] 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:
 

Categories and Ranking

Elastic Search
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
90
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Search as a Service (1st), Vector Databases (2nd)
Oracle Endeca [EOL]
Average Rating
6.0
Number of Reviews
1
Ranking in other categories
No ranking in other categories
 

Featured Reviews

Anurag Pal - PeerSpot reviewer
Technical Lead at a consultancy with 10,001+ employees
Search and aggregations have transformed how I manage and visualize complex real estate data
Elastic Search consumes lots of memory. You have to provide the heap size a lot if you want the best out of it. The major problem is when a company wants to use Elastic Search but it is at a startup stage. At a startup stage, there is a lot of funds to consider. However, their use case is that they have to use a pretty significant amount of data. For that, it is very expensive. For example, if you take OLTP-based databases in the current scenario, such as ClickHouse or Iceberg, you can do it on 4GB RAM also. Elastic Search is for analytical records. You have to do the analytics on it. According to me, as far as I have seen, people will start moving from Elastic Search sooner or later. Why? Because it is expensive. Another thing is that there is an open source available for that, such as ClickHouse. Around 2014 and 2012, there was only one competitor at that time, which was Solr. But now, not only is Solr there, but you can take ClickHouse and you have Iceberg also. How are we going to compete with them? There is also a fork of Elastic Search that is OpenSearch. As far as I have seen in lots of articles I am reading, users are using it as the ELK stack for logs and analyzing logs. That is not the exact use case. It can do more than that if used correctly. But as it involves lots of cost, people are shifting from Elastic Search to other sources. When I am talking about pricing, it is not only the server pricing. It is the amount of memory it is using. The pricing is basically the heap Java, which is taking memory. That is the major problem happening here. If we have to run an MVP, a client comes to me and says, "Anurag, we need to do a proof of concept. Can we do it if I can pay a 4GB or 16GB expense?" How can I suggest to them that a minimum of 16GB is needed for Elastic Search so that your proof of concept will be proved? In that case, what I have to suggest from the beginning is to go with Cassandra or at the initial stage, go with PostgreSQL. The problem is the memory it is taking. That is the only thing.
it_user6903 - PeerSpot reviewer
Head of Engineering at CloudBearings
It’s got a good range of data visualisation components, but lacks the support for runtime complex query firing and support which OBIEE supports.
Primarily, a BI tool that enables analysis of unstructured and semi-structured data, as well as more traditional structured (measures, dimensions etc) data sets with ability to bring together loosely-related datasets and analyse them using search and lexical analysis tools. The in-memory key-value store database it uses doesn’t have the same costs around data manipulation, table joins and disk access that traditional databases have, and the column-based storage it uses is particularly suited to selecting from sets of dimension members.

Quotes from Members

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

Pros

"I would say that Elasticsearch is better than all the other solutions."
"This is a very rich product, and it's got a very wide functionality, and a wide range of functionalities which I don't see in the other products, especially not in the cheaper ones."
"It gives us the possibility to store and query this data and also do this efficiently and securely and without delays."
"Using real-time search functionality to support operational decisions has been helpful."
"The speed with which Elastic Search is able to search through all of the documents we place into it is quite remarkable, as we search through 65 billion documents in less than a second in most cases, on a constant consistent basis."
"The most valuable features of Elastic Enterprise Search are it's cloud-ready and we do a lot of infrastructure as code. By using ELK, we're able to deploy the solution as part of our ISC deployment."
"The initial setup is fairly simple."
"I appreciate the indexing capabilities and the speed of indexing in their product, which demonstrates how quickly logs are collected and stored."
"Primarily, a BI tool that enables analysis of unstructured and semi-structured data, as well as more traditional structured data sets with the ability to bring together loosely related datasets and analyse them using search and lexical analysis tools."
 

Cons

"Elastic Search should provide better guides for developers."
"An improvement would be to have an interface that allows easier navigation and tracing of logs."
"Elasticsearch is useful for different business processes, but there are some problems."
"The one area that can use improvement is the automapping of fields."
"There are potential improvements based on our client feedback, like unifying the licensing cost structure."
"They're making changes in their architecture too frequently."
"I have not been using the solution for many years to know exactly the improvements needed. However, they could simplify how the YML files have to be structured properly."
"The different applications need to be individually deployed."
"It has a good range of data visualisation components, and a web-based dashboard that appears to do a similar job to OBIEE’s interactive dashboard but lacks the support for runtime complex query firing and support which OBIEE provides through the Essbase engine."
 

Pricing and Cost Advice

"We are using the free version and intend to upgrade."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"The solution is free."
"We are using the Community Edition because Elasticsearch's licensing model is not flexible or suitable for us. They ask for an annual subscription. We also got the development consultancy from Elasticsearch for 60 days or something like that, but they were just trying to do the same trick. That's why we didn't purchase it. We are just using the Community Edition."
"We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
"The tool is not expensive. Its licensing costs are yearly."
"The basic license is free, but it comes with a lot of features that aren't free. With a gold license, we get active directory integration. With a platinum license, we get alerting."
"The premium license is expensive."
Information not available
report
Use our free recommendation engine to learn which Indexing and Search solutions are best for your needs.
885,286 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Computer Software Company
10%
Manufacturing Company
9%
Retailer
7%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business38
Midsize Enterprise10
Large Enterprise45
No data available
 

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?
On the subject of pricing, Elastic Search is very cost-efficient. You can host it on-premises, which would incur zero cost, or take it as a SaaS-based service, where the expenses remain minimal.
What needs improvement with ELK Elasticsearch?
From the UI point of view, we are using most probably Kibana, and I think they can do much better than that. That is something they can fine-tune a little bit, and then it will definitely be a good...
Ask a question
Earn 20 points
 

Also Known As

Elastic Enterprise Search, Swiftype, Elastic Cloud
Endeca
 

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.
Virgin Media, Agilent, NHS Business Services Authority, IBFD, Valdosta State University, Ministry of Labor and Social Policy, Delphi Automotive, Riverbed
Find out what your peers are saying about Elastic, Luigi's Box, OpenText and others in Indexing and Search. Updated: March 2026.
885,286 professionals have used our research since 2012.