Apigee Reviews

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. 

Apigee is a platform for developing and managing APIs.

Overall the solution works well, it is one of the best solutions on the market. There is plenty of support documentation available.

The Apigee cloud admin UI could be more user-friendly by adding a few more features.

I have been working with Apigee for one and a half years.

The solution is highly stable.

We have built an API platform o over 2,000 different partners and all of them are using the gateways.

The technical support is very good.

The installation was not difficult.

I rate Apigee an eight out of ten.

There are plenty of use cases. My clients were using for internal API management as well as external API management, including subscription models and pre-payment models.  Essentially, it was for using internal data and selling external data.

Apigee gives you plenty of opportunities to set up your workspace depending on how you want to manage your APIs. This is something that the majority of clients like.

What my clients don't like is that the on-premises solution is not being treated and maintained as well as the cloud solution.

I know that they are working on the integration of no-code and low-code solutions to make it more accessible to users that have no technical background. This is something that I find very interesting and they should continue working on that.

I was working at a client site where Apigee was being used. I have two years of experience in this environment.

Stability-wise, I haven't observed any major issues with the product.

It is pretty scalable and we haven't reached any limits so far. We have thousands of users. There are a few hundred active internal users, a few thousand developers, and far more external users.

I haven't been involved in any interaction with support.

I would like to see the implementation of further options for billing because as it is now, the opportunities you have in terms of a package are limited. You don't have the choice of too many billing models, which is an issue that needs to be worked on.

My clients have a monthly pricing model.

If you compare this to Microsoft Azure API Management, Apigee is a bit better because Microsoft has no real built-in solution.

I would rate this solution an eight out of ten.

We are a telecom-based organization, so our use cases are generally based on telecom functionalities like the MF APIs. I'm a technical architect and we partner with Google. 

Apigee is a front-layer gateway and it helps to improve our overall performance.
We can repair requests and respond to vacant needs and that's a big help to us. 

Many of the features available are valuable to us including out-of-the-box policies, the vacant creation, throttling and more. We are using authentication and authorization which are also good features. 

Integration should be improved as we'd be able to use solutions such as NewSoft or Del Boomi. It would be helpful if Apigee would lower their licensing costs. I'd like to see a cloud-based solution and some new features similar to those available with TD cloud or Salesforce.

I've been using this solution for over six years. 

The solution is stable.

To date, our use cases have been limited so we haven't had significant scalability requirements. We have no plans for expanding the use of this product. 

On a number of occasions we've needed some immediate help or a quick turnaround, but the technical support response was quite slow. 

Neutral

Initially, we figured out how to deploy the solution on the job and it required some external assistance, but because we've been working with Apigee for so long, deployment is relatively easy for us these days and is carried out in-house. 

Apigee has so many servers nowadays that are based on requirements. Much of the information is available on Apigee documentation which is good. 

I rate this solution eight out of 10. 

I'm a part of a service provider company, and we basically provide all kinds of services for our customers. One of the areas for which we provide services is API management. We work a lot with Apigee, and we have experience and a good team working with Apigee.

In terms of use cases, we've created a good marketplace for one of the clients. They are a logistics company, and they have a lot of vendors and partners with whom they work. So, we have created a marketplace where the vendor's partners can integrate for their shipments and other things. They can integrate their applications into this marketplace.

We have also implemented developer portals where we do the onboarding of developers. They can create their code SDKs, etc.

Currently, we are at a customer site, and we are migrating the on-premise version H to Apigee X, which is the latest one.

The analytics function and the developer portal are the two valuable features of Apigee. The analytics part is very good, and the developer portal is quite rich in features.

The authentication mechanisms are quite easily built into Apigee, which is something that most of the other products have also now started supporting.

iPaaS is something that we would like to see. For example, MuleSoft is kind of an integrated platform as a service (iPaaS), and it provides a lot of out-of-the-box connectors and other such things. This is where Apigee lacks. I'm not sure if that's the roadmap for Apigee, but any improvements on those lines would be helpful where things become easier to implement.

It has been four to five years.

It is definitely stable. Performance-wise, we have not seen any major bottlenecks. What we have realized is that the performance is not just because of the tool itself. If you take any API management tool, the performance also depends on the way the integrations are done. So, if implemented correctly, performance is not really an issue.

With the SaaS model, scalability is there. 

It is suitable for large companies because it is a bit pricey. It is definitely not for small companies, but it might be suitable for medium companies.

We have not been in touch with them much because we mostly have done development, but they do provide good support. Their support during the initial design architecture phase is also very good. So, if you have bought the licenses, they do provide an architect to come in and define the whole architecture. That way, the support is good.

We work on multiple API management tools based on the requirement of a particular customer. We have worked on Apigee, Dotcom, MuleSoft, to name a few.

Managing an on-premise setup themselves can be a huge overhead for customers. Apigee, I believe, releases patches very frequently, and those upgrades and maintenance activities are quite an overhead. Having said that, it has good support. They provide a lot of scripts through which the installation and other things can be automated, but obviously, we have to tailor those to our needs. On-premise is definitely a little bit of overhead. We have to have a team to manage that, but now with Apigee X going on SaaS, most of the implementations are on SaaS. So, this overhead is minimized a lot, and you just have to do the configurations.

It is a bit on the expensive side. Its licensing cost is a bit high, and that's where we've seen people going back on their decisions.

In the latest version of Apigee, they've broadened the support for socket communication, which was previously missing in Apigee Hybrid.

I wouldn't recommend Apigee for simple situations because sometimes, it does become an overhead. It is overkill for simple situations. If you have very complex scenarios where you are trying to embark on a cloud journey and you still have systems on-premise or some systems are hosted on some other cloud and you want to do an integration, Apigee is really good. It provides support for the mesh architecture, and with that, it becomes quite easy.

The advice that we normally give is that when you are starting on an Apigee journey, you should not think of it just as an API management tool. We try to give it as an enterprise API platform that a large customer with different lines and businesses, such as a bank, would eventually leverage as a whole. You should not treat it in a way where only a particular group is using Apigee. It is an enterprise platform. So, you should treat it as a platform.

I would rate Apigee an eight out of 10.

The following features are most valuable: API Management, Analytics, Quota, and the Developer Portal.

Being an employee of a service-based company, we have implemented the product for different customers.

Role-based access management needs to be improved. It would also be nice if the solution could be integrated with code versioning systems like Git/Bitbucket.

I have used this solution for more than 2 years.

The APIGEE SaaS offering is quite stable.

I did not encounter any issues with scalability.

On scale of 1-10, I would rate technical support 8.

No, I have not used any other tools.

The on-premises setup is really complex.

As most of the customers say, the tool is a bit expensive.

I did evaluate other options.

The tool is good, easy to use, and has good customer support.

In my previous company, I used Apigee after modernization to manage client APIs.

Apigee is a great product with good feedback and recommendations from clients.

It is best to ask a developer about the areas for improvement in Apigee, as I'm a content writer, though the pricing for the product was a bit higher.

Apigee would also need developers or a dedicated team for deployment. I also found it challenging to manage sometimes.

My last project with Apigee last December.

Apigee is a stable product.

The company only used Apigee. It didn't use any other solutions.

As a writer, I didn't set up Apigee. Another team set it up.

Compared to other products, Apigee had higher pricing.

I used Apigee for my customer, but I no longer work for the company.

I'm a content writer and was involved in researching and creating documentation about Apigee for a client.

The majority of the clients had fifteen to twenty users of Apigee.

My rating for Apigee is seven out of ten.

The company was an Apigee partner.

One feature I found most valuable in Apigee is its simplicity. All features remain the same in all of the API tools, and I have experience with IBM API Connect and Apigee, but Apigee is easier to work with, plus the learning curve is not that steep.

Another thing I like about this solution is that the support is really good, and this gives Apigee advantage over other providers.

I like the development feature of Apigee. You will find it easier to work with Apigee than IBM API Connect.

We found a glitch in Apigee, and we raised it with them: It's the response overlapping from the API with high traffic.

They have been working on that, and they have shared a patch with us, but I'm not sure if that is publicly available for all users. It was made available to our organization: one single patch of Apigee.

I've been using Apigee for over two years, and I've used it in the last 12 months.

This product is is stable.

Apigee is a scalable product.

Technical support for Apigee is very good.

I used IBM API Connect, but found it easier to work with Apigee.

I evaluated IBM API Connect.

I'm both a user and an integrator of Apigee.

We have deployments both on-premises and via cloud. We use both, like Google SaaS and the on-premises solution.

We are a consultant for different organizations. Some organizations prefer on-premises deployment, with everything on their private cloud, and this means they use the older version of Apigee. Some organizations use the latest version because they're using Google SaaS directly.

My advice to people who are looking into implementing Apigee in their organization: If it fits your budget, then it is a good product. If it fits into your ecosystem, e.g. you are in that ecosystem, not in IBM or other CA-based ones, Apigee is something you can go for. It is a good platform.

I haven't worked with CA, and there are others, e.g. MuleSoft, so I can't comment on how Apigee compares with those competitors, but compared to IBM API Connect, Apigee is a good one.

I'm rating Apigee eight over ten. There's still room for improvement, so it's an eight for me.