CentraSite vs webMethods.io comparison

"The governance is powerful, and you can look up services very easily, which may reduce some development cycle time."

"ActiveTransfer lets us maintain the file in the staging area before we transfer it. After that, we can remove the file to make sure that the reconciliation process is done. Sometimes we will zip and unzip the files, but if we have a GKB file, we often ignore it."

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

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

"webMethods API Portal is overall very valuable. It is now a comprehensive API catalogue that serves various purposes, including API assessment and evaluation."

"They are the building blocks of EAI in SAG products, and they offer a very good platform."

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

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

"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 setup is mild. It's not so simple and not very difficult. You can make it happen with some configuration, but it's not easy for non-professional people."

"The product's stability is an area of concern where improvements are required."

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

"I would like to have a dashboard where I can see all of the communication between components and the configuration."

"The product must add more compatible connectors."

"The on-premises setup can be difficult."

"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."

"We'd like for them to open up to a more cloud-based solution that could offer more flexibility and maybe a better rules engine or more integration with rules engines."

"webMethods.io Integration's installation is complex. It should also improve integration and connectors."

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

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

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

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

"I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors."

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

"I am not involved in the licensing side of things."

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