We performed a comparison between 3scale API Management and Apigee 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 product is stable."
"I like the API automation."
"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 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 solution is quite lightweight, and the installation is very easy. It's like a two-click installation."
"The standard deployment is very simple."
"3scale API Management's best feature is API management."
"Apigee is an easy-to-use solution."
"Apigee is a strong-featured solution. It leads in Gartner Quadrant ratings and it is a full-slated API solution that has the features that an API gateway requires."
"Highly scalable from any initial topology to horizontal extension"
"Easy interface to monetize and deliver APIs with very easy integration for third-party development environments/delivery."
"We use it to build API proxies for securing targeted back-ends with an emphasis on Continuous Integration/Continuous Development (CI/CD)."
"Apigee's best features are flexibility and breadth of capabilities."
"The following features are most valuable: API Management, Analytics, Quota, and the Developer Portal."
"It's a good return on my investment."
"3scale API Management only supports restful APIs and doesn't support SOAP."
"The user experience could be better. The developer portal is too complex and hard to configure."
"It would be helpful to improve the customization features so that the customer can do it based on their own needs."
"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."
"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."
"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."
"The product is not that flexible for developers. It's less flexible and rigid. It's not easy to make changes or customize it."
"In terms of the functionalities of a typical API gateway, Apigee is actually doing its job, but when it involves integration with backend applications, which some gateways have, I don't believe it has this functionality. You have to do Java or do some other low-level coding before you are able to do the integration. Apigee has a lot of components, which means that management will be a bit difficult. It probably has ten different components, and all of these components leverage open-source utilities, such as NGINX. When those open-source vendors upgrade their utility, Apigee usually lags behind because they need to do a lot of tests and any required development in their own platform. They need to do rigorous testing to make sure that nothing breaks. Because of that, it takes them a while to upgrade whatever components have been upgraded by the open-source vendor that owns the utility. We've been chasing them for a particular upgrade for well over a year and a half, and they have not done that upgrade. It is creating a security risk for us as an enterprise, but that upgrade has not been done, even though the open-source vendor, the owner of the utility, has upgraded it a long time ago."
"More documentation on the Open Banking Standard will help."
"There should be an integrated continuous integration and continuous deployment approach with Apigee. Currently, for development at a more integrated level, you have set it up yourself."
"Areas like traffic handling of incoming requests, security features between third-parties and Apigee, and between Apigee and internal network servers, resources, or JSON areas, etc."
"We are experiencing some performance issues."
"We do not have control over the installation."
"I would recommend this solution to those who want to start using it, but it depends on the requirements and automation."
"Since it is based on various open sourced projects, we might have to depend on the fixes provided by those components rather than Apigee directly fixing the issues."
3scale API Management is ranked 14th in API Management with 10 reviews while Apigee is ranked 2nd in API Management with 82 reviews. 3scale API Management is rated 7.4, while Apigee is rated 8.2. 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 Apigee writes "Has a robust community and outstanding performance". 3scale API Management is most compared with Amazon API Gateway, Kong Gateway Enterprise, IBM API Connect, Microsoft Azure API Management and WSO2 API Manager, whereas Apigee is most compared with Microsoft Azure API Management, IBM API Connect, WSO2 API Manager, Amazon API Gateway and SwaggerHub. See our 3scale API Management vs. Apigee 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.
Apigee for sure. Not only do you get the benefit of hybrid and on-prem deployments. As a gov entity, you will face those challenges. Over time you might want to use AWS/Azure clouds so you can migrate it accordingly or just use the PAYG on GCP with all the security Bells and Whistles. https://www.gartner.com/review...
I will choose MuleSoft due to its ease of use, integration extendibility, and product roadmap.
MuleSoft API Management is better because of the following reasons:
* Ease of initial setup & configuration
* Most robust features in API management: oath, throttling, and access levels can be done very easily.
* MuleSoft API-led connectivity & Integration solution (you can extend the API management solution with a flexible integration option). You can very easily extend APIM to integration.
* Very Clear Product roadmap including APIM, RPA and multi-cloud implementation.
The cost of both MuleSoft APIM & APIGEE is similar.
Compared to 3scale, Apigee API Management has a better API gateway for security and traffic management.
Apigee is better for API policy enablement compared to 3scale API Management. Apigee provides better support for GraphQL, OData, OAS2.