Apigee Reviews

We primarily use the solution as API Management, as both proxy and security.

The solution has improved our company's time to market. When we deploy a policy for a particular API, the creation of the policy and the gateway is significantly faster than what we were doing with our Layer 7 gateways. It's easier to develop the policy and to walk through the policy using the Apigee interface.

The ease of creating policies has been the most useful of the solution's features. It's a quick ramp-up time. It's easy for our support staff to implement the policies in the API management layer.

The company needs to better support webhooks. It used to support webhooks and their policies and they have since stopped. They had some issues in the product and they abandoned the support for them. It's not come back since. Webhooks are still used by some of our production partners. It would be nice to see the support for them come back. Right now, we have to pull the API instead of using a webhook to do the notification.

With Apigee, there are frequent updates, so they seem to have a very strong user base. 

There's a lot of users in Layer 7 too, but we've had some bad experience with support from the company. Stability-wise, it's hard to say. I don't think we've had any bugs associated with the gateway itself where the gateway has failed, but we've had support issues from Layer 7. 

In comparison, Google and Apigee have done a fantastic job supporting their product.

Scalability wise, I've heard from some customers that Apigee has some limitations on scalability, but we haven't experienced those as of yet.

As far as Layer 7 is concerned, it seems that the policies are very deterministic as to how the actual gateways function. Some of them have had a significant impact and we've had to scale up their clusters just to support a minimal load. Some are disappointed with the number of services that we have to engage for Layer 7, and the number of clusters we've had to create. We've had to create a pretty large cluster for supporting some applications.

The Layer 7 gateway's front end is for a high-end brand product. We have the largest loyalty program in Canada. Our PC Optimum program, for instance, uses our Layer 7 gateways. There are 14 million users that use the PC Optimum card that goes through those gateways.

The initial setup of Apigee is straightforward. Google/Apigee gives us all the information to support their private owned clouds. The interface is very straightforward to use as well. It's a lot easier than the Layer 7 product.

CA was overly complex in its configuration. CA also does significantly more as far as security and policies are concerned. It has developed a huge number of policies into their product. It's way more than what I would expect an API management product to be. It took us two months to set up the solution.

We basically took the policies from Layer 7 that we had previously created and we transformed them to policies for Apigee. That was fairly easy.

In terms of deployment, we haven't transformed totally from Layer 7 yet to Apigee. Our support is very low on Apigee right now. There's only one person that's working on Apigee currently. It's minimal. Accenture is handling the support, as they did for CA. We had about five people supporting the gateways on Layer 7.

For Apigee, we had the assistance of an integrator. The company was Accenture, and we have a good working relationship with them. They're currently supporting the platforms in many facets. The deployment was straightforward, so they didn't need to do too much.

There was no specialization or skill required for them for Apigee, but there was with Layer 7.

We looked at a couple of other vendors. We looked at offerings by Red Hat and some others. We basically looked at the market leaders.

From an enterprise point of view, our digital division had already migrated to GCP. GCP uses Apigee by default. They had selected Apigee initially. That was one factor in choosing Apigee over CA. Another factor is that it would support on-premises and it would support our Azure environment as well. The ease of use, creation of the policy, and the developer portal experience were all factors. The fact that developers could easily create the policies themselves without having to get our administration staff or engineers to actually create the policies was a big factor as well.

Right now, we are still in the process of testing the solution. We're using both on-premises and cloud versions.

CA has developed a sort-of enterprise service spot inside of their API management platform. It does interesting things with files, and it has a lot of security features that are not normally used in a majority of API calls. It's overkill. Its portal is very clunky and very difficult to set up. Its gateways and its policies are not straight forward either. It basically requires a three-day class to understand how to get in and add policies and it's not very simple to add policies into the CA Layer 7 gateway. Apigee does a way better job. 

CA is also owned by Broadcom now and when that transition happened, Broadcom did a lousy job of handing off support of that product. They basically fired everybody from CA. They left us without production support for a good part of a year. We've had CA for about 2 years and mostly we used the on-premises version, but we had a small amount on the cloud as well.

Because of these reasons, we're moving away from Layer 7 to Apigee.

In terms of advice to those considering using Apigee versus CA, I'd say they need to understand their use cases for APIs.

I would rate Apigee eight out of ten.

In comparison, I would rate CA five out of ten.

We primarily use the solution for API management. We use the solution with open banking, and we are managing our customer's cloud, on-premises, and Apigee environments. 

The solution is great in general. There are many categories of APIs that need to be maintained. It helps maintain and add rules to manage open banking. 

The solution is stable.

The initial setup isn't too complex.

It can expand well. Google seems to be moving into the cloud more than on-premises and the cloud makes scaling easier.

Apigee deals with APIs. However, most of our clients need more tailoring done to the solution.

Google isn't enthusiastic about supporting older versions. Google is now trying to move all of its clients to X within the cloud. However, some still want on-premises. 

I've been using the solution for about four years. I've used it for a while. 

The solution is stable. However, it depends on the release, the customer, and the sophistication of the infrastructure. 

We have had some issues with bugs in the product itself. 

The solution is scalable.

We have three banking clients on the solution. 

The amount of users depends on the customer. Some use it internally. Others expose the API to clients. Some have more than a billion APIs. Some have less. 

The technical support is not the best. It does depend on the size of the customer. Larger customers tend to get more attention. 

The ease of setup depends on the level of sophistication of the clients. It can be rather simple; however, the more complex the infrastructure, the more difficult the setup can be. 

We do both cloud and on-premises deployments. The length of deployment depends on the customer. It depends on the kind of network or the organization. It can take a few months up to a year.

We have a strong knowledge of the flow and the templates. For us, it's pretty straightforward. 

There is a team of six people that can assist with deployment and consulting with clients.

There are different models that customers can choose from. They have a subscription model. 

I'm a consultant. 

We are using a few different versions of the solution.

I'd recommend the solution to others.

It'd rate the solution eight out of ten. 

An area for improvement would be to provide more information while troubleshooting. In the next release, Apigee should allow product owners to use its tools instead of just platform engineers.

I've been using Apigee for a year.

Apigee is stable.

Apigee is scalable.

The initial setup was easy - there was an onboarding document with steps that we followed.

I would rate Apigee eight out of ten.

I use Apigee for healthcare management. 

I simply like how you can personalize your products and put them into product categories. That's what I like the most.

The analytical aspect of it could be better. I think it is fair if Apigee lets you configure some of the metrics of the key details you want to monitor in terms of analytics.

I have been using Apigee for about two years.

Apigee is a stable solution.

Apigee is a cloud solution, and it's scalable. I have about two departments using it predominantly to share staff. Because of how the company was structured, we had one for original regulations and one for Africa. The regulations in some of the African countries are not the same.

I'm satisfied with customer service. On a scale of one to five, I'll give them a five.

Before Apigee, I used G Data Software, IBM, and more.

Apigee is in the cloud, so it's more like software-as-a-service.

You do not necessarily pay for the license. The cloud solution is based more on transactions. So, you pay for it either way.

I would recommend this solution to potential users.

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

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.

My current job is to compare all the different API gateways and to create a report for management. We use this tool primarily to secure our API. We have a set of API from our four businesses and we're trying to apply these APIs to multiple applications. For example, third parties can leverage our APIs built to their own solutions and applications and we build applications on top of these APIs. I make the system available like a mobile app. Primarily the API management for the entire ecosystem of AP that we are building and the DGPS are providing, have varied capabilities across the organization. Apigee also acts as a proxy, everything is done within that. 

We also leverage the developer portal of Apigee as a main feature, which can be given to outside customers by third parties to build their own applications around our API. One of the standout features of Apigee is the different PolyPhaser functions that we use. For example, we use throttling, encryption/decryption and we also use external AP integration with PV.2 I'm a senior architect and big data engineer and we are customers of Apigee. 

I like the functionality of this solution. 

The cost of this solution could be improved and it would be better if it were on private cloud. 

The solution is stable. 

The solution is scalable. 

I'm not directly involved in the technical support aspect, but I've heard that the technical team is excellent. They provide support from the beginning until you completely run all your setups.

This solution is much easier to set up compared to any of the other API gateway solutions. There is extensive documentation available.

I would go with Apigee if you have the money. It will give you enough APIs for management. If you're looking simply for one functionality then I wouldn't recommend Apigee.

I would rate this solution an eight out of 10. 

We are resellers of Apigee and also use it internally. The most common use case is monetization for the APIs. I'm the sales manager and we are resellers of Apigee.

The ability to convert from language to language using the same tool without needing different developer teams to deploy is a valuable feature. It doesn't require a lot of skill to run Apigee and the security features are good. This is a powerful tool for API management. 

The only disadvantage with Apigee is that they lack market presence. I think they may have limited resources. IBM's strategy is stronger on the marketing level. 

I believe they're working on adding some integration features that are currently lacking. 

I've been using this solution for three years. 

The solution is very stable even in very complicated environments. 

The solution is scalable and it's great for enterprise companies.

Technical support is good. Google team has many teams can support it. And there is a lot of partners ecosystem who understand and implement and support strategy as well.

I previously worked with IBM Connect but I prefer Apigee. It provides all the features and requirements for AI management.

The initial setup is very straightforward and can be done by anyone. 

The licensing cost is very reasonable and it gives you unlimited transactions.

I would recommend testing this solution for a month or so. It's easy to implement and easy to use. I rate the solution nine out of 10 - the one point reduction is because of the marketing strategy. 

Essentially, we have our own product where we have hosted the APIs and Apigee for consumers to consume. We have an airline domain and our own product.

We provide services to our clients, who are end users.

We are experiencing issues with automation; the production in Apigee is quite time-consuming. 

The integration with serviceability also needs improvement. It gives our developers access. We have a developer who can deploy the APIs to the platform. As a result, they are encountering some difficulties in automating those processes. Stability relies on whether those issues can be addressed in any other API gateway.

I'd like to see the automation, time to release, time to market the new APIs, and pushing the APIs from one environment to another, to production, improved in the next release.

It is time-consuming; according to the information I have received, it can take up to two months for any new API to be published for production. I'm not sure what the difficulties are in between, but this is what I'm dealing with in this segment.

While I don't have the hands-on experience, in my opinion, and based on my research, it is not very user-friendly in terms of user experience, or UIUX.

I have been working with Apigee for a few years.

Apigee is quite stable.

The initial setup is complicated. There is a lot involved, and many teams are involved.

When attempting to apply a new host, they are setting up the DNS network, which takes some time.

We already have Apigee in our system, but we're trying to evaluate APM based on the differences between Apigee and APM.

Right now, I don't have any experience with Apigee. The only task I've been assigned is to evaluate the APIM. So far, I've only explored APIM. And all I'm doing is defining the features and differences between Apigee and APM.

I'm still evaluating, but in terms of overall performance and stability, it's quite good. As a result, we have not failed any of the issues in that regard.

For the technical capabilities, I would rate Apigee a seven out of ten.