The licensing cost is high compared to other options. Additionally, AI support could be improved. Overall, the features are good, but the high cost could be a limiting factor.
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.
Readiness Manager/Business Analytics for GCC India Operations at Ericsson
Real User
Top 5
2024-02-12T10:34:05Z
Feb 12, 2024
One area that needs improvement is the version upgrade process. Many customers I've worked with encounter challenges when transitioning from their current version, such as x or 9, to a newer version. The process is not smooth, and they must shift their entire website. If I am part of the consultancy company, I could propose taking on the version upgrade process as a separate project. From the company's perspective, this upgrade could vary in duration depending on the complexity of the business, ranging from six months to a year. This extended timeframe poses a significant challenge for customers due to the competition. From a cost perspective, getting the money for the upgrade project can be challenging for customers.
Integration Delivery Lead at a tech consulting company with 10,001+ employees
Real User
Top 10
2024-01-30T18:46:57Z
Jan 30, 2024
Other products have been using AI and cloud enhancements, but webMethods Integration Server is still lagging in that key area. It's very good as a standalone integration server, but it has to come up with more features in the cloud. The solution's API management is slightly lagging, and its API policies could be improved.
The main reason my company decided to replace webMethods.io Integration is because of the integration capabilities in the newer versions of the tool. Whenever there is a new version of webMethods.io Integrations, there is a lot of work to be done by our company since the newer versions don't offer seamless integration. The aforementioned reason can be considered for improvement in webMethods.io Integrations. With the solution, our company has experienced sudden outages at times. The product's stability is an area of concern where improvements are required. Not just the cost related to licensing but also the cost of introducing new versions need improvement in the product. When you have an OS like Windows or Apple, in which some new features are installed when you restart your system, after which everything works fine, with webMethods.io Integration, the new features introduced in the tool don't just need you to stop and restart your application but expects you to update the whole application to be able to use the new functionalities, which is something that is good. My company does a business in which we have to create a complete project which costs a lot of money. In the future, I expect to not be paying a lot of money or extra work to be able to update the product, and webMethods.io Integration needs to update the product automatically.
A potential drawback of webMethods.io API is its adaptability to legacy systems, which can vary in compatibility. This becomes evident when dealing with diverse products within a client's portfolio, requiring significant time and resources for API integration. The challenge lies in the need for a robust team and cost optimization to bridge the gap between legacy systems and modern API standards. Additionally, the time and effort involved in transforming products into API-ready formats can be a limiting factor. While the platform offers comprehensive solutions, addressing these challenges requires careful consideration and a modular approach for optimal results.
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 licensing cost is high compared to other options. Additionally, AI support could be improved. Overall, the features are good, but the high cost could be a limiting factor.
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.
webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience.
One area that needs improvement is the version upgrade process. Many customers I've worked with encounter challenges when transitioning from their current version, such as x or 9, to a newer version. The process is not smooth, and they must shift their entire website. If I am part of the consultancy company, I could propose taking on the version upgrade process as a separate project. From the company's perspective, this upgrade could vary in duration depending on the complexity of the business, ranging from six months to a year. This extended timeframe poses a significant challenge for customers due to the competition. From a cost perspective, getting the money for the upgrade project can be challenging for customers.
Other products have been using AI and cloud enhancements, but webMethods Integration Server is still lagging in that key area. It's very good as a standalone integration server, but it has to come up with more features in the cloud. The solution's API management is slightly lagging, and its API policies could be improved.
The main reason my company decided to replace webMethods.io Integration is because of the integration capabilities in the newer versions of the tool. Whenever there is a new version of webMethods.io Integrations, there is a lot of work to be done by our company since the newer versions don't offer seamless integration. The aforementioned reason can be considered for improvement in webMethods.io Integrations. With the solution, our company has experienced sudden outages at times. The product's stability is an area of concern where improvements are required. Not just the cost related to licensing but also the cost of introducing new versions need improvement in the product. When you have an OS like Windows or Apple, in which some new features are installed when you restart your system, after which everything works fine, with webMethods.io Integration, the new features introduced in the tool don't just need you to stop and restart your application but expects you to update the whole application to be able to use the new functionalities, which is something that is good. My company does a business in which we have to create a complete project which costs a lot of money. In the future, I expect to not be paying a lot of money or extra work to be able to update the product, and webMethods.io Integration needs to update the product automatically.
The patching of infrastructure is not very smooth and improved authentication should be added in the next feature.
A potential drawback of webMethods.io API is its adaptability to legacy systems, which can vary in compatibility. This becomes evident when dealing with diverse products within a client's portfolio, requiring significant time and resources for API integration. The challenge lies in the need for a robust team and cost optimization to bridge the gap between legacy systems and modern API standards. Additionally, the time and effort involved in transforming products into API-ready formats can be a limiting factor. While the platform offers comprehensive solutions, addressing these challenges requires careful consideration and a modular approach for optimal results.
The solution could be improved in the VTA part. The solution should include REST API calls.
Perhaps in the area of Microservices, where I think Trading Networks could benefit from some improvements.