Key to Legacy Integration
April 15, 2025
Key to Legacy Integration
Score 8 out of 10
Vetted Review
Verified User
Modules Used
- webMethods Developer Portal
- webMethods API Gateway
- webMethods Microgateway
- webMethods AppMesh
Overall Satisfaction with IBM webMethods
We use it to to streamline and automate integration processes, connecting disparate systems, applications, and data sources across on-prem, cloud, and hybrid environments. We use it to create a seamless integration between our CRM, ERP and other systems.
Pros
- API Management
- ESB
- Real time analitics
- Automation
Cons
- UX - It's complex for newer users
- Cost - Expensive
- Cloud native capabilities - (kuberbetes)
- Limited AI capabilities
- Signifiant costs savings in legacy modernization. Instead of investing into legacy archive platform to modernize it, we simply built a conncetor to it.
- Elimination of some manual processes in our B2B transactions
- Compliance through their auditing functions
webMethods does better for end to end integrations whereas Azure is more focused on APIs. We selected webMethods because we felt their integrations, especially to mainframe environments, were much better than the others. IBM has been in this space for a long time and know it well. Otherwise, the features were comparable across products. Pricing and mainframe integrations were our primary differentiators.
Do you think IBM webMethods delivers good value for the price?
Yes
Are you happy with IBM webMethods's feature set?
Yes
Did IBM webMethods live up to sales and marketing promises?
Yes
Did implementation of IBM webMethods go as expected?
Yes
Would you buy IBM webMethods again?
Yes
Comments
Please log in to join the conversation