Apigee Reviews

We are utilizing Apigee as a means to host and manage our internal APIs. This involves creating an Apigee proxy that acts as a reverse proxy and hosting it on our gateway. When external customers want to use and monetize our internal APIs, we use Apigee to host them. Additionally, for internal applications that require interaction with our existing APIs, we also host them on Apigee.

The most valuable feature of the current version of Apigee, such as Apigee Edge, is that the maintenance and scalability of the service are not our responsibility. As a SaaS platform, Google takes care of it, ensuring the system is stable. Another valuable feature is the ability to customize the platform extensively. We can add JavaScript functionality to cater to any use case that is not available out of the box.

Compared to its competitors, such as Axway AMPLIFY API Management and Layer7 API Management, Apigee could benefit from having more policies to cater to various use cases. This would reduce the need for writing custom JavaScripts. If more features come straight out of the box, we can leverage them instead of writing custom code to achieve the same functionality.

I have been using Apigee for approximately two years.

The solution is stable.

Apigee is scalable. It can handle a decent amount of traffic.

We have 15 architects and developers using this solution in my organization.

The technical support team is not good. The support is not proactive. Google is a heavyweight in the industry, its support may not be as good as that of other industry partners. It is possible that Google's market dominance may have made them complacent in terms of support.

I rate the support Apigee a seven out of ten.

Neutral

The initial setup of the solution is easy. The setup is being handled by Google, you only need to request a new setup and procure a license for the solution.  Google takes care of everything else.

The current version of Apigee is not too expensive, but we are currently in talks with Google to understand their roadmap for Apigee X. However, we anticipate that with the introduction of Apigee X, the pricing will likely increase.

When comparing this solution to others, such as Axway AMPLIFY API Management Layer7 API Management, Apigee is a more stable and mature solution. Being a SaaS platform, you do not need to worry about deployment, scalability, server performance, and other related issues. However, with the upcoming release of Apigee X, there may be some constraints applied to the current version. If you choose to continue using Apigee it is a good choice.

I rate Apigee a nine out of ten.

We use this solution when we have microservices developed in either .NET Core or microservices developed on Java Spring Boot to develop and manage those APIs. We use it fof external and internal customers.

Before using Apigee, we used to have file transfer integrations. With Apigee in place, we are directly integrating or exposing our APIs to our partners who can access our services directly in real time.

The most important feature is the security capabilities and the way it integrates very quickly with other security providers. We have integrated it with Azure and it integrates quite seamlessly. Other valuable features include the API management and monitoring.

I am still struggling to understand how we can use Apigee as a hybrid system. The pricing of this solution could also be improved as there are multiple new products coming onto the market at competitive price points. Many of our customers are trying to move away from Apigee. They are considering open source platforms like Akana, Kong, Boomi and Mulesoft. 

I have been using this solution for two years. 

This is a stable solution. 

This is a scalable solution. 

I would rate the technical support for Apigee a four and a half out of ten. 

Positive

The initial setup involves medium complexity. We have 30 people who are involved in the setup of this solution for other clients and work in different locations.

I have a team of people who complete these deployments and implementation for our customers. Maintenance of this solution is easy and does not require more than one person. 

We have experienced ROI using this solution. 

If you want to monetize and externalize your API, I would recommend Apigee as a solution.

I would rate this solution an eight out of ten. 

We decided that the Apigee would be our API management corporative, and we just use it in a cloud operation. For all the communications that we are using for the public as well as some services for third parties, we use Apigee. We also are starting to use Apigee for our services inside our cluster. There is a proxy that we use that synchronizes with Apigee and the metrics that we need to follow the use of the API management.

We use it for exposed proxies. We want Apigee to be the only reference point for our client or for the only company that communicates with us. We try not to have business logic inside Apigee since we use it like a proxy. Sometimes we use some clients or some features that have to be here, for example, captcha-ing, or something like that. However, we try to use as few of the features as possible since we want to be agnostic.

The solution offers the best API management in the world. They have a lot of features. Their capchaing is very good.

The security that you have with Apigee is very good and aligns with compliance. It’s easy to manage in the development kit or tool you have to create, and that process is very easy to create, and the metrics you can get from the traffic of Apigee are excellent as well.

The solution offers an advantage over other kinds of API management. I don't want to select one, however, as no one is not going to be your silver bullet for solving a problem. However, in terms of my favorite aspect, the capchaing is excellent due to the time of response with Apigee. It’s about one millisecond, and that time is very remarkable for a client.

It’s easy to set up.

They have all the features needed to create good API management.

It’s a stable product.

The solution can scale.

One feature they have to invest time into is the developer portal they use. They do not have a good development portal. It's not easy to use, and you can not take advantage of the developer portal. You have to start creating your own developer portal and use the old API management to publish your API market.

Technical support could be better and more local.

I’ve used the solution for three or four years.

I’ve worked with the solution for about three years, and I have not had any problems with stability. It’s reliable. There are no bugs or glitches. It doesn’t crash or freeze. It’s been great.

It's a scalable product. I don't have a problem with scaling since I contract with the service, and I don't have to worry about how they scale.

There are five of us that working on the solution currently. They are primarily architects that help with the development.

Support could be easier to deal with.

We don't use it very often. I’m not sure about the team here in Chile. They may not have the skills necessary to be highly effective. However, we use a partner that is experienced with Apigee, and they have about ten years of experience. If we dealt with Apigee, the closest person to contact is in Mexico, and it’s very difficult to get the time booked with them.

The solution is one of the most accessible API management solutions I have worked with. I work with others, and this is the easy one. The setup, therefore, is pretty straightforward and simple.

We have persons that are specialists in Apigee and are confirmed to manage the Apigee and develop it over there.

I’ve not noted any ROI while using this product.

The API management can grow well. We went to Google a few weeks ago, and they have evolved. You can contract with this service in the marketplace. When using the marketplace, you can run Apigee in your organization, which can be local and fast. You can have an amble proxy in the Kubernetes or the function to use in the local environment. Overall, they have a strong roadmap as it’s continuously easier to use and offers a good cost-benefit. Now with the management that we have, we have a SaaS, and when you have a big team, like our company, that has a development fabric, they need more accounts to see the metrics and the console of Apigee. The SaaS approach makes it all easier to manage.

I’d advise new users to get to know the tool. If you don’t, you won’t get all of the performance out of t that you could. You won’t be able to take advantage of all the features, and you can lose the governance of the Apigee proxies. It’s important in the first month and year to clear governance for the product and to learn how to use it effectively.

Overall, I would rate the solution ten out of ten.

I work for a medium to big size IT consultancy firm in Mexico, and I am in the innovation and interoperability division. Our main work here is to develop projects on interoperability platforms and KPI management, et cetera, and transition from a legacy system to micro-services. In the last year, I have worked on a project on migrating a very big telecom firm from several API gateways and API exposures to Apigee. They're centralizing all their API gateways into Apigee.

We are hoping to lay out the plan for migrating the first sprint of about 200 APIs starting in January. Originally, the plan was to start in December, but the project is so big that it was suffering from delays.

We are going to start doing the actual proxies and migration in January next year. The project consists of about 10-month long sprints. We are going to use all of next year on this first phase. During the course of the next year, we are going to lay out the plan for the next phases. At this point, the total number of APIs to be migrated to Apigee is not clear, but we're thinking that it's about 300, 400 APIs that are going to be migrated.

The solution is deployed on-premise. They're thinking that in the second phase, they're going to go hybrid to have some of the features in the public cloud and some in the proprietary. 

We are integrators.

I think the most valuable features are the security features. Of course, the user access control is the same as the security. The other very important issue is the sandboxing capability of Apigee.

The caching capabilities are somewhat limited. This is more on the developer-oriented capabilities.

At this point, we aren't sure of what else could be improved since we are migrating some pieces of code that are really legacy and really difficult to model as a standard REST API. We are not sure in which areas Apigee is going to fall short. I think that next year we will have a more clear picture of some issues that we are going to find that could be addressed by a new feature, or by enhancing some existing feature in the next versions of the tool.

I have been using Apigee for one year.

Right now, in the development area of Apigee, we have about 20 developers, architects, et cetera. We are in the process of training because our expected growth drives us to have about 100 developers by the end of next year. I think that by the end of Q1, next year, we're going to double our capacity. By mid-year, we have to have 20 more, and so on, until the end of the year. We are planning to have about 100 trained developers, or configuration experts, in Apigee.

All the infrastructure, the enablement, is being done by another company. They are in charge of all the dimensions and actually creating all the infrastructure to host the platform. I have never installed Apigee as a proprietary cloud. I have been working either on the pure cloud environment or hybrid environment. I didn't phase the deployment of the tool, just the configuration.

In Latin America, Apigee is expensive. It's not for small businesses; it's more for big businesses. That's why I was trying to compare, for example, WSO2 against other API management tools. We are trying to create an inside practice in our company to also recommend WSO2 for a mid-size or small-size company where maybe the Apigee pricing for them is too heavy.

Apigee prices are targeting medium to large companies in Mexico. In Latin America, it's basically the same.

I would rate this solution 9 out of 10. 

I think the correct roadmap should be first an approach to Google to create a partnership. Then create a team of developers and an architect, and then start adding more resources as the demand grows.

We have been using the solution for multiple customers. We performed a greenfield implementation for one of our customers in Canada. It is a complete enterprise platform. The version is Apigee X. We have also created an in-built developer portal. It is mostly used for external APIs, exposing APIs to partners and vendors.

One of our banking customers also uses Apigee. They use it more like a gateway and not like a full-fledged marketplace. We are also doing a lot of support work for one of our European customers. They have internal and external API exports on Apigee. We support the whole platform. We have done a lot of automation, built a lot of processes, and brought in governance.

The development is quite standard. The deployment can be completely automated because the solution exposes APIs. We have built a completely automated deployment cycle. It triggers validation, verification, deployment, testing, and promotion to the higher environment. It is completely done through Ansible Playbooks. Apigee also provides a few playbooks.

The solution is quite strong in security. It provides integrations, OAuth mechanisms, and token-based integrations. We have integrated some identity providers. We can customize the dashboard. The tool provides a lot of custom monitoring dashboards. We can track the API usage analytics. Apigee gives us a lot of parameters to track.

We can decide what to turn on or off and build the dashboards accordingly. We have built an analytics dashboard. We have built dashboards to see the usage trends, performance of the APIs, and degradation seen by API consumers. Monetization is a strong feature. We haven’t used it, though. The developer portal feature is very rich. We have also built a portal on Apigee using ReactJs. The developer portal is good.

Some customers are moving away from Apigee to other tools like Kong. The product’s licensing model is very expensive. Apigee is completely SaaS-hosted. We do not have control over the installation. API management solutions like Kong have a very good separation of concerns between the control and data planes. Apigee does not have such features.

I have been using the solution for more than six years.

I rate the tool’s stability an eight or nine out of ten.

I rate the tool’s scalability an eight or nine out of ten.

I rate the support a six or seven out of ten. We tried contacting support five years ago. We needed help with policies and architecture. We did not get much support. It might be because the product was still growing in Canada.

Neutral

The deployment is quite easy.

I rate the pricing a ten out of ten. The tool is extremely expensive.

We are a service provider. Our customers use Apigee. We are also partners with Google. We are SI integrators. The tool is quite stable. It has rich features. Customers prefer it if they can afford it. It is one of the best products we have. Overall, I rate the product a seven or eight out of ten.

We have hundreds of backend services, APIs, that are running. We want to protect and do analysis with calling externally, internally, and all the statistics we want to track using Apigee. That is the reason we're using the API gateway.

We have seen product improvement. Initially, we didn't use much of the analytics part. Later on, we saw that as an improvement. The rate-limiting quotas are improved as well.

The analytics feature is quite good. We can look at all the statistics, how many requests coming in, how many requests going out, what type of failures are happening, what is the performance of the APIs on those features. The solution helps us to track whenever there is an issue that comes in.

The only concern overall, with the organization, is cost-wise. I believe there is already a plan, within our organization, for moving to Azure API Management. The main reason is one of the features is a cloud-based, pay-per-use. And then, because a lot of our services are moving towards Azure, why have another network of API gateway.

The testing feature is one additional feature that I see is in APIM and it is not here. We can build our own demo web service and test your proxy. That feature has been provided in APIM, not in Apigee.

I've been using the solution almost three years now.

Overall, the solution is good.

The scalability is good. Our load has improved drastically in the last three years. The traffic has been increased, and we still see a good performance overall.

Mostly developers from different teams use it. And there are administrative teams maintaining the overall solution within the organization.

The technical support is good. As a user, we report to the admin team and they work with the consultants if they are not able to resolve the issue.

I was not involved in the initial setup, but I've been told that the onsite setup was a little complex and there were a few restrictions as well.

We see a return on investment. As of now, it's good. But overall, cost wise, it is a little higher, comparative. 

For Apigee, I think licensing is on a monthly basis. The cost increases as the usage increases. It's higher than many competitors.

Azure APIM is the one option we evaluated.

From two or three years back using it to now, it's quite fast. The performance side is good.

It's a user-friendly product, it is. You can customize all you want, and the policies and the features they have are quite easy to use. Anyone can use it, drag and drop, and it supports a lot of other languages like JavaScript, non-JS, and all. 

I would rate the solution an eight out of ten.

The bank embarked on a journey towards open banking solutions, particularly in the realm of online banking and medical services. This initiative prompted the need for a gateway solution, and after careful consideration, the bank chose Apigee as its API management platform. Since then, the collaboration with Apigee has proven beneficial, leading to ongoing improvements and learning experiences for the teams involved.

We find great value in the ability to segregate distinct projects within the system and extract security statistics. Its flexibility allows seamless management of different products, showcasing scalability to handle extensive solutions. Whether dealing with hundreds or thousands of nickel services, this configuration enables us to sustain ongoing work effectively, ensuring real and efficient management of diverse IT projects.

Our focus on improvement primarily revolves around security, differing somewhat from the Connect endpoint. We've encountered challenges in leveraging Connect functionality, prompting us to explore additional tools, such as Fergus, to address implementation and security issues.

I have been working with it for four years.

The stability issue occurred once in a real-life scenario at the bank, causing a downtime of approximately one hour, leaving the entire bank without internet access. This incident was not typical of a bank, and other companies might view it as an isolated event. Occasionally, a service may slow down due to factors like migration, causing disruptions within the timeframe of a timeout.

The system is scalable; however, achieving scalability involves updating numerous properties and parameters. While it is manageable, the learning curve proved significant, and we gained insights through collaboration with a team of three during the development process.

The initial setup is relatively complex. While it may require learning, trial, and understanding, once you reach an advanced level, it becomes a more personalized experience.

The deployment process involves sharing JSON or Slack commands, and the subsequent steps are then taken over by the company from the Apigee, initiating the process from scratch or refreshing it.

Overall, I would rate it seven out of ten.

We use Apigee every day. Because we have a backend system, we use Apigee to capture and track all of our transactions and for monitoring calls, which is the target for our client service. We then use this information to create a report and provide a price for each transaction. For this reason, we created a proxy that we use as an integration layer, like API management, which helps build applications. For that reason, each and every call goes through Apigee so that we can track and capture all of the information.

There are a few features that are quite interesting. We can provide our API developer with an API proxy to the developer portal, which comes in handy. There are also some interesting policies, like authentication where we normally provide any code and quotas and rate limit policies for protection. The administration and monitoring features are also quite useful as you can receive alerts and notifications and monitor them on a virtual dashboard. There are just a lot of security features in general.

With Apigee, we can easily monitor applications, and our core IT team informed me that installing upgrades is very simple. We also have a portal where we can share our proxies with the convenors, which is quite useful. 

When compared with other products and tools in the market like MuleSoft or other API management solutions, I see some lagging in regards to integration capacity — where we don't have all of the connectors. It's not the perfect ESB, it's only for API management solutions. For example, MuleSoft will provide you with the API management solution as well as ESB, allowing you to integrate with large, complex IT systems. So, there is some lagging there that needs to be fixed. 

The main area they should improve is the integration capability. They should have useful connectors that we can use to provide code so that we can integrate with other systems. This needs to be improved.

When compared to other products, such as MuleSoft and other tools in the market, Apigee has some lagging issues. 

Over the last three years, we haven't had any issues with the stability, both on-premise and on the cloud. It's a stable solution. We haven't experienced any error-value from the product.

Product-wise, we don't have any technical support, our IT team takes care of it. We also have a number of applications we are managing, but only two recruiters are monitoring them.

It's easy to create proxies in Apigee. Compared to other integration tools, we can quickly and easily export any APIs in Apigee, which saves us a lot of time. 

The setup was taken care of by our core IT team, I was part of the development team so all activities relating to the setup, updates, and customer service were handled by the core IT team.

We would definitely recommend Apigee. You can use Apigee to create proxies (and share API proxies with consumers), monitor calls, and provide security for particular endpoints. We have a complete telephone portal under Apigee, I would recommend it.

I would give Apigee a rating of seven or eight out of ten. The API moderation, administration monitoring, product architecture, infrastructure, and overall quality is good. The only area lagging is integration capability.