Really Beyond Integration possible
Modules Used
- webMethods Developer Portal
- webMethods API Gateway
- webMethods Microgateway
- webMethods AppMesh
- Webmethods MFT
- Webmethods B2B
- Webmethods BPM
Overall Satisfaction with IBM webMethods
Unifying applications, build digital Integration Hub, modernisation, technology stack like api management, Integration, mft and b2b and bpm made digital Integration with variety of applicatiob using single platform.
Pros
- Low code or no code Integration
- Api gateway can extend to have complex logic ( low code) underneath if required
- Easy of using product line, citizen developer and adhoc integrator perspective
- Deployment flexibility
Cons
- Streaming can be the area to improve
- Messaging tool like universal Messaging, real difficult to have highly available deployment
- Extension to have run node js or javascript kind of programs.
- Time to market
- Connectivity with mutilple databases and maintain transaction boundaries
- Flexibility to maintain vm based and microservices architecture at same time.
Api gateway - policies Integration server - pluggability
We were having customer having 3 different product like api (open source), esb and different bpm product, with IBM webMethods they deprecated all three and Unified under one stack.
- Apigee Edge and Oracle Integration (OIC)
Do you think IBM webMethods Hybrid Integration delivers good value for the price?
Yes
Are you happy with IBM webMethods Hybrid Integration's feature set?
Yes
Did IBM webMethods Hybrid Integration live up to sales and marketing promises?
Yes
Did implementation of IBM webMethods Hybrid Integration go as expected?
Yes
Would you buy IBM webMethods Hybrid Integration again?
Yes
Comments
Please log in to join the conversation