We performed a comparison between 3scale API Management 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.
"3scale API Management's best feature is API management."
"The standard deployment is very simple."
"The most valuable features are the gateway and security features."
"It's good that they aren't adding a lot of features like ESP, etc. It's okay with just being a gateway."
"The gateway is the most valuable feature because it makes it possible for us to gather all traffic into one proxy, which is a good thing."
"The product is stable."
"The solution is quite lightweight, and the installation is very easy. It's like a two-click installation."
"I like the API automation."
"The Portal API helps us with deployments. It also helps to have a catalog of everything. The replication is also a critical feature for us. It helps to have a more robust architecture and makes our systems are highly available."
"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 allows us to keep clear traceability of the changes made in each of our APIs."
"It impresses me as a product because it never goes down. It always does what it is supposed to do."
"The administration interface (Policy Manager) is very easy to understand and use."
"The actual management of APIs is fundamental to us, as we're a heavy API user/provider. So, obviously, a centralised management platform is important."
"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."
"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."
"It would be helpful to improve the customization features so that the customer can do it based on their own needs."
"The user experience could be better. The developer portal is too complex and hard to configure."
"3scale API Management only supports restful APIs and doesn't support SOAP."
"We tried to use the portal, but we decided that it wasn't enough. The content management system (CMS) is not easy to use if you want to customize things, and it's hard to get someone who has the knowledge to work with the CMS."
"What was suggested by Red Hat was a crucial part of the configuration, but when we started to ask about the supportability of this configuration, Red Hat said only some parts of the configuration would be supported."
"I believe the CMS part of it has room for improvement though. That is where you write a couple of things if you want to publish your API. It's based on liquid scripting, which doesn't seem like the obvious ones to script with."
"What I'd like to improve in 3scale API Management is its route-limiting feature. Currently, I don't know how to do that effectively on the solution, but in Kong, I know how to do it, so I would love to see route-limiting being easily done on 3scale API Management. It would also be good if there was some authentication that you could do from 3scale API Management because Kong offers that functionality out of the box. What I'd love to see in the next release of 3scale API Management is the ability to integrate more plug-ins easily onto the platform, so you'll be able to extend it, and even do customs management. If Red Hat could offer that extension where it allows the internal organization where 3scale API Management is deployed on-premise to integrate its tools on top of 3scale API Management and provide an API for that, that will make the solution very powerful."
"The product is not that flexible for developers. It's less flexible and rigid. It's not easy to make changes or customize it."
"They need a workflow for the API Developer Portal, where the process only allows requests to go to the correct person."
"Layer7 API Management could improve by assing more portal-based capabilities."
"It is not possible for clients to migrate to a newer version."
"I would like for the new release to allow us to speed up code generation. The integration with CICD could also be more seamless."
"The interface is Java which is difficult to make look very nice."
"The architecture of the solution does not allow for flexibility in using different components for the gateway architecture."
"The overall cost of Layer7 API Management is high, they can improve it by making it less expensive."
"The initial setup was very complex."
3scale API Management is ranked 11th in API Management with 10 reviews while Layer7 API Management is ranked 10th in API Management with 109 reviews. 3scale API Management is rated 7.4, while Layer7 API Management is rated 8.4. The top reviewer of 3scale API Management writes "Useful as it lets you add a backend to the product, it integrates well with clusters, and it has exceptional technical support, but route-limiting isn't easy to do on it". On the other hand, the top reviewer of Layer7 API Management writes "Has great drag-and-drop features and it requires minimal coding ". 3scale API Management is most compared with Amazon API Gateway, Kong Gateway Enterprise, Apigee, IBM API Connect and SwaggerHub, whereas Layer7 API Management is most compared with Apigee, Kong Gateway Enterprise, Amazon API Gateway, MuleSoft Anypoint API Manager and Axway AMPLIFY API Management. See our 3scale API Management 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.
