CentraSite vs webMethods.io comparison

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

"In the API gateway, there is a new feature that allows us to filter logs within a payload. This has been a useful feature."

"It's very flexible and a good platform to use."

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

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

"Operationally, I consider the solution to be quite good."

"A product with good API and EDI components."

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

"The tool supports gRPC."

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

"This product has too many gaps. You find them after update installations. This should be covered by automatic testing."

"They should develop clear visibility for the onboarding."

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

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

"​Large file handling is pretty hard comparatively to other middleware tools."

"The solution should include REST API calls."

"t doesn't represent OOP very well, just a method and proprietary interface called IData."

"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."

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

"This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."

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

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

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

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

"webMethods Integration Server is expensive, and there's no fixed price on it because it has a point pricing model. You can negotiate, which makes it interesting."