Apigee Reviews

We use the Apigee platform for analytics, specifically for retail customers. We have used this solution to enhance the capability of some of our legacy systems. We have 300 users on this platform. 

One of the best parts of this solution is the implementation as we did not need to use code or out-of-box policies. When it comes to the cloud-based architecture, there is a high level of reliability.

When it comes to the rate limit, we don't have a specific category for rate limits for a particular customer.

I have been using Apigee for more than seven years.

This is a stable solution. 

This is a scalable solution. 

The customer support for this solution is very good. We have received immediate responses from the technical team.

Neutral

The initial setup is not that straightforward. 

This solution offers annual licensing.

I would recommend this solution for API management and is one of the best on the market.

I would rate it an eight out of ten.

We have an API, which I developed using multiple languages and different applications. We have a lot of applications, and they have their individual APIs. We create a proxy for those applications in Apigee, and we expose those proxies to access those APIs.

Apigee didn't exactly improve our organization, but it fulfilled a requirement. There are a few tools in the marketplace, but we thought Apigee was the best for our use case.

Apigee is very easy to use, and you can code in any language, like JavaScript, Java, or any other language. That's really helpful. It's cloud-based, so there's no need for any installation.

Access restrictions can be improved. For example, you can't restrict access to some people or some groups. You have to give them total access. 

I've been using Apigee for about three months. 

Apigee is a stable solution.

I think it depends on your license, but it's highly scalable.

The initial setup is straightforward. We don't need a lot of training for the developers to start working, just a few days at most. It's very easy to start with, and the development effort is also a lot less.

For potential users of Apigee, I'd tell them there's a free version if they want to check it out and have a trial. 

On a scale from one to ten, I would give Apigee an eight.

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 have a legacy and non-legacy databases that are both on-premises and off-premises.

Apigee is used to connect to any Google-based applications that are available. In addition, we are experimenting and testing in other environments.

I'm a CIO in consulting.

Apigee has proven to be one of the best of the breed. Others are attempting to innovate and are succeeding. So we don't know how innovations will be distributed, Azure, Amazon. Amazon, without a doubt, is lagging, but I've recently heard in the reinventing that they're working on a lot of API-related innovations. So you can't say that they'll be lagging behind as they are catching up.

We are experiencing some performance issues. Except in terms of performance, we can't find anything that needs improvement. This is something that we are trying to understand, and we will fix it soon.

I'm dealing with the Google and Apigee teams directly, so I can't go into specifics. But I believe we will be able to fix it sooner rather than later. It will be one of the most extensive implementations. And while we did not find any performance issues during testing and development, we did find some in production. We will be in a position to fix it soon.

Our environment consists of multiple clouds. The usual question is whether you have a single environment or a multi-cloud environment. What I've answered is applicable to all multi-cloud scenarios. I haven't specifically mentioned the Apigee-related issues. In CA Cloud, that is Google, I am working in a multi-cloud environment with settings and cross-components.

More platform integration, lower prices, and improved performance are all potential improvements; however, when it comes to standardization, all of them are converging on standardization, but, my criteria are more performance-based.

Either one is focusing on the API or on alternative exchanges that can improve performance. As a result, making a choice of API and the use cases that surround it, as well as how the implementation is done for scale, can be difficult at times. When we talk about the scale, there are definitely a lot of considerations that must be understood, and one of them is performance, which is our primary focus area.

If you are going to use APIs or even exchanges, you should be more concerned with performance.

I have been dealing with Apigee for quite a long time before it was part of Google. It's been approximately three years.

The stability of Apigee is one of the best of the breed.

The scalability of Apigee is good.

Apigee will be implemented in over 100 hospitals.

We have been working closely with technical support, and everything is fine.

We are also collaborating with Amazon teams and some of the standardization committees to help standardize APIs.

The integration of Apigee was straightforward.

It is not an installation, it's an integration. Apigee is integrated rather than installed.

The number of people needed to maintain this solution is determined by the project's, and the complexity of the situation.

Apigee is subject to licensing fees.

Typically, the customer is internal, so it is accounted for in the integrated budgets.

I have other affiliations. Like, I am associated with Cloud Security Alliance, which is a nonprofit organization. And I am also part of ISO SC 38. SC38 has a PWI, a preliminary work initiative on API management. And that goes as the advisory at a global level for a standardization. This topic is not only of my interest, but it is my passion.

I would recommend this solution based on the use case they have.

I would rate Apigee a nine out of ten.

We've got quite a large technology footprint and I'm looking after the integration of our banking platform with our payment systems.

The REST API allows for faster user engagement.

The flexibility allows you to quickly run a cloud-native application architecture.

The ability to work across different management solutions in a plug and play fashion would make it easier for faster uptake.

Pricing is an area that can be improved, as it is a little on the higher side. It is more expensive when you compare to open-source products or other vendors.

I think it would be helpful if Apigee had support for voice-activated activities, rather than having to type.

More intelligence in terms of being able to learn from previous activities would be a good addition in the future.

I have been using Apigee for about two years.

Apigee is used on a daily basis in our payment systems.

It has performed relatively well from a scalability perspective.

We have about 15 users in the company. They are a mixture of engineers, architects, and administrators, with the majority being architects.

In cases where we have a problem and need support, we have an agreement in place with the vendor to help us navigate through it. They are good and respond to our issues quickly.

Apigee was our first choice for this type of product.

The initial setup is of medium complexity. End-to-end, we took about a week to get everything ready. This included the account, the proxies, the target endpoints, etc.

We received assistance from the vendor for our implementation.

Our in-house team is responsible for routine maintenance. This includes backup support, uptime support, patching, applying of certificates, etc. It is an ongoing activity and we also work with the business to continuously improve the integration, so that they are getting the value of the capability of Apigee.

My understanding is that there are costs in addition to the standard licensing fees.

My advice for anybody who is considering Apigee is to first do research and an analysis of what they want to use it for, including specific use cases. It is a good tool but it is important to have well-defined requirements to avoid a high implementation cost and rework.

The requirements have to be very well documented and understood by all parties, especially those who will be involved in implementing it. Following this approach is an important step to getting a good return on investment.

I would rate this solution an eight out of ten.

My company works mainly in the BFSI domain. The tool helps us to build, manage, and run the APIs. 

The tool is one of the earliest API management products and is good. It reduces the Time To Market aspects of products. 

I would like to see better integration and some architectural improvements in future releases of the solution. 

I have been working with the solution for more than six years. 

The product is stable and I would rate its stability a nine of ten. 

I would rate the product's scalability an eight out of ten. 

Google's tech support team is helpful in terms of knowledge transfer. 

Positive

The tool's setup is very simple. You would need around 50 people to maintain the solution. 

The tool offers good returns on investment. 

The product's pricing is fair. You need to pay additional costs for the support. 

I would rate the product an eight out of ten. 

This is our major service when we have services and need an API gateway. They allow us to expose these services to clients.

The solution offers good customization. It's very easy to customize in general. 

You can integrate with things very well. 

The caching is good.

You can add basic flows with ease. 

The Google CMS is a great tool. 

The solution is stable. 

Technical support has been decent. 

We are considering scalability regarding using a centralized environment, and the documentation seems to indicate it's not easy to integrate with Kubernetes or deploy into a cluster. 

It's not using SPA, single page applications, like Angular. 

There isn't very good monitoring right now. We need better performance monitoring.

We need it to offer better debugging, so if there is slowness in the flow, it's not easy to fix. You have to use other tools to debug.

I've used the solution for four years. 

The stability is good. I'd rate it nine out of ten. It is very reliable. There are no bugs or glitches and it doesn't crash or freeze. We've had no issues on this front. 

We have around eight people that directly work with the solution. They are four developers, two engineers, and two support staff. 

The scalability is good. I'd rate it five out of ten. It's deployed on the VM. You cannot scale up in some areas as you might hit a limit. Then, there are peak hours, and that might be different as well. You might hit a wall. 

We've dealt with technical support in the past. They've handled a few tickets. However, I have never directly dealt with them. I have not seen any complaints in regard to the service they provide. 

Positive

We did not use a different product previously. 

I didn't handle the deployment. I don't handle that aspect of the solution. 

We do have a team that manages and administers the solution. 

There might have been some assistance from the Apigee support team during implementation. 

The pricing isn't something that I deal with. I don't know the exact cost. 

We are currently looking into other solutions. We want to see how others stack up in terms of pricing, stability, scalability, et cetera. 

I am using the latest version of the solution. 

I'm not sure if I would recommend the solution to others. I still need to make comparisons between this and other options. I'm trying to decide if I should stick with Apigee or move to something else.  

So far, I'd rate the solution eight out of ten. It has a high rating on Gartner. 

We want to sell API products and if you want to market the API product that you are building, then definitely you can go for the Apigee or any API product, but if you are in Google Cloud, definitely you can go for Apigee because only Apigee offers current cloud.

The most valuable feature is the API gateway.

I have heard there maybe be some security issues that need to be addressed. If this is the situation I would encourage taking a look at the security matters.

I have been using Apigee for the past two years.

There is good stability with Apigee

Apigee is scalable and we have around one thousand customers currently.

Technical support is good with everything.

Positive

The initial setup is extremely straightforward and not complex at all.

You can do the deployment usually in one month with the documentation provided and it can be done in-house.

Apigee has several different licenses you can obtain depending on your needs.

Previously, I had used IBM Data Power.

I would rate Apigee an eight out of ten.