IBM webMethods Hybrid Integration

The most important part is the library of pre-defined connectors for integrating applications, databases and industry standard protocols. Also, I like the platform that offers tools for monitoring integrations and associated data flows and managing governance to ensure security and compliance

It was the complete and most advanced offer for SOA based integratien solution.

The ecosystem is highly integrated. We can easily move to various deployment models (SaaS, on-prem, cloud native, etc.). There are a lot of adapters and several protocols are supported. The API Gateway philosophy is very strong and aligned to our needs.

While the webMethods has gained footprint as iPaaS - Integration Platform as a Service, it is gaining foot on SaaS - Software as a Service and trying to adapt to cloud-based integration solutions and centralized control capabilities

Obstacles in our Azure Migration despite the hybrid rhetorics

While we value the capabilities of the platform, there are a few areas where we see room for improvement. We would like to seamlessly transition integration flows between an on-premise environment (based on containers) and the iPaaS offering, in order to shift workloads as needed without limitations. In addition, a unified observability across the products would be highly valuable: at present, monitoring and logging is fragmented across each product (API GW, iPaaS, on-premise runtime, etc) and achieving a consolidated view requires integrating third party solutions. Finally, the vendor must invest in generative AI to speed up development and management of the platform.