No more typing reviews! Try our Samantha, our new voice AI agent.

Elastic Search vs IBM Watson Discovery 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
Ranking in Indexing and Search
1st
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
99
Ranking in other categories
Cloud Data Integration (5th), Search as a Service (1st), Vector Databases (5th)
IBM Watson Discovery
Ranking in Indexing and Search
10th
Average Rating
7.8
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Indexing and Search category, the mindshare of Elastic Search is 10.1%, down from 24.1% compared to the previous year. The mindshare of IBM Watson Discovery is 3.2%, down from 4.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Indexing and Search Mindshare Distribution
ProductMindshare (%)
Elastic Search10.1%
IBM Watson Discovery3.2%
Other86.7%
Indexing and Search
 

Featured Reviews

reviewer2817942 - PeerSpot reviewer
Senior Software Engineer at a consultancy with 11-50 employees
Logging and vector search have transformed observability and empowered reliable ai agents
Elastic Search is not specifically being used for certain purposes. I deploy Elastic Search database on the cloud and use cloud services so that nobody can attack. However, I do not use Elastic Search to resolve attack issues. The basic main purpose of Elastic Search, as of now, I feel it can do more in the AI area. Sometime I saw that when I am developing RAG and have to generate the embeddings, which I call metadata, sometimes it tries to fail. That durability or issue handling should be improved, but apart from that, I did not find anything as of now. As per my use case, whatever I am using seems pretty good. Apart from that, some definitely improvement will be there. One improvement is that it should be faster. Whenever I am searching any logs, it takes much time. For example, if I open my log in Notepad or a similar tool, I can search the text within a second. With Elastic Search, it takes a little bit of time, ten to fifteen seconds. That can be improved. Sometimes, engineers take time to assign when I create a ticket.
Geraldo Lima - PeerSpot reviewer
Sales Director at Kukac
Stable, scalable, and has testing and conversational AI features
The total time it takes to deploy IBM Watson Discovery depends on the documents you'll be working with. For example, I was in a situation where I was working with some painting files and folders for a painting store. The store had PDF documents, but the information was mixed up, so I had to treat the documents on IBM Watson Discovery, and discovering and understanding each PDF file took longer. The process is more straightforward for plain documents, and you have to work with questions that will help IBM Watson Discovery understand the documents. The time to deploy the product depends on the quantity and type of documents you'll be working with.

Quotes from Members

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

Pros

"Elasticsearch includes a graphical user interface (GUI) called Kibana, and the GUI features are extremely beneficial to us."
"The special text processing features in this solution are very important for me."
"The most valuable feature is the out of the box Kibana."
"Elastic Search is the perfect tool for scalability."
"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 solution is very good with no issues or glitches."
"The solution has a lot of features; they have machine learning jobs they can implement, I'm not there yet, but I can use anomaly detection to see there are various processes that can find users that aren't supposed to log onto certain machines."
"I find the solution to be fast."
"Being able to have some rules to extract the entities is valuable."
"The most valuable features of IBM Watson Discovery are the integration with the rest of the Watson Suite and the Watson Assistant capability. If you use Watson Assistant, the ability for it to be able to determine the accuracy of your voice models and your voice response systems is a benefit."
"The most valuable feature of IBM Watson Discovery is testing, mainly because the product applies conversational AI, which means I can ask questions to get the information I want from a specific test area."
"It has allowed us to provide longer service availability for support to users."
"Being able to have some rules to extract the entities is valuable. The capability to crawl external sites and internal documents, and then draw internal information with external contents is also valuable."
"Language support and the ability to build a natural language of speech recognition are the most valuable features."
 

Cons

"To do what we want to do with Elastic Search, the queries can get complex and require a fuller understanding of the DSL."
"They should improve its documentation. Their official documentation is not very informative. They can also improve their technical support. They don't help you much with the customized stuff. They also need to add more visuals. Currently, they have line charts, bar charts, and things like that, and they can add more types of visuals. They should also improve the alerts. They are not very simple to use and are a bit complex. They could add more options to the alerting system."
"In terms of product improvement, ratio aggregation is not supported in this solution."
"The GUI is the part of the program which has the most room for improvement."
"It is hard to learn and understand because it is a very big platform. This is the main reason why we still have nothing in production. We have to learn some things before we get there."
"The price could be better."
"Kibana should be more friendly, especially when building dashboards."
"I think the first area for improvement is pricing, as the cluster cost for Elastic Search is too high for me."
"The support from IBM Watson Discovery is good but could improve to make it great."
"There are probably other chatbots out there that were built for specific use cases and are easier to deploy than this."
"IBM Watson Discovery has moved to a newer version and it is very difficult to train the newer version."
"It needs a lot of memory. Our index is very big. It is around 100 gigabytes. So, we need more than 100 gigabytes of memory to use Watson."
"There are probably other chatbots out there that were built for specific use cases and are easier to deploy than this. Having said that, Watson is way more flexible. While it may require a greater amount of effort, it is not substantially more than some of the other ones that are kind of prebuilt for a specific use case. It would be good to have more prebuilt and specific use cases and specific business models. It can have better phone integration, even though I think that it is actually becoming less of an issue. Most people are online nowadays."
"The pricing is an area for improvement in IBM Watson Discovery because the customer initially used the free version. Still, when he needed more questions and documents, he had to move to a different version, which was paid and cost $500 per month. That change in pricing made my company lose many customers."
 

Pricing and Cost Advice

"This is a free, open source software (FOSS) tool, which means no cost on the front-end. There are no free lunches in this world though. Technical skill to implement and support are costly on the back-end with ELK, whether you train/hire internally or go for premium services from Elastic."
"It can move from $10,000 US Dollars per year to any price based on how powerful you need the searches to be and the capacity in terms of storage and process."
"The solution is free."
"​The pricing and license model are clear: node-based model."
"We use the free version for some logs, but not extensive use."
"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."
"The solution is affordable."
"The price of Elasticsearch is fair. It is a more expensive solution, like QRadar. The price for Elasticsearch is not much more than other solutions we have."
"Cost-wise, it is very reasonable because it is cloud-based."
"IBM Watson Discovery is an expensive product."
report
Use our free recommendation engine to learn which Indexing and Search solutions are best for your needs.
900,747 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Manufacturing Company
9%
Computer Software Company
8%
Retailer
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business40
Midsize Enterprise12
Large Enterprise49
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for ELK Elasticsearch?
Elastic Search is easy to use in Azure cloud. Mostly, my full company uses Azure cloud, so it is easy to use. Cost-wise, my company found Elastic Search is good. Cost matters. Based on cost and use...
What needs improvement with ELK Elasticsearch?
The initial configuration could be easier; at first, the learning curve is a little high, and over time, it becomes easier. For me, the initial configuration might be improved.
What is your primary use case for ELK Elasticsearch?
We use Elastic Search for a research application based on paper study, and the primary usage is for indexing the data and then functioning in a similar way to an e-commerce search bar.
Ask a question
Earn 20 points
 

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.
Prudential, Bradesco, Woodside
Find out what your peers are saying about Elastic Search vs. IBM Watson Discovery and other solutions. Updated: June 2026.
900,747 professionals have used our research since 2012.