Apigee Reviews

We use Apigee in health care, where multiple databases and applications need API. So far, there has been no standardization, but in the near future, there will be standardization towards the FHIR, which will drive interoperability and integration.

Apigee is an easy-to-use solution.

The solution’s scalability could be improved.

Apigee is a stable solution.

The solution’s technical support is good.

It is easy to deploy Apigee from one vendor, but if you are talking about multiple APIs, then it becomes complex. Then, you have to wait for the standardization efforts.

The solution’s pricing could be more competitive.

Apigee is used by one of the largest healthcare groups, which has over 50 hospitals, and each hospital has 50 to 60 applications.

I would recommend Apigee to other users.

Overall, I rate Apigee a nine 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. 

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.

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.

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 are a solution provider and this is one of the products that we implement for our clients. We also it it ourselves.

Our use case involves accessing functions on our backend systems through a portal used on mobile devices. The app on the mobile device uses the internet portal, and we have the API as a security layer to pass the functions through to the backend.

It is very easy to implement and the configuration of the API is very simple.

It is easy to upload a Swagger file and build an API.

The user interface for building APIs is very simple. Anyone with basic knowledge can build an API.

Disaster recovery capabilities are included.

Apigee is demanding on the infrastructure so the setup cost is very high for an on-premises deployment.

We have been working with Google Apigee for almost one year.

Apigee has high availability and we have not faced any problems in regards to stability.

We have not had to scale as of yet. Our license allows for 125 million messages and we have not yet reached that stage.

We have been in contact with technical support and we are fully satisfied. I would say that they go out of their way to support us. For a priority-one issue, Google commits to having it resolved within 24 hours.

There are also community blogs where you can find other people that are working with it. These are independent sources and people where we can get information about implementation as well as customization.

A new version is released every six months and if we don't upgrade in one and a half years, the old version will be deprecated or be out of support. For example, they recently upgraded the Edge UI. The old one was not integrating with Active Directory to allow for centralized control of users. However, the new one requires authentication from ADFS before implementing it, which was a feature that was previously lacking.

The entire set of documentation is available online. You can follow it step-by-step to install the application.

We have an in-house team that handles deployment and maintenance.

It is administered by two people and we have another person to handle the analytics.

The cost of the licensing is based on the number of API calls that are made. This is good because we don't pay for the number of nodes that we are installing. They also do not charge you for non-production transactions, which is extremely good.

Everything else is included as a package. For example, ZooKeeper, Cassandra, and PostgreSQL are part of the product, so we don't need to purchase any additional licenses apart from the OS.

We had evaluated Software AG at the same time as Apigee. The initial setup cost for an on-premises deployment of Software AG is less than that of Apigee. For example, if I require four cores to operate Apigee then it would be a two-core system for Software AG.

We chose Apigee because of its high availability and disaster recovery. Google Apigee uses ZooKeeper with an unstructured Cassandra database. This is different from Software AG, which uses a structured database like Oracle. Having to purchase Oracle licenses increases the cost.

My advice for anybody who is considering Apigee is that it is has a very easy and intuitive GUI to build APIs, and I can also import Swagger files. It is built on a high availability model, so if anything goes down then another node will automatically take over. We can build an active-active across the DR site.

The primary site is active, the DR site is active, and they are synchronized. It is easy to build, customize, install, and implement.

The support is also extremely good. We get immediate responses and support is available every day of the week. Google commits on the resolution time for priority-one issues as 24 hours. No other software today can commit to resolution time. I have only seen such a service with Google Apigee.

Overall, I am satisfied with this product and it is aligned to all of my needs.

I would rate this solution a ten out of ten.

Apigee brings a lot of projects, including development projects. For example, when an oil company is swiping a card in the palm station for payment of oil. As it swipes, it hits the database, and Apigee manages the entire process with the help of dedicated proxies. Managing those proxies is very easy, and Apigee makes proxy management very simple.

We have found APA management and API health monitoring valuable.

The solution can be improved by simplifying the account creation process.

We have been using the solution for a year and a half and are currently using version eight.

The solution is stable.

The solution is scalable, and multiple users utilize it in our organization.

I rate customer service and support as six out of ten.

Neutral

We previously did not use any other solutions.

I rate the complexity of the initial setup as medium. The deployment method is based on the company's contract, and approximately ten people are required for deployment.

We have seen a return on investment.

I rate the solution a seven out of ten. The solution is good, but the account simplification process can be improved. I advise users considering this solution to go for it because it has many API management features, including the health log error-finding tool and developing a new proxy.

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.