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

"You have dashboards, it is visual, there are maps, you can create canvases. It's more visual than anything that I've ever used."
"The UI is very nice, and performance wise it's quite good too."
"The most valuable feature of Elastic Enterprise Search is the Discovery option for the visualization of logs on a GPU instead of on the server."
"The special text processing features in this solution are very important for me."
"It helps us to analyse the logs based on the location, user, and other log parameters."
"I find the solution to be fast."
"Helps us to store the data in key value pairs and, based on that, we can produce visualisations in Kibana."
"We had many reasons to implement Elasticsearch for search term solutions. Elasticsearch products provide enterprise landscape support for different areas of the company."
"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 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."
"Weka's best features are its user-friendly graphic interface interpretation of data sets and the ease of analyzing data."
"There are many options where you can fill all of the data pre-processing options that you can implement when you're importing the data. You can also normalize the data and standardize it in an easier way."
"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."
"It is a stable product."
"Working with complicated algorithms in huge datasets is really easy in Weka."
"The interface is very good, and the algorithms are the very best."
 

Cons

"Pagination in Elastic Search is very slow."
"Elasticsearch could improve by honoring Unix environmental variables and not relying only on those provided by Java (e.g. installing plugins over the Unix http proxy)."
"Technical support should be faster."
"The solution's integration and configuration are not easy. Not many people know exactly what to do."
"What they need is to be more transparent about the actual setup of the cluster and the deployment process."
"The setup is somewhat complicated due to multiple dependencies and relations with different systems."
"There are some features lacking in ELK Elasticsearch."
"The documentation regarding customization could be better."
"While it might offer insights for basic warehouse tasks, it falls short of deeper understanding and results."
"If you have one missing value in your dataset and this missing value belongs to a specific attribute and the attribute is a numeric attribute and there is only one missing data, whenever you import this data, the problem is that Weka cannot understand that this is a numeric field. It converts everything into a string, and there is no way to convert the string into numerical math. It's really very complicated."
"In terms of scalability, I think Weka is not prepared to handle a large number of users."
"A few people said it became slow after a while."
"Within the basic Weka tool, I don't see many tools that are available where we can analyze and visualize the data that well."
"Not particularly user friendly."
"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."
"The product is good, but I would like it to work with big data. I know it has a Spark integration they could use to do analysis in clusters, but it's not so clear how to use it."
 

Pricing and Cost Advice

"The solution is affordable."
"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."
"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."
"ELK has been considered as an alternative to Splunk to reduce licensing costs."
"This product is open-source and can be used free of charge."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"The version of Elastic Enterprise Search I am using is open source which is free. The pricing model should improve for the enterprise version because it is very expensive."
"The solution is not expensive because users have the option of choosing the managed or the subscription model."
"Currently, I am using an open-source version so I don't know much about the price of this solution."
"The solution is free and open-source."
"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."
"We use the free version now. My faculty is very small."
report
Use our free recommendation engine to learn which Indexing and Search solutions are best for your needs.
884,108 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.
884,108 professionals have used our research since 2012.