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.  

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.

Our primary use case is for building an open API platform for a financial services company, and we needed something that could do the task quickly.

The most valuable features are low-code play, quick packaging, and production.

I would like to see the support improved. I think the time frame should be shorter for responses when it comes to technical support. This is not the ideal situation you want to be in when you need support.

I have been using Apigee for the past four years.

The stability is definitely close to a ten on a scale of one to ten.

On a scale of one to ten, I would rate the scalability around an eight. We currently have around twenty users implementing the solution on a regular basis.

When it comes to customer support I would rate them a six and a half because of the response time and prioritization. This prioritization factor is most likely due to geography.

We were using API Connect from IBM before switching to Apigee for better user readiness options.

The initial setup took a few weeks.  This was primarily because of us. It took us a while because of internal approvals. The team I was working with just was not fast enough.

When it comes to the return on investment it is pretty good. There is value for money when it comes to engaging external partners and collaborators. The initial cost is one tends to recover quickly with the right business case.

Apigee is expensive and not cost-effective. On a scale of one to ten, I would rate it an eight for the high cost. The changes individuals need to make on their side are costly.

Your team should be familiar with the product before you jump into it. There is training involved for the team, and before deploying and starting to use it, the team should get adequate training. On a scale of one to ten, I would rate Apigee an 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.

I use Apigee to design the proxy and rebuild the pilot, which becomes the API developer's design. This saves time and money for the customer and Rapid7 and 8 by simplifying the process of synchronizing and obtaining actual IDs. 

Apigee is the tool we use to test the API.

Apigee provides good documentation.

The pricing is reasonable.

Apigee's certification is beneficial.

I like the customized tools included with Aigee such as CI/CD.

Apigee integrates well with Kubernetes, Atos, Jira, Microsoft Teams, as well as ServiceNow.

I'm not a fan of the developer portal. It should be simplified. There is an excessive amount of customization required. 

When compared to Azure, Azure is more user-friendly to customers.

Monitoring could be improved. Google Cloud provided better monitoring than Apigee. 

I still prefer monitoring in Azure or Anypoint MuleSoft.

It also requires additional tools to assist in the deployment of Apigee.

I would like to see the monitoring, dashboards, and reports improve.

I have been using Apigee for five years.

I am working with version 8.

Apigee is a stable solution.

Apigee is a scalable solution.

Technical support is very good.

They resolve issues quickly.

I have experience with many different platforms such as Mulesoft and Microsoft API Management.

In Azure, I use Azure DevOps and with Mulesoft I use Jira.

In my previous location, I partnered with Microsoft using Azure in API Management.

The initial setup was straightforward, however, when compared to MuleSoft, MuleSoft was easier.

QMance, C1/CD, GitHub, GitLab, and Jenkins were among the applications we used to manage Apigee deployment.

We completed the deployment ourselves.

The north direction used in SolarWinds and MuleSoft is the same as the north direction used in Azure and Azure DevOps for solution and system deployment.

From my perspective, Azure and Azure DevOps are the appropriate solution and system deployment tools.

I like the deployment and customization in Apigee.

The deployment process is a  scheduled tool on the file. In my opinion, testing the tool is important during the development process. However, in Azure, I haven't seen any tool testing. Therefore, I need to test the tools for the testing and deployment process. In IT, I require sales tools to test the APIs.

it is necessary to have two forms for testing, and I see the testing tool in MuleSoft, but in Azure, I haven't seen any testing tool. I need to test the tools for the testing and deployment process.

In IT, I need the sales tools to test the APIs.

Licensing fees are paid on a monthly basis.

The prices are comparable. It is comparable to MuleSoft, WhiteCloud, and other similar applications.

Apigee X improves the connection series by solving a different problem for me. It refers to service connections.

Apigee is something I would suggest to others. It has good documentation, is simple to install, has great support, and is a good testing tool.

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

I am API architect. We are service providers and provide API solutions to our customers.

Apigee provides out-of-the-box policies, so it is ready to use with minimal configuration to those policies. You can govern your API and manage the life cycle of the API completely with the Apigee tool.

You can use the documentation through the API portal and integrate it with the open API specification, and then design and create your API process.

When we compare Apigee with Mulesoft, we find that Mulesoft provides many out-of-box connectors to your legacy applications and it is now part of Salesforce. It was acquired by Salesforce. It has hundreds of soft connectors available and an exchange place where you can put your reusable assets. A similar kind of thing is available in Apigee as well, where developers start putting their assets which can be reused.

Right now we can create custom policies using Java scripts and other supported languages. That's the good thing. But if you are supposed to have created some APIs that are available on the market as public, it would be good if you can share it. It would give a bit more flexibility and then connect configurations that you can do on your own which are not supported by APIs.

From a connector perspective, it would be good if it could allow you to create a custom connector, or it could provide out-of-box connectors, or some in the backend. That would be great.

I have been working with Apigee almost five years.

Apigee is an excellent product.

The scalability depends on your configuration. You can make it scalable.

Other vendors are basically giving more. For example, Azure. Azure is cloud-based, so they offer many things, including client support and hosting. So if you take Azure for all your storage and hosting, then they are inclined to use their API data solution. Similarly, MuleSoft provides you many things. It is an ESB kind of service broker, so you can connect to many varieties of backends. It supports that, so they can use Mulesoft API. Apigee provides a number of out-of-the-box policies and it handles the API governance. But if are looking for an end-to-end solution, Apigee is a bit behind. But if it is combined together with Google Cloud, and if the Google cloud offerings are comparable to Azure, then probably Apigee will lead.

Technical support is very good. In my previous company we had on-premise Apigee installed. For that we reached out to customer support. It was excellent. And while deploying it to our customer side, we reach out to them, for both Mulesoft and Apigee. And it has a very good community portal. Customers have shared their experiences troubleshooting - their challenges, issues, and resolutions. It was good.

We have used Mule API, Mule API Gateway, and API Manager.

The initial setup is pretty simple.

It provides some sort of integral service communication support. We have a multiple API proxy with multiple APIs currently deployed. So if API A is calling API B, and API B is calling API C, if that left to right communication is also available in API B, for that we have to use some kind of service tool. That is also available inside Apigee.

Apigee is more of an entry level solution that does basic things pretty well, but if you want to go more customizable, you want to really look for another solution.

My general advice is, suppose you have minimal organizational and transformation requirements, and you have an all HCTP backend with no processing required, then definitely you should go for Apigee, because Apigee provides all those things out of the box. It can protect your backend from any penetration threat and you can integrate it with your identity provider for security. All those things are provided by Apigee. Suppose you have very, very little request response, it does not require much transformation. In that case, you can use Apigee. But if it requires a huge transformation and lots of calculations and business logic is involved, in that case, you have to go for where you can write your custom logic, so for that you should go for a Mulesoft kind of solution.

On a scale of one to ten, I would give Apigee an eight.