Avoid at all cost.
Updated April 12, 2017
Avoid at all cost.
Score 1 out of 10
Vetted Review
Verified User
Overall Satisfaction with Apigee
We are using Apigee as an API gateway. The business decision to use Apigee was for it to manage token minting and routing requests from UIs to our APIs.
- Nothing?
- Only one user can be active in a proxy at a time
- No version control
- Prohibited from using JSON.stringify on Apigee objects (tokens)
- Debugging is difficult
- Unable to rename or delete policies without bumping revision
- Why would anyone give a js policy one name, display name something else, and script a different name?
- 'Trace' limited to only 20 transactions
- UI allows users to add target servers, but users must utilize the api to turn on SSL.
- I'm sure there's more, they just aren't coming to mind right now.
- Apigee forgets (expires?) your password at random intervals without notice. Every few weeks, or days, sometimes even three times in one day, I'll attempt to login to Apigee and my password will be 'wrong'. I've reset my password and Apigee still claims it's wrong. I've had to reset my password three times before it finally let me log back in.
- Unruly, difficult to maintain, unable to test, difficult to troubleshoot and debug. Every ticket that requires Apigee work increases stress and anxiety.
A Node server as a proxy that uses JSON Web Tokens would be more maintainable than Apigee.