CentraSite vs webMethods.io comparison

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

"With webMethods, the creation of servers and the utilization of Trading Networks facilitate B2B integration. It resolves any related issues effectively."

"It integrates well with various servers."

"webMethods Integration Server is an easy-to-use solution and does not require a lot of coding."

"High throughput and excellent scalability."

"What I found most valuable in webMethods Integration Server is that it's a strong ESB. It also has strong API modules and portals."

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

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

"Oracle's self-service capabilities, of which we make extensive use, is the most valuable feature."

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

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

"Scalability and connectors to different cloud applications is lacking."

"The price has room for improvement."

"Version control is not very easy. The packages and the integration server are on Eclipse IDE, but you can't compare the code from the IDE. For example, if you are working on Java code, doing version control and deployment for a quick comparison between the code isn't easy. Some tools or plug-ins are there, such as CrossVista, and you can also play with an SVN server where you have to place your package, and from there, you can check, but you have to do that as a separate exercise. You can't do it from the IDE or webMethods server. You can't just right-click and upload your service."

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

"The product must add more compatible connectors."

"When it comes to scaling, it requires more RAM and more machines."

"Some of the things that we use cannot be done in this solution. For these things, we have to either use a Java service or a util service. There is no predefined or existing service that we can use. So, we have to work on the util service and write on top of it. Its price can also be better. It is pretty costly because they charge us for each transmission."

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

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

"Its cost depends on the use cases."

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

"The product is expensive."

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

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

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