What do you like best?
I like the way Apigee Edge handles the creation and editing of API proxies. The mechanisms they use for tracing traffic through those proxies is clear and understandable to most people who already know how to run a website.
I like the mechanisms that Apigee provides to throttle APIs (SpikeArrest and respond with the same results to multiple queries for the same information (Caching when the same response is appropriate.
I think most of the User Interface is as visual as it can be. There are certain aspects of the features that require a few lines of code, but their transaction maps are diagrams.
What do you dislike?
The some of the API Analytics charts look too much like Google Analytics for my taste. Without training from Apigee, I can see that some devops people would gloss over the information that Apigee's API Analytics provides.
Recommendations to others considering the product
Get a full hands-on demo of the platform and let your developers and devops people work through some of the examples that Apigee has created to illustrate the tent pole features.
What business problems are you solving with the product? What benefits have you realized?
I am migrating a legacy LAMP stack application to Apigee Edge and Apigee's implementation of Usergrid (which Apigee calls API BaaS. The SpikeArrest and caching functions of Edge would take person-years to develop independently, so these features are absolutely worth the fees that customers pay to use the service.