Apigee Reviews

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.

We are customers of Apigee. 

This solution offers a lot of flexibility in its features. Other tools like IBM Data Power have limited capability when it comes to features like data control, VPN management and monitoring. 

I think the portal could offer a better user experience. It's functional and does what it's supposed to but it's not user friendly. I'd also like to see better routing features. Currently routing is limited and the setup is complicated. From a VPN management perspective, I think we would like to have more user training available, particularly for advanced users, without having to pay. There is generally a learning curve for advanced usage and configuration, and troubleshooting is a steeper curve. Whenever we have an issue, we're dependent on support. We'd like our personnel to be better trained by Apigee so we can handle issues in-house. 

I've been using this solution for six months. 

The solution is stable and, from an enterprise perspective, it can handle volume which is important for us. 

We have good support from Google. They provide onsite support and everything is available to us. We are happy with the support.

The initial setup is quite easy. 

I recommend this solution. Apigee offers a month free usage so you can play around and explore the product and then make a decision. We had a good opportunity to test things out before purchasing the solution. 

I rate this solution an eight out of 10. 

I'm a developer as well as an architect. We have internal clients as well as external clients. We have other teams within the enterprise that use this platform. They do development, and sometimes, we do development for them. Then we host these solutions in the same infrastructure. We also have external clients who want to integrate their applications with us.

We've been having point-to-point connections with external vendors. It has actually helped us to be able to integrate our internal applications with external vendors. It is more like a single point of entry into the enterprise. Initially, we used to have the vendor directly interact with the application owners, but now, we come in between as an integration partner for external vendors. All integration has to go through us, which makes management as well as security simpler.

We have been using Apigee mostly for proxy FGIs. We also use its security features as well as traffic control features.

In terms of the functionalities of a typical API gateway, Apigee is actually doing its job, but when it involves integration with backend applications, which some gateways have, I don't believe it has this functionality. You have to do Java or do some other low-level coding before you are able to do the integration.

Apigee has a lot of components, which means that management will be a bit difficult. It probably has ten different components, and all of these components leverage open-source utilities, such as NGINX. When those open-source vendors upgrade their utility, Apigee usually lags behind because they need to do a lot of tests and any required development in their own platform. They need to do rigorous testing to make sure that nothing breaks. Because of that, it takes them a while to upgrade whatever components have been upgraded by the open-source vendor that owns the utility. We've been chasing them for a particular upgrade for well over a year and a half, and they have not done that upgrade. It is creating a security risk for us as an enterprise, but that upgrade has not been done, even though the open-source vendor, the owner of the utility, has upgraded it a long time ago.

We've been using this solution for four years.

It has been a very stable platform. We've not really had any production issues. We've not had any issues where the production environment went down, and we were not able to use it at all. 

We've not really had so many issues. Whenever we had issues, sometimes, they responded quickly, and sometimes, it took them a while to get back to us, but it has not really affected the business because we usually have development issues or issues that don't cause an outage. 

It is not straightforward. It has multiple components, so setting it up is not straightforward, but the good thing about this is that they have automated a lot of the setup. It comes as an appliance or in RPM packages that you can install at specific locations in the operating system. So, its installation is easy because it has been automated.

Because of the multiple components it has, if you are trying to implement this in your environment, you need people who are experienced in most of these open-source utilities, such as NGINX, Drupal, OpenAL, etc. You would require someone knowledgeable in those utilities to be able to support the environment.

I would rate Apigee 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.

The solution is primarily used for managing the interactions between channels, customer experience systems, and other systems.

The API management on the solution is very good. It's likely the most valuable aspect of the solution for us.

The pricing is okay.

It is possible to scale the solution.

The solution isn't really lacking any features.

The user interface could be better. It could be easier to navigate and more user-friendly.

The pricing model could be improved. Things can get expensive for larger companies, or organizations that are growing.

The solution should offer more training to partners. It would help in the understanding of the product by quite a bit.

I've been using the solution for three or four years at this point. It's been a while.

The stability of the solution is okay. We haven't run into any issues.

Larger customers typically have 14-20 users on the product.

For large transactions, the commercial model is proving to be a constraint to some of our customers. For example, they're asking, when the scale grows, the commercial option becomes expensive. Some of our customers, for example, ask for an alternative approach due to the cost of the commercial model.

That said, you can scale. It's not a challenge in terms of doing it, it's just a challenge in terms of cost.

I've never really had to contact technical support, and therefore can't really speak to their level of assistance.

Typically, if I need assistance, I turn to Google or forums and I seek help online that way.

The initial setup is straightforward. It's not overly complex. A company shouldn't run into issues setting it up and rolling it out.

I'm part of a services organization. There are various developers, and Apigee users tend to be more than 300 people from our organization. In terms of support, there are 40 people. These are split across different customer organizations.

We are an integrator and can implement the solution for our clients.

The pricing starts off okay, however, for enterprise-level organizations, or companies that are scaling, the price can rise and become costly. If you don't scale too big, the pricing is fair.

We are systems integrators. We aren't just end-users.

In general, I would rate this solution at an eight out of ten. If the pricing in relation to scaling was better, or if they offered better partner training, I would rate them higher. There aren't really any features lacking and we're largely happy with the product.

We are working on some client POC where we have all the workloads deployed on Google Cloud. We wanted a gateway that was more like an API Management tool. We wanted to manage all our APIs centrally in one place. For example, we can route the traffic. We can limit, we can perform throttling, we can have the security checks like the authentication mechanism implemented centrally. We can also have a reverse proxy to our service endpoint.

I like implementing different policies, for example, rate-limiting policy. We can create a custom rate-limiting policy, and we can have an application-specific rate-limiting policy. That's what we're implementing or using, and I like that feature.

More documentation on the Open Banking Standard will help. For example, WSO2 supports the Open Banking API, but I can't find relevant documentation from Apigee. I'm not sure whether Apigee even supports the Open Banking Standard. If they do, then I think they have left out the documentation for that. For example, WSO2 has extensive documentation and training available to everyone. In that sense, I think, Apigee can improve.

I've been using Apigee for a few months.

It's a stable product. It's easy to manage, and we have implemented it for our production deployment.

Apigee is a scalable solution.

I never tried reaching out to tech support because the documentation is good. The documentation is available, and there is some training available on Udemy and the product site. These nicely describe how to deploy or set up different policies, which was enough for us.

The installation is straightforward. You just need to get a license for Apigee and then configure the reverse proxy. Once you have the reverse proxy configured, you have to set up whatever policies you want. One or two guys were able to install, deploy, and host our reverse proxy for our endpoint within a day.

We went through the documentation and the website and deployed the solution ourselves.

All these technologies are using Google Cloud for hosting our microservices, and we trialed Apigee. We were also using WSO2, an open-source API management tool, but as everything is on Google Cloud, we chose Apigee.

If your workload is already deployed on Google Cloud, integration is very easy. Even if your services are hosted in some other cloud, like AWS, I think you can use Apigee, but I haven't tried that approach. 

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

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.

We implement a set of microservices. We expose different APIs and control and monitor the use of the APIs by using Apigee. We have approximately 15 developers.

The central monitoring feature is the most valuable. It also provides security for the APIs and high availability for our use cases.

Apigee is the best product in the industry in comparison to other API management solutions. It helps in fast development, which is a top point. It also supports a lot of industry standards and has excellent documentation.

The developer portal's adoption of the OpenAPI standard needs to be improved. In the latest version of the developer portal, they have adopted the OpenAPI standard. This feature, however, can be improved by supporting more characteristics of the OpenAPI standard.

I have been using Apigee for approximately one year.

It is stable. I did a series of tests, and Apigee was excellent in the results.

Scalability is very good in the SaaS version. 

In general, they respond very fast and provide good service. Sometimes, they take longer to respond. It can take three to four days.

We didn't use any API management solution.

The initial setup of Apigee is very easy. However, we had a problem with the deployment of Microgateway in on-premises infrastructure. The deployment took about two to three months. 

We worked with a partner. We have three teams for deployment. Each team has five developers. These teams also do maintenance. 

We have three people for the administration task. They do monitoring and reporting.

We have a contract for three years. I don't know the cost.

We evaluated API management solutions from Oracle, IBM. Most of the solutions are similar in terms of functionality. We went for Apigee because it had more points or better ratings as per Gartner and Forrester.

I would definitely recommend this solution. It is a good solution for masking data, using methods like RPC, and administering APIs. We plan to continue using this solution. We have legacy systems in our company, and we need to move to new technologies. We plan to create developer APIs for the rest of the functionality and use Apigee for API management in our company.

I would rate Apigee a nine out of ten. It is an excellent product.