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

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

"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 standard plug-ins available for different data sources."

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

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

"Within the new version, webMethods API Gateway gives us an end-to-end lifecycle from the creation of the API up into the development, deployment, and promotion into production/live. The current end-to-end lifecycle of the API gives us enough authority and governance of the API. We know what are currently live services, what is in the testing stage of development, and what version that has been commissioned. So, the full life cycle itself gives us full authority and governance of the API."

"There's hardware, software and application integration, providing hosting flexibility."

"I feel comfortable using this product with its ease of building interfaces for developers. This is a better integration tool for integrating with various applications like Oracle, Salesforce, mainframes, etc. It works fine in the integration of legacy software as well."

"It is a very stable product."

"From a user perspective, the feature which I like the most about Integration Server is its designer."

"High throughput and excellent scalability."

"We can arrange data caching and look at the solid state. Also, the API gateway is a very good component that can handle relevant cachings and integrations, as well as and also load permitting."

"One valuable feature is that it is event-driven, so when new data is available on the source it can be quickly processed and displayed. Integration is definitely another useful feature, and B2B is one area where webMethods has its own unique thing going, whereby we can do monitoring of transactions, monitoring of client onboarding, and so on."

"Improvements could be made to mapping presentations."

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

"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's price needs improvement for the African market."

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

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

"The solution's release management feature could be better."

"I have noticed that webMethods ActiveTransfer has had problems when handling large files. For example, when we receive (and perform operations on) files that are larger than about 16 MB, the software starts losing performance."

"The Software AG Designer could be more memory-efficient or CPU-efficient so that we can use it with middle-spec hardware."

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

"The configuring of the JWT token would be improved as it is a confusing process. We require more information on this part of the solution."

"Forced migration from MessageBroker to Universal Messaging requires large scale reimplementation for JMS."

"webMethods Integration Server could improve on the version control. I'm not sure if Web Method has some kind of inbuilt integration with Bitbucket or GitHub or some kind of version control system. However, that's one area where they can improve."

"This solution could be improved by offering subscription based licensing."

"FME Server used to cost £10,000; now it can cost over £100,000."

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

"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."

"Some who consider this solution often avoid it due to its high price."

"webMethods Trading Networks is a bit costly compared to others solutions."

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

"webMethods Integration Server is expensive, and there's no fixed price on it because it has a point pricing model. You can negotiate, which makes it interesting."

"This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."

"Most of my clients would like the price of the solution to be reduced."

"The product is expensive."