Apigee Edge vs Layer7 API Management (formerly CA API Management)

• Manage user access, we can allow specific access to users based on their need and even customize requests of services based on user requirements.
• Allow branding, so that SFO can maintain its look and feel but still get the support and functionalities we need from Apigee.
• Integrates well with other platforms we use.

Read full review

• SOAP to Rest / Rest to SOAP web services transformation.
• Secure authorization and authetication (JWT, OpenIP Connect, OAuth, SAML and more). WASP Features as injection protection.
• Easy rule writing without coding.

Read full review

• 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.

Read full review

• It would be nice to have an integration with services like Github for managing projects and versions.

Read full review

• Unruly, difficult to maintain, unable to test, difficult to troubleshoot and debug. Every ticket that requires Apigee work increases stress and anxiety.

Read full review

• Very fast implementation and is easy to learn & use.

Read full review