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

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
92
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Search as a Service (1st), Vector Databases (3rd)
Weka
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
15
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 11.3%, down 25.8% compared to last year.
Weka, on the other hand, focuses on Data Mining, holds 8.0% mindshare, down 20.3% since last year.
Indexing and Search Mindshare Distribution
ProductMindshare (%)
Elastic Search11.3%
OpenText Knowledge Discovery (IDOL)6.0%
Lucidworks6.0%
Other76.7%
Indexing and Search
Data Mining Mindshare Distribution
ProductMindshare (%)
Weka8.0%
IBM SPSS Modeler17.4%
IBM SPSS Statistics17.2%
Other57.400000000000006%
Data Mining
 

Featured Reviews

Anurag Pal - PeerSpot reviewer
Technical Lead at YatriPay Limited
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.
reviewer1522338 - PeerSpot reviewer
Phd at a educational organization with 51-200 employees
Using data mining and visualization has improved my research and student learning process
In my opinion, Weka is very useful. I think perhaps a new function with a new algorithm in data mining could be developed. The algorithms currently available in Weka are very good, and all functions are very useful. I have found that I need to use Weka with R and different databases, which has been very useful for me. I am satisfied with Weka's visualization tool. Weka is very easy to use, is very complete, and provides many benefits to the end user. It has many algorithms in data mining and many algorithms to prepare data for the next process in data mining. Weka has many graphical interfaces, though it may not have as many tools for analyzing results.

Quotes from Members

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

Pros

"I really like the visualization that you can do within it; that's really handy, and product-wise, it is a very good and stable product."
"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."
"What I appreciate about Elastic Search is that the best features include the ability to search through very big documents and index and search through them really fast."
"The solution has great scalability."
"The initial setup is fairly simple."
"The special text processing features in this solution are very important for me."
"The special text processing features in this solution are very important for me."
"Overall, considering key aspects like cost, learning curve, and data indexing architecture, Elasticsearch is a very good tool."
"Weka's best features are its user-friendly graphic interface interpretation of data sets and the ease of analyzing data."
"It doesn’t cost anything to use the product."
"Working with complicated algorithms in huge datasets is really easy in Weka."
"I mainly use this solution for the regression tree, and for its association rules. I run these two methodologies for Weka."
"It is a stable product."
"Weka is very easy to use, is very complete, and provides many benefits to the end user."
"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."
 

Cons

"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."
"I know many customers who lost their data and could not recover it."
"Its licensing needs to be improved. They don't offer a perpetual license. They want to know how many nodes you will be using, and they ask for an annual subscription. Otherwise, they don't give you permission to use it. Our customers are generally military or police departments or customers without connection to the internet. Therefore, this model is not suitable for us. This subscription-based model is not the best for OEM vendors. Another annoying thing about Elasticsearch is its roadmap. We are developing something, and then they say, "Okay. We have removed that feature in this release," and when we are adapting to that release, they say, "Okay. We have removed that one as well." We don't know what they will remove in the next version. They are not looking for backward compatibility from the customers' perspective. They just remove a feature and say, "Okay. We've removed this one." In terms of new features, it should have an ODBC driver so that you can search and integrate this product with existing BI tools and reporting tools. Currently, you need to go for third parties, such as CData, in order to achieve this. ODBC driver is the most important feature required. Its Community Edition does not have security features. For example, you cannot authenticate with a username and password. It should have security features. They might have put it in the latest release."
"It was not possible to use authentication three years back. You needed to buy the product's services for authentication."
"The pricing of this product needs to be more clear because I cannot understand it when I review the website."
"The solution has quite a steep learning curve. The usability and general user-friendliness could be improved."
"The open source version should ship basic security versions with it."
"The solution's integration and configuration are not easy. Not many people know exactly what to do."
"Scalability and performance are the main aspect of improvement in Weka, since it has the main Java limitations, regarding the JVM."
"The solution doesn’t really have very good technical support."
"A few people said it became slow after a while."
"In terms of scalability, I think Weka is not prepared to handle a large number of users."
"I'm not sure if it's reliable. It's a little difficult to get results, especially if you are on some other programs like Tableau."
"The filter section lacks some specific transformation tools."
"Weka is a little complicated and not necessarily suited for users who aren't skilled and experienced in data science."
"With Python and R, you can do anything — you have that confidence, but with Weka, I don't have that confidence."
 

Pricing and Cost Advice

"We use the free version for some logs, but not extensive use."
"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 cost varies based on factors like usage volume, network load, data storage size, and service utilization. If your usage isn't too extensive, the cost will be lower."
"The solution is less expensive than Stackdriver and Grafana."
"ELK has been considered as an alternative to Splunk to reduce licensing costs."
"We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
"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 price of Elastic Enterprise is very, very competitive."
"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."
"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."
"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.
886,510 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Computer Software Company
9%
Manufacturing Company
9%
Retailer
6%
Educational Organization
17%
University
10%
Comms Service Provider
8%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business38
Midsize Enterprise11
Large Enterprise46
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise1
Large Enterprise2
 

Questions from the Community

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...
What is your primary use case for ELK Elasticsearch?
Elastic Search use cases for us involve maintaining a huge amount of data per day, around millions of transactions for each record. We are maintaining all this data with Elastic, and Elastic is doi...
What needs improvement with Weka?
I think Weka could improve by providing more analysis options, though I am uncertain about specific recommendations at this moment.
What is your primary use case for Weka?
I use Weka in my process, study, and sciences for research with my students. I have experience with Weka's Experiment feature, as I use all the tools available in Weka. I utilize Weka's Experiment ...
What advice do you have for others considering Weka?
I use the free version of Weka, and I do not know the cost of the professional version or the lite version. I can recommend Weka to other users. I give this review a rating of 10.
 

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.
886,510 professionals have used our research since 2012.