Apigee Reviews

Primarily we do the Apigee implementations for the customer. We are more like a service company. We sell the product and consult with the clients about their needs. There are options for the API gateways and we look at the client's requirements, their budgeting, and then we deliver and install the new solution.  

Apigee makes it nice and easy for the clients and those using the product to access the product's help resources.  

It would help with Apigee if we could make a list of our assets. If the client knows more about all the extensions they can use to work with through the Google cloud and we have an extensions database it would be easier to let them know what is available and we could do more to recommend Apigee for all different kinds of customer needs.  

I have been working with Apigee at this company for the past three years.  

The stability of the product is not an issue.  

We have not had any issues with the product scalability.  

We are actually partners with Google, so we get the best support from them.  

I did have some previous experience with other products in this category before Apigee, like MuleSoft. The main differences between Apigee and MuleSoft are that Apigee is more lightweight and the licensing is also lesser than the MuleSoft. Based on the use case of big clients, the ones who want more services can get them and because the Apigee solution is more lightweight it offers more possibilities for them to use API solutions.  

With Apigee you can bring in some adapters to work with things like business rule engines. So those might create more standardization and help make the investment in Apigee more valuable.  

I tried to do the initial installation and setup a couple of times. It is straight forward and easy. It is just done by calling a couple of CMA (Connection Manager Agent) commands and you can get it up and running.  

What I would recommend for clients who are considering this type of solution depends on the customer's use cases. Since we are Google partners we generally go with Apigee as the solution. But if the client insists that there has to be a lot of orchestration and other integrations need to be done, then we will go with MuleSoft.  

On a scale from one to ten where one is the worst and ten is the best, I would rate Apigee as somewhere around an eight.  

We are a solution provider and Apigee is one of the API management products that we implement for our customers. Most of our clients want to expose their APIs to their consumers and they need to have a generic infrastructure for it. At the same time, they want it to be scalable as well as highly secure.

We have been able to fulfill all of our use cases with Apigee.

Tracing in Apigee is a very good feature.

The scalability and performance are both very good.

As it is now, the rotation of certificates is a manual task and is something that can be improved. It only has to be done once every two or three years, but I would state that there is still room for improvement.

We have been working with Apigee for five years.

The last time we had a disturbance was a year and a half ago, and it was due to an AWS infrastructure failure. Apigee was not to blame for it. For the most part, it has a very high availability.

We have some very large customers that make a billion API calls a month and we have never heard any complaints about scalability. It's not an issue.

About half of our clients are mid-sized companies, with approximately 5,000 employees, whereas the other half is made up of companies that are bigger than that. 

We have engaged multiple times with Google's technical support. I can't say that they're necessarily very quick in their response. It can take a couple of days. That said, they're very knowledgeable and to the point. In the five years that we have been working with them, we have built a big network with them.

We use several similar solutions including Mulesoft, SAP, and Azure. Mulesoft is the one that we use the least and try to replace it with other systems. Out of ten customers, we have two using Azure, six using Apigee, and the final two using SAP.

The initial setup is very straightforward and we perform it as a service for our clients. Normally, it takes us about a week to get it fully operational with all of the rules in place, and fully onboarded.

When it comes to deployment, we have variety with our customers. 60% of them will use a cloud-based deployment, while the remaining 40% work on-premises. We are now just engaging the first customers using the new hybrid model from Apigee.

We perform the deployment and maintenance of Apigee for our clients.

My advice for anybody who is implementing Apigee is to use it as an API platform, and not as a full-stack integration platform.

I would rate this solution a nine out of ten.

This solution provides us with a good gateway for API Management and versioning. It gives us easy to map backend version services, and additional security and policies can be adopted.

We are achieving five thousand TPS (Throughput per second) on peak load, and managing thousands of proxies against K8s cluster services.

I have found the most valuable features to be tracing a proxy, and managing proxy versions and revisions via the Edge UI component.

Drag and drop of features would be more beneficial, rather than manually working on the configuration and updates.

We use this product for exposing API's to the digital platform and for B2B.

I think it is the most functional tool on the market. The security is a valuable feature. 

Apigee on premise is quite complex and it is always moving faster. I would advise anyone who is interested, to use the SaaS implementation.

I have not encountered instability with the product. 

I do not have experience with tech support. 

API gateway tool and management of API solutions. This tool is extremely helpful for discovery, self-service of API solutions.

• Allowed us to convert from SOAP to RESTful patterns
• Improved security/throughput/management
• Throttling is also useful as well as management console tools to track performance.

• API gateway tool
• API developer tool
• Visualization tools to measure and manage the performance of APIs. 

I would like to see a long-term direction for the overall architecture (similar to what WSO2 has done), in that all three areas — pub/sub, events, and APIs — are treated as part of a continuum, instead of treating each as separate topics.

We use it to build API proxies for securing targeted back-ends with an emphasis on Continuous Integration/Continuous Development (CI/CD).

It has been a potential source of mission-critical customers.

We expect to gain new business opportunities upon providing Apigee services to customers.

• Pragmatic RESTful
• Developer portals
• Continuous Integration/Continuous Development
  
• Tracing tool

I would like them to add features, such as caching and mediation policies.

It is a platform for the publication of API services, access control, limiting the use of resources, and monitoring consumption.

• Identifies services which are most consumed.
• Identifies possible risks.
• Improves productivity.
• Accelerates development and deployment processes.

• Developer portal 
• Apigee Sense
• Analytics
• Microgateway
  

• Predictive analysis of consumption
• Identification of attacks
• Identification of operational errors
  

Ease of use during development, deployment, discovery, and usage of Developer portal.

A mature end-to-end model for API distribution and revenue earned through monetization.

One unified solution for different LOBs. Easy interface to monetize and deliver APIs with very easy integration for third-party development environments/delivery.

• Flexible setup
• Pricing and license cost for end-user delivery/ distribution model
• Both on-premise and cloud deployment models are available.
• Highly scalable from any initial topology to horizontal extension.

Technical support model for OPDK should be more exposed and mature in terms of providing support during installation, run, and debug of Apigee in production on OPDK mode.