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

Elastic Search vs IBM Watson Discovery comparison

Why PeerSpot?
 

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
100
Ranking in other categories
Cloud Data Integration (5th), Search as a Service (1st), Vector Databases (6th)
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 September 2026, in the Indexing and Search category, the mindshare of Elastic Search is 9.4%, down from 21.0% compared to the previous year. The mindshare of IBM Watson Discovery is 3.2%, down from 4.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Indexing and Search Mindshare Distribution
ProductMindshare (%)
Elastic Search9.4%
IBM Watson Discovery3.2%
Other87.4%
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

"It is a stable and good platform."
"The solution has great scalability."
"A good use case is saving metadata of your systems for data cataloging. Various systems, like those opened in metadata and similar applications, use Elasticsearch to store their text data."
"Decision-making has become much faster due to real-time data and quick responses."
"I find the solution to be fast."
"The solution is stable and reliable."
"The tool's stability and performance are good."
"The AI-based attribute tagging is a valuable feature."
"Language support and the ability to build a natural language of speech recognition are the most valuable features."
"It has allowed us to provide longer service availability for support to users."
"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."
"Being able to have some rules to extract the entities is valuable."
"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."
"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."
 

Cons

"The metadata gets stored along with indexes and isn't queryable."
"We had initially planned to expand use of ELK because of its cheap price and the services that are included, but given the difficulty with implementation we've decided to go with Nagios instead."
"I would like to see more open source tools and testing as well as a signature analysis in the solution."
"I see that there are areas in Elastic Search that have room for improvement, such as user documentation and onboarding processes."
"There should be more stability."
"The UI point of view is not very powerful because it is dependent on Kibana."
"I have not explored Elastic Search at the most. Searching from vector DB is available in Elastic Search, and there is one more concept of graph searching or graph database searching. I have not explored it, but if it is not there, that would be an improvement area where Elastic Search can improve."
"The initial configuration could be easier; at first, the learning curve is a little high, and over time, it becomes easier."
"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."
"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."
"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 support from IBM Watson Discovery is good but could improve to make it great."
 

Pricing and Cost Advice

"Although the ELK Elasticsearch software is open-source, we buy the hardware."
"The tool is not expensive. Its licensing costs are yearly."
"There is a free version, and there is also a hosted version for which you have to pay. We're currently using the free version. If things go well, we might go for the paid version."
"The solution is affordable."
"The pricing structure depends on the scalability steps."
"This product is open-source and can be used free of charge."
"The premium license is expensive."
"We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
"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.
913,806 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Outsourcing Company
9%
Manufacturing Company
9%
Comms Service Provider
7%
No data available
 

Company Size

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

Questions from the Community

What is your experience regarding pricing and costs for ELK Elasticsearch?
The pricing for Elastic Search is mainly budgeted according to the organization budget, so we take it as a yearly subscription, and that is acceptable since we do get a fair discount when we are ta...
What needs improvement with ELK Elasticsearch?
When we get the logs, it is mostly about how we edit the configurations and how we make changes according to the requirements of our organization. In these cases, the logs sometimes can be a bit in...
What is your primary use case for ELK Elasticsearch?
I am the Elastic Search admin for my organization, and we are using Elastic Search to handle the traffic to GCP. The monitoring of all the clusters and all the deployments are quite good, and compa...
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: September 2026.
913,806 professionals have used our research since 2012.