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

"Using real-time search functionality to support operational decisions has been helpful."
"It helps us to analyse the logs based on the location, user, and other log parameters."
"The most valuable feature of the solution is its utility and usefulness."
"The solution is quite scalable and this is one of its advantages."
"It is stable."
"Data indexing of historical data is the most beneficial feature of the product."
"I find the solution to be fast."
"I appreciate that Elastic Enterprise Search is easy to use and that we have people on our team who are able to manage it effectively."
"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."
"Working with complicated algorithms in huge datasets is really easy in Weka."
"I like the machine algorithm for clustering systems. Weka has larger capabilities. There are multiple algorithms that can be used for clustering. It depends upon the user requirements. For clustering, I've used DBSCAN, whereas for supervised learning, I've used AVM and RFT."
"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's best features are its user-friendly graphic interface interpretation of data sets and the ease of analyzing data."
"It is a stable product."
"It doesn’t cost anything to use the product."
 

Cons

"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."
"An improvement would be to have an interface that allows easier navigation and tracing of logs."
"This product could be improved with additional security, and the addition of support for machine learning devices."
"The solution must provide AI integrations."
"Elasticsearch could be improved in terms of scalability."
"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."
"Enterprise scaling of what have been essentially separate, free open source software (FOSS) products has been a challenge, but the folks at Elastic have published new add-ons (X-Pack and ECE) to help large companies grow ELK to required scales."
"The reports could improve."
"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."
"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."
"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."
"While it might offer insights for basic warehouse tasks, it falls short of deeper understanding and results."
"Within the basic Weka tool, I don't see many tools that are available where we can analyze and visualize the data that well."
"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."
"The filter section lacks some specific transformation tools. If you want to change a variable from a numeric variable to a categorical variable, you don't have a feature that can enable you to change a variable from a numeric variable to a categorical variable."
"If there are a lot more lines of code, then we should use another language."
 

Pricing and Cost Advice

"To access all the features available you require both the open source license and the production license."
"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."
"This product is open-source and can be used free of charge."
"The price could be better."
"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."
"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 pricing structure depends on the scalability steps."
"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."
"Currently, I am using an open-source version so I don't know much about the price of this solution."
"We use the free version now. My faculty is very small."
"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."
report
Use our free recommendation engine to learn which Indexing and Search solutions are best for your needs.
883,824 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
14%
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,824 professionals have used our research since 2012.