FME vs webMethods.io comparison

"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."

"FME is spatially aware and understands how to deal with the conversion of spatial objects and their attributes."

"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."

"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."

"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."

"The performance is good."

"The solution has a very comprehensive and versatile set of connectors. I've been able to utilize it for multiple, different mechanisms. We do a lot of SaaS and we do have IoT devices and the solution is comprehensive in those areas."

"webMethods Integration Server is an easy-to-use solution and does not require a lot of coding."

"It’s fairly easy to view, move, and mange access across different components. Different component types are categorized and can be viewed in a web based administration console."

"Segregation of deployment for the environments is the most valuable feature of the solution."

"All of the components are very independent but are tied together to give the business value."

"We needed a tool that was able to orchestrate and help us configure our APIs so that we could maintain and see the heartbeat, traffic, trends, etc."

"How simple it is to create new solutions."

"We are looking at the possibility of using Glue instead of FME, using the native AWS product."

"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."

"To get a higher rating, it would have to improve the price and the associated scalability. These are the main issues."

"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."

"FME's price needs improvement for the African market."

"Improvements could be made to mapping presentations."

"The learning curve is a little steep at first."

"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."

"​Large file handling is pretty hard comparatively to other middleware tools."

"Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems."

"The product needs to be improved in a few ways. First, they need to stabilize the components of the whole platform across versions. Also, they should stop replacing old components with brand new ones and, rather, improve by evolution."

"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."

"Prices should be reduced, ideally by up to 30% for long-term customers like us."

"The UI for the admin console is very old. It hasn't been updated for years and is pretty much the same one that we started with. This is something that could be refreshed and made more modern."

"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."

"It is expensive, but we reached a good agreement with the company. It is still a little bit expensive, but we got a better deal than the previous one."

"The pricing is a yearly license."

"webMethods.io Integration's pricing is high and has yearly subscription costs."

"Pricing is the number-one downfall. It's too expensive. They could make more money by dropping the price in half and getting more customers. It's the best product there is, but it's too expensive."

"The solution’s pricing is too high."

"It is worth the cost."

"I do see a lack of capabilities inside of the monetization area for them. They have a cloud infrastructure that is pay per use type of a thing. If you already use 1,000 transactions per se, then you can be charged and billed. I see room for improvement there for their side on that particular capability of the monetization."

"Its cost depends on the use cases."