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
89
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), 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 (2nd)
 

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 27.5% compared to last year.
Weka, on the other hand, focuses on Data Mining, holds 9.3% mindshare, down 21.2% since last year.
Indexing and Search Market Share Distribution
ProductMarket Share (%)
Elastic Search12.0%
Lucidworks6.7%
OpenText Knowledge Discovery (IDOL)6.3%
Other75.0%
Indexing and Search
Data Mining Market Share Distribution
ProductMarket Share (%)
Weka9.3%
IBM SPSS Modeler19.1%
IBM SPSS Statistics18.5%
Other53.099999999999994%
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

"All the quality features are there. There are about 60 to 70 reports available."
"The ability to aggregate log and machine data into a searchable index reduces time to identify and isolate issues for an application. Saves time in triage and incident response by eliminating manual steps to access and parse logs on separate systems, within large infrastructure footprints."
"The product is scalable with good performance."
"My favorite feature is the ease of use, particularly in how you integrate the agent; I've been using it since version 7, and we're on version 9 now, and I've seen the progress from using Beats to using the agent, making it so simple today to enroll a server with the Elastic Agent."
"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."
"We can easily collect all the data and view historical trends using the product. We can view the applications and identify the issues effectively."
"Elasticsearch includes a graphical user interface (GUI) called Kibana. The GUI features are extremely beneficial to us."
"One thing I appreciate about Elastic Search is the ability to aggregate everything into one dashboard, so I can have monitoring, logs, and traces in one portal instead of having multiple different tools to do the same."
"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."
"It is a stable product."
"It doesn’t cost anything to use the product."
"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."
"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."
"Working with complicated algorithms in huge datasets is really easy in Weka."
"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."
"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."
 

Cons

"We see the need for some improvements with Elasticsearch. We would like the Elasticsearch package to include training lessons for our staff."
"Kibana should be more friendly, especially when building dashboards."
"While integrating with tools like agents for ingesting data from sources like firewalls is valuable, I believe prioritizing improvements to the core product would be more beneficial."
"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 documentation for Elastic Search can be challenging if you're not already familiar with the platform."
"It is hard to learn and understand because it is a very big platform. This is the main reason why we still have nothing in production. We have to learn some things before we get there."
"We have an issue with the volume of data that we can handle."
"The metadata gets stored along with indexes and isn't queryable."
"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."
"A few people said it became slow after a while."
"Weka could be more stable."
"In terms of scalability, I think Weka is not prepared to handle a large number of users."
"If there are a lot more lines of code, then we should use another language."
"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."
 

Pricing and Cost Advice

"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 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."
"ELK has been considered as an alternative to Splunk to reduce licensing costs."
"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."
"We are using the free version and intend to upgrade."
"I rate Elastic Search's pricing an eight out of ten."
"The price of Elastic Enterprise is very, very competitive."
"An X-Pack license is more affordable than Splunk."
"We use the free version now. My faculty is very small."
"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."
report
Use our free recommendation engine to learn which Indexing and Search solutions are best for your needs.
882,103 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business37
Midsize Enterprise10
Large Enterprise44
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?
While Elastic Search is a good product, I see areas for improvement, particularly regarding the misconception that any amount of data can simply be dumped into Elastic Search. When creating an inde...
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.
882,103 professionals have used our research since 2012.