Apigee Reviews

It is a Google cloud solution for API management and analytics.  

I have not had the opportunity to completely explore the product's capabilities in the time that we have been using it. But I can say that the customization is really vast and it is a really good feature built into the product. I can customize different authentication methods and methods for authorization. I can also use redaction. So security is flexible to our needs and it works well.  

It is a user-friendly solution, but it would help if Google could provide a container-based solution instead of just a standalone one. With a container-based deployment and support for Terraform, it would be better for our deployments and that would be great. Right now we have to configure different areas manually. Some areas can be automated, but the deployments are not as fully automated as they could be otherwise. 

so, they currently have a software as a service offering or a standalone offering. I want to see something like a hybrid cloud deployment. I also want to see a private cloud deployment. 

We are still building out the environment. We are running four environments until we accept that it is fully tested. So we are not live yet and we will really go live and into production sometime in the first quarter of next year. But we have been using Apigee within the last 12 months for testing purposes.  

The scalability of the product is good. Our use case is right now is applied in only one environment. When we are about to go to production, we will probably do high-availability testing with a dual environment so we can come up with any potential scalability issues. But for now, we have not really touched that area in our testing.  

We do have a lot of people using Apigee already. This is the primary gateway for us to talk to external applications. I would say that services around 800- 900 applications which are using the gateways. That is also involving many teams and end-users who access those applications.  

My recommendation for installations is that the product installation, set up and delivery process could be improved. It is straightforward in the initial steps. The part which is automated by Google is very straightforward. The remaining part, we have to do manually. The remaining components have to be manually configured. If Google were to do a container offering of this solution, then adopting it would be seamless because everything would be able to be automated.  

I would say that it currently takes too long to set up and deploy and that it is not as short a time to complete the process as it should be. It is more mediocre, somewhere in the middle, and has moderate difficulty instead of being seamless and simple.  

We did not have to use an integrator, reseller, or a consultant for deployment. It was all done in house by our own teams.  

We tried Axway API gateway and we also tried MuleSoft. We found that these solutions did not fit our scenario as well as Apigee because our scenario is a very special scenario where we want to keep everything that we already have on board. In our current situation, we have big AWS (Amazon Web Services) accounts and a big AWS footprint. So we want to also be able to use AWS for Apigee hosting. That is where our environment and needs become a little bit of a custom scenario. Apigee works for us in this scenario and that is why we ultimately went with Apigee over other products.  

I would definitely recommend this product over any other products available in the market in this category. It has all the features necessary to work in anything from a basic scenario to advanced applications. So I find that everything in it is flexible and available in this one product. Because of that I highly recommend it to anyone.  

On a scale of one to ten (where one is the worst and ten is the best), I would rate Apigee around an eight out-of-ten.  

Our primary use case for Apigee is as an API management tool. Our client has a fast platform and they want to go to the next level when it comes to customization. As they are looking to go beyond minimalistic customization, they need multiple versions of servers and several APIs. This was a challenge we solved with Apigee.

The features I found most valuable are how the APIs are published, the whole process of finalizing the API, and then controlling it.

I'd like this solution to improve on releasing new features; I'd like it to be more frequent.

In my opinion, I think that they should start thinking about improving the solution so that they can compete with open source. You get the support in the paid version, but open source features are being introduced much faster than Apigee's. New open source features come out every week. 

I have been working with the Apigee solution for about eight months. 

My impression is that the stability of this solution is good. It's easy to use and stable. The releases take a long time. They do proper testing and introductions. But, when it comes to open source, they keep giving you more features.

I would rate the technical support of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

Positive

My impression is that the initial setup is seamless. The deployment was done pretty quickly. Our model of deployment is the cloud, more specifically, AWS.

I think that the deployment and maintenance are done by a team of DevOps of six people.

Apigee as a management tool is essential and critical. There is no question when it comes to ROI because this is a mandatory spend from either a policy perspective or an invoicing perspective. When it comes to smaller companies, the pricing might be a bit of a concern.

The smaller companies have a more innovative pricing model, which is why I recommend Apigee when it comes to price. We have a monthly license. I usually work on onboarding the solution for a client for about six months and then I hand it over to them.

We currently have only one customer with Apigee.

I would rate this solution as a whole an eight, on a scale from one to 10, with one being the worst and 10 being the best.

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.

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. 

It's deployed on the cloud. There are a few hundred people in my organization who use this solution. 

It's easy to use and the security features are valuable.

I have used this solution for about three years.

It's a stable solution.

It's scalable. You can onboard multiple partners.

Setup isn't very complex.

My clients pay for a license.

We also use Amazon.

I would rate this solution as eight out of ten.

I would recommend this solution to those who want to start using it, but it depends on the requirements and automation.

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.

We have a legacy and non-legacy databases that are both on-premises and off-premises.

Apigee is used to connect to any Google-based applications that are available. In addition, we are experimenting and testing in other environments.

I'm a CIO in consulting.

Apigee has proven to be one of the best of the breed. Others are attempting to innovate and are succeeding. So we don't know how innovations will be distributed, Azure, Amazon. Amazon, without a doubt, is lagging, but I've recently heard in the reinventing that they're working on a lot of API-related innovations. So you can't say that they'll be lagging behind as they are catching up.

We are experiencing some performance issues. Except in terms of performance, we can't find anything that needs improvement. This is something that we are trying to understand, and we will fix it soon.

I'm dealing with the Google and Apigee teams directly, so I can't go into specifics. But I believe we will be able to fix it sooner rather than later. It will be one of the most extensive implementations. And while we did not find any performance issues during testing and development, we did find some in production. We will be in a position to fix it soon.

Our environment consists of multiple clouds. The usual question is whether you have a single environment or a multi-cloud environment. What I've answered is applicable to all multi-cloud scenarios. I haven't specifically mentioned the Apigee-related issues. In CA Cloud, that is Google, I am working in a multi-cloud environment with settings and cross-components.

More platform integration, lower prices, and improved performance are all potential improvements; however, when it comes to standardization, all of them are converging on standardization, but, my criteria are more performance-based.

Either one is focusing on the API or on alternative exchanges that can improve performance. As a result, making a choice of API and the use cases that surround it, as well as how the implementation is done for scale, can be difficult at times. When we talk about the scale, there are definitely a lot of considerations that must be understood, and one of them is performance, which is our primary focus area.

If you are going to use APIs or even exchanges, you should be more concerned with performance.

I have been dealing with Apigee for quite a long time before it was part of Google. It's been approximately three years.

The stability of Apigee is one of the best of the breed.

The scalability of Apigee is good.

Apigee will be implemented in over 100 hospitals.

We have been working closely with technical support, and everything is fine.

We are also collaborating with Amazon teams and some of the standardization committees to help standardize APIs.

The integration of Apigee was straightforward.

It is not an installation, it's an integration. Apigee is integrated rather than installed.

The number of people needed to maintain this solution is determined by the project's, and the complexity of the situation.

Apigee is subject to licensing fees.

Typically, the customer is internal, so it is accounted for in the integrated budgets.

I have other affiliations. Like, I am associated with Cloud Security Alliance, which is a nonprofit organization. And I am also part of ISO SC 38. SC38 has a PWI, a preliminary work initiative on API management. And that goes as the advisory at a global level for a standardization. This topic is not only of my interest, but it is my passion.

I would recommend this solution based on the use case they have.

I would rate Apigee a nine out of ten.