Layer7 API Management and webMethods.io are competitive in the API solutions category. Layer7 appears to have an edge in data security and traffic routing, which are vital for mobile-first strategies, while webMethods.io stands out in integration capabilities, especially with legacy systems.
Features: Layer7 is recognized for its robust API gateway that manages protocol and security token translation. It provides seamless REST-to-SOAP conversions and supports OAuth implementation, essential for securing API calls. Layer7 also offers load-balancing features and integrations with SiteMinder to guard against threats like DDoS. webMethods.io is notable for its comprehensive integration capabilities, efficient data mapping, and lifecycle management which are crucial in complex enterprise environments. It features a flow language that aids in simplifying the debugging and development process.
Room for Improvement: Layer7 users suggest foundational token support should be integrated directly into the base product to avoid additional costs for features like OAuth. Enhancements to the developer portal could elevate user experience. webMethods.io could improve its interface for more intuitive use and expand its middleware integration support, highlighting the need for a streamlined user experience aligned with existing infrastructures. Improving the developer portal is also noted as a potential area for webMethods.io.
Ease of Deployment and Customer Service: Layer7 provides on-premises and hybrid cloud deployment options. Feedback on customer service varies, especially post-Broadcom acquisition, with some users noting responsiveness issues. webMethods.io also supports on-premises and hybrid deployments. It is generally praised for good support, though similar to Layer7, users occasionally report delays. Both are recognized for strong technical support, despite some concerns about timeliness.
Pricing and ROI: Layer7 is considered pricey yet competitive, often requiring negotiation to reach a suitable price point. It can offer cost savings compared to competitors depending on the specific feature set utilized. webMethods.io is also seen as expensive but is justified by its vast integration features. Users note the potential for a favorable ROI, thanks to efficient API management, despite higher upfront costs. Both platforms emphasize understanding their value propositions to justify the investment.
Technical support is excellent, and I would rate them as ten.
An incident portal is available where we can raise tickets and based on priority, they reply.
All nodes communicate with one primary database, affecting connections and causing crashes under high load.
Whenever more resources are needed, they become available automatically without any human interference.
If any webMethods.io product is installed on-premises and a company wants to scale its application, either vertical scaling or horizontal scaling is needed.
Vertically, scalability is fine, however, I have not expanded horizontally with the product yet.
Without rebooting for ninety to one hundred eighty days, cache builds up in Linux boxes, causing memory utilization issues.
We provide support to our clients, and the minimum calls I receive are for webMethods.io; it's very stable.
There are some issues like the tool hanging or the need for additional jars when exposing web services.
Broadcom's push for upgrades from version nine to ten, ten to 10.3, and onwards to twelve needs improvement in migration processes, especially with service dependencies.
When comparing the license cost and request per minute cost, webMethods.io needs to address that.
Another enhancement would be in OCR; currently, there is a huge demand for OCR capabilities. It would be perfect if webMethods.io had a built-in component for OCR, as this would be tested and allow customers to use it better than a third-party OCR application.
A special discount of at least 50% for old customers would allow us to expand our services and request more resources.
Seeing other products makes the tool's pricing seem high.
Regarding the pricing and licensing of webMethods.io, I don't think it's expensive when compared with the features.
The flexibility to develop APIs for various platforms, from front-end applications to ATM machines, is valuable.
If we want to make a REST API, SOAP, REST, or any other type, all kinds of things are put in one box and we can make anything we want to.
It facilitates the exposure of around 235 services through our platform to feed various government entities across the entire country.
I believe data transformation is exceptional in webMethods.io because they have an online database that can cache the database online.
| Product | Market Share (%) |
|---|---|
| webMethods.io | 2.5% |
| Layer7 API Management | 2.4% |
| Other | 95.1% |
| Company Size | Count |
|---|---|
| Small Business | 23 |
| Midsize Enterprise | 13 |
| Large Enterprise | 84 |
| Company Size | Count |
|---|---|
| Small Business | 23 |
| Midsize Enterprise | 11 |
| Large Enterprise | 64 |
Layer7 API Management is a comprehensive solution that enables organizations to securely expose, manage, and monetize their APIs.
It provides features such as API gateway, developer portal, analytics, and security to ensure seamless integration and control over API traffic.
With Layer7 API Management, businesses can streamline their API operations and drive innovation.
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.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
