The suitability of the webMethods API Portal depends on the organization's size. It's not appropriate for small or medium enterprises; rather, it's intended for larger enterprises. This is particularly in cases like ours, where it's utilized for managing big data APIs. As an example, we employ it to oversee the government's resources and permissions on a daily basis. This illustrates the significant volumes of data and APIs we handle regularly. I would rate it a nine out of ten because the solution is not very efficient in certain use cases, particularly concerning authorization. It's still developing. Despite seeking input from software experts, our organization's experience indicates that there haven't been significant instances where this solution has been effectively implemented. We even reached out to external entities for successful cases globally, but the search yielded no positive results. This lack of concrete use cases over a year's time underscores the challenge of introducing it.
Vice President - Digital Integration at Kellton Tech Solutions Limited
Real User
Jun 3, 2021
We are partners with Software AG. We've been a partner for more than 20 years now. I'm an IT consultant. We are a consulting company, most of my teams are certified in Software AG technology, and we've worked for a lot of customers leveraging that technology. We typically deal with the most up-to-date versions of the solution, although occasionally, one or two might be a version behind. A lot of the API Portal and Gateway form the layer of API management, however, usually, API management does not go on its own. There's typically some level of an integration layer behind it as well. Either a customer is applying an API management layer on top of an existing integration layer, or, if not, a customer is starting fresh and has to apply both layers subsequently, or consecutively. It's kind of like creating an API management layer, and a hybrid integration layer. Both go together, especially in data integration, or in application integration and cloud application integration. Overall, I would rate the solution at a seven out of ten.
webMethods.io Integration is a powerful integration platform as a service (iPaaS) that provides a combination of capabilities offered by ESBs, data integration systems, API management tools, and B2B gateways.
The suitability of the webMethods API Portal depends on the organization's size. It's not appropriate for small or medium enterprises; rather, it's intended for larger enterprises. This is particularly in cases like ours, where it's utilized for managing big data APIs. As an example, we employ it to oversee the government's resources and permissions on a daily basis. This illustrates the significant volumes of data and APIs we handle regularly. I would rate it a nine out of ten because the solution is not very efficient in certain use cases, particularly concerning authorization. It's still developing. Despite seeking input from software experts, our organization's experience indicates that there haven't been significant instances where this solution has been effectively implemented. We even reached out to external entities for successful cases globally, but the search yielded no positive results. This lack of concrete use cases over a year's time underscores the challenge of introducing it.
We are partners with Software AG. We've been a partner for more than 20 years now. I'm an IT consultant. We are a consulting company, most of my teams are certified in Software AG technology, and we've worked for a lot of customers leveraging that technology. We typically deal with the most up-to-date versions of the solution, although occasionally, one or two might be a version behind. A lot of the API Portal and Gateway form the layer of API management, however, usually, API management does not go on its own. There's typically some level of an integration layer behind it as well. Either a customer is applying an API management layer on top of an existing integration layer, or, if not, a customer is starting fresh and has to apply both layers subsequently, or consecutively. It's kind of like creating an API management layer, and a hybrid integration layer. Both go together, especially in data integration, or in application integration and cloud application integration. Overall, I would rate the solution at a seven out of ten.
I would rate webMethods API Portal a seven out of ten.