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

Elastic Search vs Weka 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 (6th), Search as a Service (1st), Vector Databases (2nd)
Weka
Average Rating
7.6
Reviews Sentiment
6.8
Number of Reviews
14
Ranking in other categories
Data Mining (4th), Anomaly Detection Tools (1st)
 

Mindshare comparison

Elastic Search and Weka aren’t in the same category and serve different purposes. Elastic Search is designed for Indexing and Search and holds a mindshare of 12.0%, down 26.3% compared to last year.
Weka, on the other hand, focuses on Data Mining, holds 8.8% mindshare, down 21.1% since last year.
Indexing and Search Mindshare Distribution
ProductMindshare (%)
Elastic Search12.0%
Lucidworks6.3%
OpenText Knowledge Discovery (IDOL)6.1%
Other75.6%
Indexing and Search
Data Mining Mindshare Distribution
ProductMindshare (%)
Weka8.8%
IBM SPSS Modeler18.9%
IBM SPSS Statistics18.3%
Other54.0%
Data Mining
 

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.
XS
Manager at XS AMSAFIS DATASETS, S.L.
A good solution offering a range of tools but is limited by its user-handling capacities
In a new machine learning job, if the method is a bit foreign to me, if I have to do it in R, it could be a tedious task. First, I need to identify the libraries required for the new methodology. This can involve identifying two, three, or even four libraries. Then, I need to read their manuals thoroughly. This is time-consuming. In Weka, as all machine learning tools are on my desktop, I easily find out the method. As a freelancer, people send me datasets, and I work on the statistics at home before providing the solution. When a solution needs to be implemented on a server, server programmers install it on the server. This is similar to Power BI, where I prepare files on my desktop, and someone else uploads them to the server for others to access. I think I cannot send a Weka solution to a server programmer. In Weka, anyone can run the program without being a programmer, which is a good feature since the entry cost is very low.

Quotes from Members

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

Pros

"My favorite feature is always aggregations and aggregators; you do not have to do multiple queries and it is always optimized for me, and I always got the perfect results because I am using full text search with aliases and keyword search, everything I am performing it, and it always performs out of the box."
"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."
"It is a stable and good platform."
"There's lots of processing power. You can actually just add machines to get more performance if you need to. It's pretty flexible and very easy to add another log. It's not like 'oh, no, it's going to be so much extra data'. That's not a problem for the machine. It can handle it."
"The best feature of Elastic Search is it does exactly what it says."
"The best feature of Elastic Search that I appreciate is its monitoring capability."
"Overall, considering key aspects like cost, learning curve, and data indexing architecture, Elasticsearch is a very good tool."
"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 analytics with Elastic benefits us due to the huge traffic volume in our organization, which reaches up to 60,000 requests per second. With logs of approximately 25 GB per day, manually analyzing traffic behavior, payloads, headers, user agents, and other details is impractical."
"The path of machine learning in classification and clustering is useful. The GUI can get you results. No programming is needed. No need to write down your script first or send to your model or input your data."
"Working with complicated algorithms in huge datasets is really easy in Weka."
"Weka is a very nice tool, it needs very small requirements. If I want to implement something in Python, I need a lot of memory and space but Weka is very lightweight. Anyone can implement any kind of algorithm, and we can show the results immediately to the client using the one-page feature. The client always wants to know the story. They want the result."
"The interface is very good, and the algorithms are the very best."
"I mainly use this solution for the regression tree, and for its association rules. I run these two methodologies for Weka."
"Weka eliminates the need for coding, allowing you to easily set parameters and complete the majority of the machine learning task with just a few clicks."
"It is a stable product."
"With clustering, if it's a yes, it's a yes, if it's a no, it's a no. It gives you a 100% level of accuracy of a model that has been trained, and that is in most cases, usually misleading. Classification is highly valuable when done as opposed to clustering."
 

Cons

"I think the first area for improvement is pricing, as the cluster cost for Elastic Search is too high for me."
"Kibana should be more friendly, especially when building dashboards."
"There should be more stability."
"Elastic Enterprise Search could improve its SSL integration easier. We should not need to go to the back-end servers to do configuration, we should be able to do it on the GUI."
"Elastic Enterprise Search's tech support is good but it could be improved."
"The solution has quite a steep learning curve. The usability and general user-friendliness could be improved. However, that is kind of typical with products that have a lot of flexibility, or a lot of capabilities. Sometimes having more choices makes things more complex. It makes it difficult to configure it, though. It's kind of a bitter pill that you have to swallow in the beginning and you really have to get through it."
"The upgrade experience and inflexibility with fields keeps Elastic Search from being a perfect 10."
"From the UI point of view, we are using most probably Kibana, and I think they can do much better than that."
"Weka is a little complicated and not necessarily suited for users who aren't skilled and experienced in data science."
"If there are a lot more lines of code, then we should use another language."
"Not particularly user friendly."
"Weka could be more stable."
"I believe is there are a few newer algorithms that are not present in the Weka libraries. Whereas, for example, if I want to have a solution that involves deep learning, so I don't think that Weka has that capability. So in that case I have to use Python for ... predict any algorithms based on deep learning."
"Within the basic Weka tool, I don't see many tools that are available where we can analyze and visualize the data that well."
"The visualization of Weka is subpar and could improve. Machine learning and visualization do not work well together. For example, we want to know how we can we delete empty cells or how can we fill in the empty cells without cleaning the data system and putting it together."
"A few people said it became slow after a while."
 

Pricing and Cost Advice

"​The pricing and license model are clear: node-based model."
"The solution is less expensive than Stackdriver and Grafana."
"The premium license is expensive."
"To access all the features available you require both the open source license and the production license."
"Elastic Search is open-source, but you need to pay for support, which is expensive."
"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."
"The price of Elastic Enterprise is very, very competitive."
"The pricing structure depends on the scalability steps."
"The solution is free and open-source."
"We use the free version now. My faculty is very small."
"Currently, I am using an open-source version so I don't know much about the price of this solution."
"As far as I know, Weka is a freeware tool, and I am not aware if they have an online solution or if it is a commercial product."
report
Use our free recommendation engine to learn which Indexing and Search solutions are best for your needs.
883,546 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Computer Software Company
11%
Manufacturing Company
9%
Retailer
7%
Educational Organization
15%
University
13%
Computer Software Company
8%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business37
Midsize Enterprise10
Large Enterprise45
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise1
Large Enterprise2
 

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?
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 startu...
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.
Information Not Available
Find out what your peers are saying about Elastic Search vs. Weka and other solutions. Updated: January 2022.
883,546 professionals have used our research since 2012.