As it is a mature product, I don't see the need for a lot of improvements. The solution is increasing and bringing more and more areas of compliance into the picture. I think the tool is compliant to meet the standards, especially in terms of, health compliance, fintech compliance, or PCI compliance system by enterprise or API compliant. In the area of compliance, the tool is improving and getting more accelerators. The tool has been improving a few things, and making it better. I think that webMethods API Gateway is getting acquired by IBM. I don't see any challenges attached to the product. Lately, webMethods API Gateway got introduced as a separate product. Initially, there was a more web service approach, after which webMethods API Gateway moved to the REST approach to meet the industry standards, providing the product more flexibility. The high price of the product is an area of concern where improvements are required.
Enterprise Architect at PT Bank Mandiri (Persero) Tbk.
Real User
Dec 15, 2020
Previously, we had some difficulties with end-to-end lifecycle management of APIs because the product was not yet mature enough. Two years ago, it was not yet mature in terms of the capabilities, which were still separated and not yet consolidated. There were several modules of webMethods API Gateway which needed to be consolidated into one webMethods API Gateway. Previously, they had two separate modules for API management as well as others. One of the improvements that need to be added into future releases is the ability to support other third-party monitoring tools. I know that they already support Jenkins, but in Mandiri. We use Bamboo for the deployment as well as part of Jenkins. We also install other monitoring tools, such as AppDynamics, for collecting information on performance and the problems of API Gateway hosting services. With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance. With their API-Portal, you need to have flexibility when changing the layout and teams, giving more flexibility to rearrange and do some type of UX/UI that fits into your organization. The API-Portal that comes from Software AG has some of those limitations, with only certain parts that can be fully customized.
@Rully Feranata hi,even we started using appdynamics in our environment, is there any chance we can check api ID, Application ID, correlation ID (which generated in api gw payload) in appdynamics transactions?? We need to check particular transaction on appdynamics to check network related error.
Senior Manager, IT Channels & Integration at a financial services firm with 501-1,000 employees
Real User
Sep 20, 2023
One area for improvement in webMethods API Gateway is orchestration. Currently, API Gateway lacks built-in orchestration capabilities, so organizations may need to rely on other applications for this purpose. For example, if you are calling two services and one of them fails, you may need another application to handle the rollback or recovery process. Improving orchestration within API Gateway could simplify complex service interactions.
The product should provide more customization options. Application of policy management is not easy. We have to do a lot of customization and configuration. Documentation is also a problem. Understanding the overall architecture is difficult.
The gateway server itself can improve the message queue implementation by considering the top ten web security controls. I would like to request the integration of response caching into the memory database, which would eliminate the need to construct logic within the API itself, and instead implement it directly in the gateway. The price has room for improvement.
Senior Consultant at a tech services company with 501-1,000 employees
Consultant
Mar 22, 2023
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. I would like for this to be included in the features since the client I work with always tends to avoid the solution. And if the client does not have existing interfaces with it, they choose not to proceed.
Vice President - Digital Integration at Kellton Tech Solutions Limited
Real User
Jun 3, 2021
In terms of improvements, maybe on the API monetization side, having users able to create separate API consumption plans and to be able to throttle API execution against those consumption plans at run time could be better. Those are abilities that might need some improvement. The on-premises setup can get a little complex, needs to be more simplified.
In relation to the lifecycle features, the user interface and the performance can be improved. It is not the quickest application and the user interface is not most up to date. It's a tool that has existed for quite some time, and there haven't been a lot of improvements. With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved.
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.
As it is a mature product, I don't see the need for a lot of improvements. The solution is increasing and bringing more and more areas of compliance into the picture. I think the tool is compliant to meet the standards, especially in terms of, health compliance, fintech compliance, or PCI compliance system by enterprise or API compliant. In the area of compliance, the tool is improving and getting more accelerators. The tool has been improving a few things, and making it better. I think that webMethods API Gateway is getting acquired by IBM. I don't see any challenges attached to the product. Lately, webMethods API Gateway got introduced as a separate product. Initially, there was a more web service approach, after which webMethods API Gateway moved to the REST approach to meet the industry standards, providing the product more flexibility. The high price of the product is an area of concern where improvements are required.
Previously, we had some difficulties with end-to-end lifecycle management of APIs because the product was not yet mature enough. Two years ago, it was not yet mature in terms of the capabilities, which were still separated and not yet consolidated. There were several modules of webMethods API Gateway which needed to be consolidated into one webMethods API Gateway. Previously, they had two separate modules for API management as well as others. One of the improvements that need to be added into future releases is the ability to support other third-party monitoring tools. I know that they already support Jenkins, but in Mandiri. We use Bamboo for the deployment as well as part of Jenkins. We also install other monitoring tools, such as AppDynamics, for collecting information on performance and the problems of API Gateway hosting services. With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance. With their API-Portal, you need to have flexibility when changing the layout and teams, giving more flexibility to rearrange and do some type of UX/UI that fits into your organization. The API-Portal that comes from Software AG has some of those limitations, with only certain parts that can be fully customized.
@Rully Feranata hi,even we started using appdynamics in our environment, is there any chance we can check api ID, Application ID, correlation ID (which generated in api gw payload) in appdynamics transactions?? We need to check particular transaction on appdynamics to check network related error.
One area for improvement in webMethods API Gateway is orchestration. Currently, API Gateway lacks built-in orchestration capabilities, so organizations may need to rely on other applications for this purpose. For example, if you are calling two services and one of them fails, you may need another application to handle the rollback or recovery process. Improving orchestration within API Gateway could simplify complex service interactions.
The product should provide more customization options. Application of policy management is not easy. We have to do a lot of customization and configuration. Documentation is also a problem. Understanding the overall architecture is difficult.
The gateway server itself can improve the message queue implementation by considering the top ten web security controls. I would like to request the integration of response caching into the memory database, which would eliminate the need to construct logic within the API itself, and instead implement it directly in the gateway. The price has room for improvement.
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. I would like for this to be included in the features since the client I work with always tends to avoid the solution. And if the client does not have existing interfaces with it, they choose not to proceed.
They should develop clear visibility for the onboarding. They could also improve the clustering.
The configuring of the JWT token would be improved as it is a confusing process. We require more information on this part of the solution.
In terms of improvements, maybe on the API monetization side, having users able to create separate API consumption plans and to be able to throttle API execution against those consumption plans at run time could be better. Those are abilities that might need some improvement. The on-premises setup can get a little complex, needs to be more simplified.
In relation to the lifecycle features, the user interface and the performance can be improved. It is not the quickest application and the user interface is not most up to date. It's a tool that has existed for quite some time, and there haven't been a lot of improvements. With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved.