We performed a comparison between Layer7 API Management and webMethods API Gateway based on real PeerSpot user reviews.
Find out in this report how the two API Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It has its own language, which make it possible to design and implement the complete flow using existing services and databases, and to create and aggregate fine-and coarse-grained APIs."
"We have more than 50 applications in the backend. We monitor the infrastructure through a database monitoring tool. Our daily tasks involve working on P1 incidents, managing change requests, conducting patching updates, working on P2 tickets, backend server certificate renewals, etc."
"It's pretty easy to use, and once we have templating set up we can add new APIs, at least through the gateway, and apply the security to them; it takes a minute."
"Easy to use, nice UI, and good search functionality."
"The initial setup process is easy and flexible."
"There are a few assertions which are built-in for threat protection. I have used them for vulnerabilities, like for DDoS attacks, XML schema validation, IP restriction, and for cross-domain."
"Compared to other vendors, this product is much faster in coming up with new features, which is good."
"I appreciate Layer 7 API management for its comprehensive approach to the entire API lifecycle, including governance, management, and analytics."
"What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth."
"The developer portal is a valuable feature."
"The most valuable aspect of this solution for me has been the configuration-based UI. Once you get the hang of it, it enables you to easily develop an API. In addition, it has many in-built policies that are quite handy."
"I like the solution's policies, transformation, mediation, and routing features."
"It's a good tool, and it has a stable messaging broker."
"Within the new version, webMethods API Gateway gives us an end-to-end lifecycle from the creation of the API up into the development, deployment, and promotion into production/live. The current end-to-end lifecycle of the API gives us enough authority and governance of the API. We know what are currently live services, what is in the testing stage of development, and what version that has been commissioned. So, the full life cycle itself gives us full authority and governance of the API."
"In the API gateway, there is a new feature that allows us to filter logs within a payload. This has been a useful feature."
"The cloud version of the solution is very easy to set up."
"Increase tools for manipulation of JSON messages."
"Layer7 API Management could have a live API creator feature, so my team can easily create APIs. Right now, the product doesn't have that feature."
"There could be more integration options included in the product."
"More developer focused tools. They have a nice debugger inside of the program, but when you are developing code with their policies, it is tough to visualize that sometimes as a developer."
"feel like Apigee's API product is more interactive. You can drag and drop with those, but it's a little more difficult in Layer7. It's less user-friendly compared to that Apigee product."
"The development toolkit used for creating APIs should be more online and user-friendly. Deployment and tracking could also be improved. Tools like Apigee provide a complete online experience along with RESTful APIs, to manage all activities. It is a very nice and user-friendly solution compared to CA."
"As the number of instances increases, its complexity of installation increases if you do not use the OVA."
"The product's initial setup phase is not very straightforward, making it an area where improvements are required."
"It is an expensive solution and not very suitable for smaller businesses."
"In terms of improvements, maybe on the API monetization side, having users able to create separate consumption plans and throttle all those consumption plans towards the run time could be better."
"With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance."
"There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere."
"They should develop clear visibility for the onboarding."
"The configuring of the JWT token would be improved as it is a confusing process. We require more information on this part of the solution."
"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."
"Understanding the overall architecture is difficult."
Layer7 API Management is ranked 10th in API Management with 109 reviews while webMethods API Gateway is ranked 12th in API Management with 9 reviews. Layer7 API Management is rated 8.4, while webMethods API Gateway is rated 8.0. The top reviewer of Layer7 API Management writes "Has great drag-and-drop features and it requires minimal coding ". On the other hand, the top reviewer of webMethods API Gateway writes "We developed several services in the cloud using a sandbox environment for our last hackathon". Layer7 API Management is most compared with Apigee, Kong Gateway Enterprise, Amazon API Gateway, MuleSoft Anypoint API Manager and Microsoft Azure API Management, whereas webMethods API Gateway is most compared with Apigee, webMethods.io Integration, Kong Gateway Enterprise, webMethods Microgateway and CentraSite. See our Layer7 API Management vs. webMethods API Gateway report.
See our list of best API Management vendors.
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.