HiT Software DBMoto vs webMethods.io comparison

"The most valuable features are that is easy to install and it is user-friendly."

"DBMoto was very simple to set up and move our tables to the Oracle DB."

"EDI is robust and integration with SAP is good."

"The development is very fast. If you know what you're doing, you can develop something very easily and very fast."

"The core product can be used not only for automatic file transfers between applications, but also as an Enterprise Service Bus (ESB)."

"The connectivity that the tool provides, along with the functionalities needed for our company's business, are some of the beneficial aspects of the product."

"One [of the most valuable features] is the webMethods Designer. That helps our developers develop on their own. It's very intuitive for design. It helps our developers to speed the development of services for the integrations."

"It is good for communicating between the systems and for publishing and subscribing. We can easily retrieve data. It is good in terms of troubleshooting and other things."

"It has a good integration server, designer, and a very good API portal."

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

"This product would be improved with additional built-in functions for simpler date conversion, as well as for data type transformations."

"Pricing is an area that needs improvement."

"In terms of improvements, maybe on the API monetization side, having users able to create separate consumption plans and throttle all those consumption plans towards the run time could be better."

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

"In terms of improvement, it would be better if it adapted quicker to open standards. It took a while for API specification before the last version was available. The spec of version two was rather quick."

"It could be more user-friendly."

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

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

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

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

"I found the price to be quite reasonable."

"Customers pay a license fee yearly."

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

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

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

"There are no hidden costs in addition to the standard licensing fees for webMethods. For corporate organizations, it's a very cheap or fairly priced product, but for growing or small businesses, it's quite expensive. These businesses would probably need to consider an enterprise services bus at some point. Thus, from a pricing point, it closes out non-cooperate businesses."

"The product is expensive."

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

"Sometimes we don't have a very clear idea what the licensing will entail at first, because it can be very customizable. On one hand, this can be a good thing, because it can be tailored to a specific customer's needs. But on the other hand it can also be an issue when some customer asks, "What's the cost?" and we can't yet give them an accurate answer."

"Some of the licensing is "component-ized," which is confusing to new users/customers."