We performed a comparison between Layer7 API Management and SwaggerHub 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."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."
"There are a couple aspects of performance. One is just speed and uptime, and it's stellar in that regard. The other is, how much effort is it to put it in place in the first place, and then how much effort is it to keep it operational. That's where its real strength is. I'm able to do things quickly and easily that I couldn't do before."
"Some of the performance matrix that API Gateway gives off, we monitor them via SNMP traps, and then we tie them into our monitoring system. You can actually monitor some of the latencies and some of the performance aspects of both API Gateways, as well back end services. So having that line of sight surely helps in terms DevOps."
"It can be scaled as we need. And it can be used in different regions. We have different data centers in the U.S. and Beijing. We use it on-premise, on-cloud, and it can be hosted and used at any place and scaled across the regions."
"The out-of-the-box security features are useful. Right now, you can just right-click and drag and drop the assertions with the rate limit. That, as well as the x-amount surge protection, is built in so we can bring that in."
"The product supports more than just HTTP protocols; it also caters to JMS and FTP protocols."
"A big win for CA was the expertise of the local country support plus having support staff on site in a matter of hours, if required."
"API Management makes dealing with APIs easier. It'll help you to move ahead on your API application journey. The solution allows developers to create more advanced security policies"
"The most valuable features are the collaboration between multiple teams and the control and distribution of specifications."
"It is quite a useful tool. It is quite good with the validation of the spec. It works quite well in terms of errors and conformity to the OpenAPI standard. It is better than Visual Studio Code in terms of editing."
"Code generation is one of the important features of SwaggerHub. We design our API, and we can generate a very rich codebase and add to it. The code generation feature is very valuable."
"The product's initial setup phase was easy and not at all difficult."
"I rate the solution's stability a ten out of ten."
"The scalability is endless."
"It is a stable solution."
"The tool's most valuable feature is licensing."
"One area where it certainly needs to improve is the way it allocates requests, in terms of rate limiting. Also, there is no native Kafka connectivity."
"The architecture of the solution does not allow for flexibility in using different components for the gateway architecture."
"From the last version, they have added more dashboard support, but there is still a lot they need to improve. In terms of monitoring, it's almost all covered. The interface can be improved, though."
"The delivery is bulky in terms of implementation. Its price could also be better. It is a very good product as compared to CA API, Google API, and WSO2 API, but its price is high. From the cloud-native perspective, some new features need to be added. It could also be made simpler to implement."
"The product needs to keep up with newer trends even though customers might not be requesting it yet."
"I feel there is a lot to improve in terms of providing plug-and-play functionalities, as at the moment it requires a lot of coding in their specific language for implementing a medium-complexity use case."
"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 overall cost of Layer7 API Management is high, they can improve it by making it less expensive."
"It could be more intuitive compared to one of its competitors."
"SwaggerHub could be improved with better integration for tools."
"The review process should be improved. There seem to be some gaps, at least for us, for the editing part because we would like to have a full request review mechanism. They support some comments, but it is really hard to manage those comments. We would like to use the full request. Therefore, we are now looking to integrate with repositories. It has integration with Bitbucket and GitHub, but we have some internal constraints, and we need to move some of the repositories to GitHub. Our source code is on-premise in Bitbucket, and it was a bit of a problem for us to integrate. Now we are transitioning our repositories to GitHub, and hopefully, we can enable the integration. This will probably solve the problem with the review and approval. Its customization should also be improved. There are limitations around the support for the developer portal. There should be more customization options for the website that you can use as a developer portal. Currently, it has only Swagger UI with minimal customization. You cannot actually add additional pages and documentation for explaining concepts and general things. That's why we have started to look around to see what other tools are doing. They should also allow tagging on the API. We would like to add some tagging on the API to reflect certain things. Currently, any metadata that you would like to have has to be a part of the spec. You cannot do anything else. It should also have support for Open API 3.1, which was released at the beginning of the year. It would be great to be able to switch to that."
"It has limited functionality...Unfortunately, some of its features are not what we need."
"SwaggerHub's UI needs to be improved as it looks very old school."
"More integration and usability with the cloud microservices would be nice"
"We have to use additional tools to test APIs."
"SwaggerHub lacks in terms of integrations. They have APIs integrated, and they also have some connectors, but they don't have integration with many of the things that we use. For example, for connecting with SVN, we had to implement external scripts. So, they should work on the integration because currently, we have to work on the integration with our DevOps, continuous delivery, or continuous deployment. It would be great if these integrations are built-in. Mainly, we would like it to integrate with SVN and Jira."
Layer7 API Management is ranked 10th in API Management with 108 reviews while SwaggerHub is ranked 13th in API Management with 8 reviews. Layer7 API Management is rated 8.4, while SwaggerHub is rated 7.8. 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 SwaggerHub writes "An easy-to-use solution for the entry point of API documentation that needs to introduce some regulatory controls". Layer7 API Management is most compared with Apigee, Kong Enterprise, Amazon API Gateway, MuleSoft Anypoint API Manager and Microsoft Azure API Management, whereas SwaggerHub is most compared with Microsoft Azure API Management, Apigee, MuleSoft Anypoint API Manager, Amazon API Gateway and RapidAPI. See our Layer7 API Management vs. SwaggerHub 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.