Informatica Enterprise Data Lake vs webMethods.io comparison

"The process of using the tool's scalability option is well documented."

"Clients choose webMethods.io API for its intuitive interface, promoting seamless interaction and quick communication between systems."

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

"The main assets are its flow language, debugging, and Broker. Flow language is far better and more flexible for debugging."

"Best feature is Insight for monitoring, and as a debugging tool. It has saved us a lot of time during crisis situations."

"One of the most important features is that it gives you the possibility to do low-level integration. It provides a lot of features out of the box, and over the years, it has matured so much that any problem that is there in the market can be solved with this product. We can meet any requirements through customizations, transformations, or the logic that needs to be put in. Some of the other products struggle in this aspect. They cannot do things in a certain way, or they have a product limitation, whereas, with webMethods, I have never faced this kind of problem."

"The developer portal is a valuable feature."

"I would say the core Web-based integrations work the best. They are the most efficient and robust implementations one can do with webMethods."

"The solution's ease-of-use is its most valuable feature, in which complex issues may be resolved."

"Informatica Enterprise Data Lake's setup process was complex since it doesn't support a lot of real-time systems."

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

"It is difficult to maintain."

"Perhaps in the area of Microservices, where I think Trading Networks could benefit from some improvements."

"Technical support is an area where they can improve."

"I would like to see the price improve."

"I would like the solution to provide bi-weekly updates."

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

"There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere."

"The licenses attached to the solution are highly priced."

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

"The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product."

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

"This is an expensive product and we may replace it with something more reasonably priced."

"Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials."

"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."

"It is a cost-effective solution."

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