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

Elastic Search vs FME 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.7
Number of Reviews
72
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (10th), Search as a Service (1st), Vector Databases (3rd)
FME
Average Rating
8.6
Reviews Sentiment
6.5
Number of Reviews
7
Ranking in other categories
Data Integration (23rd)
 

Featured Reviews

Anand_Kumar - PeerSpot reviewer
Captures data from all other sources and becomes a MOM aka monitoring of monitors
Scalability and ROI are the areas they have to improve. Their license terms are based on the number of cores. If you increase the number of cores, it becomes very difficult to manage at a large scale. For example, if I have a $3 million project, I won't sell it because if we're dealing with a 10 TB or 50 TB system, there are a lot of systems and applications to monitor, and I have to make an MOM (Mean of Max) for everything. This is because of the cost impact. Also, when you have horizontal scaling, it's like a multi-story building with only one elevator. You have to run around, and it's not efficient. Even the smallest task becomes difficult. That's the problem with horizontal scaling. They need to improve this because if they increase the cores and adjust the licensing accordingly, it would make more sense.
Alan Bloor - PeerSpot reviewer
Great for handling large volumes of data, but it is priced a bit high
When I do coding, I think about every single function. Some of these functions can be very elementary, like doing a substring or some capitalization. But FME removes all that coding because it's a transformer, so the time to develop an application to get to a point where you're producing results is decreased massively. It used to take weeks and months to develop software, and now I can use something like FME, and within one day, we get results. We can look at and validate data. We make minor subtle changes to the workbenches to improve it. We can share the workbenches. We don't have to use GitHub or anything else.

Quotes from Members

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

Pros

"The security portion of Elasticsearch is particularly beneficial, allowing me to view and analyze security alerts."
"It helps us to analyse the logs based on the location, user, and other log parameters."
"The flexibility and the support for diverse languages that it provides for searching the database are most valuable. We can use different languages to query the database."
"X-Pack provides good features, like authorization and alerts."
"The solution has great scalability."
"The solution offers good stability."
"All the quality features are there. There are about 60 to 70 reports available."
"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."
"FME is spatially aware and understands how to deal with the conversion of spatial objects and their attributes."
"The most valuable feature of FME is the graphical user interface. There is nothing better. It is very easy to debug because you can see all steps where there are failures. Overall the software is easy to optimize a process."
"All spatial features are unrivaled, and the possibility to execute them based on a scheduled trigger, manual, e-mail, Websocket, tweet, file/directory change or virtually any trigger is most valuable."
"From my reseller perspective, the best features in FME are the ease of operation and the fact that it works."
"It has a very friendly user interface. You don't need to use a lot of code. For us that's the most important aspect about it. Also, it has a lot of connectors and few forms. It has a strong facial aspect. It can do a lot of facial analysis."
"We make minor subtle changes to the workbenches to improve it. We can share the workbenches. We don't have to use GitHub or anything else."
"It has standard plug-ins available for different data sources."
 

Cons

"We have an issue with the volume of data that we can handle."
"I don't see improvements at the moment. The current setup is working well for me, and I'm satisfied with it. Integrating with different platforms is also fine, and I'm not recommending any changes or enhancements right now."
"Both the graph feature and the reporting feature are a little bit lacking. The alerting also needs to be improved."
"There is another solution I'm testing which has a 500 record limit when you do a search on Elastic Enterprise Search. That's the only area in which I'm not sure whether it's a limitation on our end in terms of knowledge or a technical limitation from Elastic Enterprise Search. There is another solution we are looking at that rides on Elastic Enterprise Search. And the limit is for any sort of records that you're doing or data analysis you're trying to do, you can only extract 500 records at a time. I know the open-source nature has a lot of limitations, Otherwise, Elastic Enterprise Search is a fantastic solution and I'd recommend it to anyone."
"There are some features lacking in ELK Elasticsearch."
"The documentation regarding customization could be better."
"The GUI is the part of the program which has the most room for improvement."
"The UI point of view is not very powerful because it is dependent on Kibana."
"Improvements could be made to mapping presentations."
"The one thing that always appears in the community is the ability to make really easy loops to loop through data efficiently. That needs to be added at some point."
"FME can improve the geographical transformation. I've had some problems with the geographical transformations, but it's probably mostly because I'm not the most skilled geographer in-house. The solution requires some in-depth knowledge to perform some functions."
"To get a higher rating, it would have to improve the price and the associated scalability. These are the main issues."
"FME's price needs improvement for the African market."
"We are looking at the possibility of using Glue instead of FME, using the native AWS product."
 

Pricing and Cost Advice

"We use the free version for some logs, but not extensive use."
"The solution is affordable."
"The price could be better."
"This is a free, open source software (FOSS) tool, which means no cost on the front-end. There are no free lunches in this world though. Technical skill to implement and support are costly on the back-end with ELK, whether you train/hire internally or go for premium services from Elastic."
"​The pricing and license model are clear: node-based model."
"The pricing structure depends on the scalability steps."
"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."
"FME Server used to cost £10,000; now it can cost over £100,000."
"We used the standard licensing for our use of FME. The cost was approximately €15,000 annually. We always welcome less expensive solutions, if the solution could be less expensive it would be helpful."
"The product's price is reasonable."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
865,484 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Financial Services Firm
13%
Government
9%
Manufacturing Company
8%
Government
31%
Energy/Utilities Company
13%
Computer Software Company
7%
Comms Service Provider
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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?
We used the open-source version of Elasticsearch, which was free.
What needs improvement with ELK Elasticsearch?
It would be useful if a feature for renaming indices could be added without affecting the performance of other features. However, overall, the consistency and stability of Elasticsearch are already...
What do you like most about FME?
We make minor subtle changes to the workbenches to improve it. We can share the workbenches. We don't have to use GitHub or anything else.
What is your experience regarding pricing and costs for FME?
The pricing is really bad. Last year, they rebranded the whole pricing structure. It used to be moderately priced at about £400 per user per year. Now they've changed the whole thing, and it's expe...
What needs improvement with FME?
The one thing that always appears in the community is the ability to make really easy loops to loop through data efficiently. That needs to be added at some point. There must be a technical or comm...
 

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.
Shell, US Department of Commerce, PG&E, BC Hydro, City of Vancouver, Enel, Iowa DoT, San Antonio Water System
Find out what your peers are saying about Elastic Search vs. FME and other solutions. Updated: July 2025.
865,484 professionals have used our research since 2012.