Dataloader.io vs webMethods.io comparison

"I find DataLoader's ability to easily integrate with external keys valuable, which is a bit more challenging with DBM."

"he product’s most valuable feature is ease of access."

"DataLoader is cost-effective since it is free."

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

"The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation."

"The most valuable feature is stability."

"The tool supports gRPC."

"It frankly fills the gap between IT and business by having approval and policy enforcement on each state and cycle of the asset from the moment it gets created until it is retired."

"The tool is very powerful and user-friendly."

"Ease of implementation and flexibility to hold the business logic are the most valuable features."

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

"DataLoader has limitations, including constraints with file sizes and transactions."

"Dataloader has limitations, including constraints with file sizes and transactions. Additionally, at times it can be slow, and when integrating DBM, we find it more complex than Dataloader."

"We need help with large data migrations. It only works well for a few thousand records or less than a million records."

"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."

"I'd like to see the admin portal for managing the integration server go up a level, to have more capabilities and to be given a more modern web interface."

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

"One area that needs improvement is the version upgrade process. Many customers I've worked with encounter challenges when transitioning from their current version, such as x or 9, to a newer version. The process is not smooth, and they must shift their entire website."

"The price should be reduced to make it more affordable."

"The orchestration is not as good as it should be."

"This is a great solution and the vendor could improve the marketing of the solution to be able to reach more clients."

"It is quite expensive."

"The product is inexpensive and economical."

"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."

"Initialy good pricing and good, if it comes to Enterprise license agreements."

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

"I signed a three-year deal with them. It is a yearly locked-in price for the next three years."

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

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

"With our current licensing, it's very easy for us to scale. With our older licensing model, it was very hard. This is definitely something that I would highlight."

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