Apigee Reviews

We use the solution as a platform to integrate different APIs and provide authentication, authorization, and performance security services.

The solution's most valuable feature is its ability to integrate APIs for various industrial sectors, including telecom, banks, and multinational companies.

They should improve the solution's monitoring tools for on-premises environments. Also, they should make all the essential features available for the private cloud.

I have been using the solution for more than five years.

The solution is highly scalable. I rate its scalability as a ten.

I rate the solution's initial setup process as a seven.

The solution is advanced. It works efficiently compared to other solutions, such as MuleSoft. I highly recommend it out of all the integration platforms. I rate it as an eight.

API/proxy lifecycle workflow for API providers is quite good and one of Apigee's strongest features. Also, like the completeness of the CLI and admin REST services, the Edge engine provides powerful, integrated analytics, which are noteworthy.  

Initial setup was not trivial for customer-managed topology.  Proxy versioning seems a bit confusing/buried in the publishing experience, especially for the URI-based versioning approach.

Not in production, we are still evaluating.

Nothing serious; just a bit complex.

We currently use WSO2 API Manager version 1.9x in production, but the solution is no longer meeting our needs.

If you deploy a 6-node+ topology, there are many steps required for initial setup. I feel most of this setup complexity is limited to the initial install, and the future auto-scaling of the gateway workload will be an easier/smoother experience

Setup was done by an internal team with some coaching by the vendor.

Our organization currently has twenty Apigee end-users. We use the solution for API management of financial and e-commerce domains.

Apigee is relatively easy to use for developers.

I have been using Apigee for six years.

Apigee is a stable solution.

The SaaS version of Apigee is quite scalable. The hybrid version is also scalable depending on your requirements.

I am satisfied with the support offered by Apigee.

The initial setup is not straightforward, particularly for hybrid solutions. It is easier to manage the managed services or SaaS-based versions.

The implementation takes time. The production setup includes TLS among other things, and the management and operationalizing take time as well.

We implemented the solution in-house.

Apigee's licensing costs more than other solutions. Some add-on packages are sold separately. For example, monitoring is not included in the standard package of Apigee Edge.

Anyone considering Apigee as a solution should start small and increase usage with experience. Start with a centralized small team and expand based upon the maturity model that Apigee has and recommends. I would rate this solution an eight out of ten.

We use Apigee to share open data for the government. It was a pilot project for one of the  government teams who wanted to start the journey of open data.

The capabilities are very powerful.

Support of integration is what is most challenging in Apigee, as well as the complexity of the components. When setting up an environment, you have many components with open-source content.

When there is an update on a new version or an automatic update, you have to be present and double-check that the update is reflected in the environment with no issues.

The implementation should be easier.

We implemented Apigee six months ago.

Apigee is stable. We have approximately 1,000 users.

This is a scalable solution.

Technical support is very good.

To construct the environment, can take two to three weeks.

The presentation is based on the business and can be done in three to four months.

The iicense is subscription-based.

I would recommend this solution to others who are interested in using it.

It's a very good product. I would rate Apigee a ten out of ten.

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.

It is easy to use from a developer perspective and a customer perspective. 

It is easy to set up. It is on Google Platform, and there are multiple deployment models they support, which is great.

There should be an integrated continuous integration and continuous deployment approach with Apigee. Currently, for development at a more integrated level, you have set it up yourself.

It lacks the connectors and connectivity. That's something that would be good to have. 

I have been using this solution for 10 years.

I have not faced any stability issues.

Their support is good.

For on-premise, there is complexity, but the cloud version is easy to set up.

Its price is reasonable for the features they provide and the maturity of the platform.

I would rate it a nine out of ten.

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.

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.