We performed a comparison between IBM API Connect and Layer7 API Management 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."The management of the API and API portal is good."
"The solution offers a pretty good SLA."
"Using API Connect allows us to quickly create proxy APIs and saves time on end-to-end testing, which lets us deliver quickly to clients."
"The statistics component is easy to use."
"API Connect's most valuable feature is its ability to act as a gateway. It's very easy to configure security and everything else in it. You don't have to kill yourself implementing custom configurations."
"The gateway is the most valuable aspect of this solution."
"The technical support is good. Whenever we need anything, we have our IT team work with IBM to change whatever requirement is needed."
"The solution is very stable."
"Every API that we get from external or from internal goes through this layer first, and it should not be a bottleneck. That was the problem we had before. Now it's no longer a bottleneck. It's more like a throughput, this process is less than 10 milliseconds for any particular API."
"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."
"Compared to other vendors, this product is much faster in coming up with new features, which is good."
"Initial setup is straightforward. It is simple and easy to do."
"This improved our organization, because it gives the management data to discuss for the next course of action and it suggests what to work on, as the next thing."
"The security checking authentication is our primary use case for this solution."
"The most valuable feature of Layer7 API Management is that their policy is really easy to develop and it is flexible."
"Scalability: API Gateway is easily scalable horizontally and managed easily."
"Improving the documentation would be beneficial as it currently presents navigation challenges. Incorporating a step-by-step guide could facilitate the integration or migration of various systems, including databases. The existing documentation only comprises plain text, hence incorporating more interactive instructions could enhance its usefulness."
"The design time setup has a lot of customizable fields, but we need certain standard fields to be added, such as what all of the consuming systems are. This needs to be very clearly articulated during the design time."
"Installation is weak."
"It would be helpful to have access monitoring."
"I would like to see support for non-Java based services. We struggle a bit to be able to deploy and connect our .NET services because of things like data types. We had to map a couple of things. For one solution provider, we had to move them to .NET Core before we could use it properly. I would like to see more agnostic tool service platforms rather than moving it more towards Java or open source."
"IBM info-center help documentation also needs improvement. Competitive product like Apigee provide out of the box policies to run Javascript, JAVA and better/flexible logging policies."
"It would be nice to have a SaaS solution that can be deployed into the cloud."
"Possible improvement is mainly around having more of the cloud oriented architecture bringing stability in adding new capabilities around security."
"Broadcom's technical support team needs improvement."
"One day, where we can have a microservices gateway and we will not need the classic gateway at all, that is what we want to see."
"There could be more integration options included in the product."
"The product needs to keep up with newer trends even though customers might not be requesting it yet."
"The only issue we have is that we have to buy an APM license separately for end-to-end monitoring."
"The CA API Management solution has good security features, but when it comes to being used in areas like enterprise integration, where it is being used as middleware for all the IT environments, that particular feature is quite limited. It doesn't support as many protocols as an industry standard, competing product should."
"The initial setup was very complex."
"It needs better mobile features and HA configuration."
IBM API Connect is ranked 5th in API Management with 73 reviews while Layer7 API Management is ranked 10th in API Management with 109 reviews. IBM API Connect is rated 8.0, while Layer7 API Management is rated 8.4. The top reviewer of IBM API Connect writes "Good speed and performance, but it's based on a bit dated architecture". On the other hand, the top reviewer of Layer7 API Management writes "Has great drag-and-drop features and it requires minimal coding ". IBM API Connect is most compared with Apigee, IBM DataPower Gateway, Microsoft Azure API Management, MuleSoft Anypoint API Manager and IBM Cloud Pak for Integration, whereas Layer7 API Management is most compared with Apigee, Kong Gateway Enterprise, Amazon API Gateway, MuleSoft Anypoint API Manager and IBM DataPower Gateway. See our IBM API Connect vs. Layer7 API Management 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.
