Apache Kafka vs Apigee Edge

• Apache Kafka is able to handle a large number of I/Os (writes) using 3-4 cheap servers.
• It scales very well over large workloads and can handle extreme-scale deployments (eg. Linkedin with 300 billion user events each day).
• The same Kafka setup can be used as a messaging bus, storage system or a log aggregator making it easy to maintain as one system feeding multiple applications.

Read full review

• 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

• Still a bit inmature, some clients have required recoding in the last few versions
• New feaures coming very fast, several upgrades a year may be required
• Not many commercial companies provide support

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

• Positive impact on ROI since now we can use one large deployment of Apache Kafka that can be used for multiple scenarios ( storage systems, log aggregate, messaging queue ).
• It is open-source so there are no licenses or subscription fees reducing the cost of deployment.
• Data can now be ingested and analyzed in real-time making it easy to fine-tune the customer experience and decision making for internal IT.

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