3scale API Management vs webMethods.io comparison

"The solution is quite lightweight, and the installation is very easy. It's like a two-click installation."

"The most valuable features are the gateway and security features."

"To me, the most valuable feature of 3scale API Management is that it lets you add a backend to the product. I also like that you can integrate it well with OpenShift clusters, making 3scale API Management a useful solution."

"It's good that they aren't adding a lot of features like ESP, etc. It's okay with just being a gateway."

"3scale API Management's best feature is API management."

"The standard deployment is very simple."

"The gateway is the most valuable feature because it makes it possible for us to gather all traffic into one proxy, which is a good thing."

"I like the API automation."

"It is a bundled product stack for A2A and B2B usage. It is one of the best products which I have used during my integration career."

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

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

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

"It's a visual tool, so our transformations can be quickly implemented without a lot of fuss. The fact that we have an easy way to expose REST services is also very interesting. It offers the possibility to connect over GMS to synchronize message brokers."

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

"The solution is scalable."

"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 would be helpful to improve the customization features so that the customer can do it based on their own needs."

"We tried to use the portal, but we decided that it wasn't enough. The content management system (CMS) is not easy to use if you want to customize things, and it's hard to get someone who has the knowledge to work with the CMS."

"The product is not that flexible for developers. It's less flexible and rigid. It's not easy to make changes or customize it."

"The user experience could be better. The developer portal is too complex and hard to configure."

"What was suggested by Red Hat was a crucial part of the configuration, but when we started to ask about the supportability of this configuration, Red Hat said only some parts of the configuration would be supported."

"I believe the CMS part of it has room for improvement though. That is where you write a couple of things if you want to publish your API. It's based on liquid scripting, which doesn't seem like the obvious ones to script with."

"3scale API Management only supports restful APIs and doesn't support SOAP."

"What I'd like to improve in 3scale API Management is its route-limiting feature. Currently, I don't know how to do that effectively on the solution, but in Kong, I know how to do it, so I would love to see route-limiting being easily done on 3scale API Management. It would also be good if there was some authentication that you could do from 3scale API Management because Kong offers that functionality out of the box. What I'd love to see in the next release of 3scale API Management is the ability to integrate more plug-ins easily onto the platform, so you'll be able to extend it, and even do customs management. If Red Hat could offer that extension where it allows the internal organization where 3scale API Management is deployed on-premise to integrate its tools on top of 3scale API Management and provide an API for that, that will make the solution very powerful."

"The product needs to be improved in a few ways. First, they need to stabilize the components of the whole platform across versions. Also, they should stop replacing old components with brand new ones and, rather, improve by evolution."

"Technical support is an area where they can improve."

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

"When migration happens from the one release to an upgraded release from Software AG, many of the existing services are deprecated and developers have to put in effort testing and redeveloping some of the services. It would be better that upgrade releases took care to support the lower-level versions of webMethods."

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

"This product is for larger companies. Compared to TIBCO I think webMethods is better in terms of ease of use and support."

"webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience."

"Other products have been using AI and cloud enhancements, but webMethods Integration Server is still lagging in that key area."

"The pricing is affordable, it's cheap."

"The cost was around $45,000 per year."

"I don't think that 3scale is very expensive."

"3scale API Management has reasonable pricing, judging from its competitor, Kong. My organization pays yearly for the 3scale API Management license, though I'm unable to give the exact figure because every single day there are new clusters deployed. I'm in charge of three to four clusters in my team, but give or take, it costs a few thousand lakhs."

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

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

"I do see a lack of capabilities inside of the monetization area for them. They have a cloud infrastructure that is pay per use type of a thing. If you already use 1,000 transactions per se, then you can be charged and billed. I see room for improvement there for their side on that particular capability of the monetization."

"The product is expensive."

"The price is high and I give it a five out of ten."

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

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

"It is a cost-effective solution."