FME vs webMethods.io comparison

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

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

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

"From my reseller perspective, the best features in FME are the ease of operation and the fact that it works."

"My impression of webMethods.io's drag-and-drop interface to design workflows is actually amazing."

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

"Application integrations are offered out-of-the-box, and that is extremely important to us. This is one of the main use cases that we have for it. It is about 60 to 70 percent of the workload in our application today."

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

"What I like best about webMethods Integration Server is its portfolio of connectors."

"The tool supports gRPC."

"Most of the work in our organization can be more easily done using the tool."

"When it comes to the user interface, I'm already really used to it. I cannot say anything against it. For me, it's easy to use."

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

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

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

"A potential drawback of webMethods.io API is its adaptability to legacy systems, which can vary in compatibility."

"Support is expensive."

"With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance."

"The stability of the various modules of the product suite have been a bit of a concern lately. Though their support team is always easy to reach out to, I would prefer it not come to that."

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

"The certifications and learning resources are not exposed openly enough. For instance, they have a trial version which comes with only a few basic features, and I think that community-wise they need to offer more free or open spaces where developers can feel encouraged to experiment."

"It would be nice if they had a change management system offering. We built our own deployer application because the one built into webMethods couldn't enforce change management rules. Integration into a change management system, along with the version control system, would be a good offering; it's something that they're lacking."

"The market webMethods Integration Server falls under is a very crowded market, so for the product to stand out, Software AG would need to get traction in the open source community by releasing a new version or a base version and open source it, so people can create new custom components and add it to the portfolio."

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

"The product's price is reasonable."

"Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under."

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

"It is an expensive tool. I rate the product price a nine out of ten, where ten means it is very expensive."

"Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client."

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

"There is a license needed to use the webMethods Integration Server."

"It is worth the cost."

"I would like to see better pricing for the license."