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.8
Number of Reviews
69
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (11th), Search as a Service (1st), Vector Databases (2nd)
FME
Average Rating
8.6
Reviews Sentiment
6.8
Number of Reviews
5
Ranking in other categories
Data Integration (24th)
 

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

"Overall, considering key aspects like cost, learning curve, and data indexing architecture, Elasticsearch is a very good tool."
"It is highly valuable because of its simplicity in maintenance, where most tasks are handled for you, and it offers a plethora of built-in features."
"I like how it allows us to connect to Kafka and get this data in a document format very easily. Elasticsearch is very fast when you do text-based searches of documents. That area is very good, and the search is very good."
"It gives us the possibility to store and query this data and also do this efficiently and securely and without delays."
"I am impressed with the product's Logstash. The tool is fast and customizable. You can build beautiful dashboards with it. It is useful and reliable."
"All the quality features are there. There are about 60 to 70 reports available."
"X-Pack provides good features, like authorization and alerts."
"It helps us to analyse the logs based on the location, user, and other log parameters."
"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."
"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."
"It has standard plug-ins available for different data sources."
"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."
 

Cons

"Better dashboards or a better configuration system would be very good."
"Something that could be improved is better integrations with Cortex and QRadar, for example."
"An improvement would be to have an interface that allows easier navigation and tracing of logs."
"Performance improvement could come from skipping background refresh on search idle shards (which is already being addressed in the upcoming seventh version)."
"Elastic Search could benefit from a more user-friendly onboarding process for beginners."
"Scalability and ROI are the areas they have to improve."
"It needs email notification, similar to what Logentries has. Because of the notification issue, we moved to Logentries, as it provides a simple way to receive notification whenever a server encounters an error or unexpected conditions (which we have defined using RegEx​)."
"They're making changes in their architecture too frequently."
"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."
"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."
"Improvements could be made to mapping presentations."
"FME's price needs improvement for the African market."
"To get a higher rating, it would have to improve the price and the associated scalability. These are the main issues."
 

Pricing and Cost Advice

"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."
"Elastic Search is open-source, but you need to pay for support, which is expensive."
"The pricing structure depends on the scalability steps."
"I rate Elastic Search's pricing an eight out of ten."
"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."
"ELK has been considered as an alternative to Splunk to reduce licensing costs."
"we are using a licensed version of the product."
"The price of Elastic Enterprise is very, very competitive."
"The product's price is reasonable."
"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."
"FME Server used to cost £10,000; now it can cost over £100,000."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
850,236 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
17%
Financial Services Firm
15%
Government
9%
Manufacturing Company
8%
Government
30%
Energy/Utilities Company
14%
Computer Software Company
8%
Comms Service Provider
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

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?
I don't know about pricing. That is dealt with by the sales team and our account team. I was not involved with that.
What needs improvement with ELK Elasticsearch?
I found an issue with Elasticsearch in terms of aggregation. They are good, yet the rules written for this are not really good. There is a maximum of 10,000 entries, so the limitation means that if...
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: April 2025.
850,236 professionals have used our research since 2012.