Apigee Reviews

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 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.

Apigee is an API gateway used for API management.

The most valuable feature of Apigee is its simplicity of deploying an API and restricting access, like rate limit, with the API.

The technical support could be improved because their response time is slow.

I have been using Apigee for two and a half years.

I rate Apigee an eight out of ten for stability.

Apigee is a pretty scalable solution. Approximately ten developers use Apigee in our organization. The traffic that we have is close to 10,000 API requests a day.

I rate Apigee a nine or ten out of ten for scalability.

The solution's deployment is quick and does not take more than an hour. However, when you face challenges, the support is not very great.

On a scale from one to ten, where one is difficult, and ten is easy, I rate Apigee an eight or nine out of ten for the ease of its initial setup.

Apigee is a pretty expensive solution.

On a scale from one to ten, where one is cheap, and ten is expensive, I rate the solution's pricing an eight out of ten.

Apigee is deployed on the cloud in our organization. I would recommend the solution to other users. Our clients for Apigee are mostly medium and enterprise businesses.

Overall, 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. 

I use Apigee as it is an API gateway.

The live tracking API feature of the product is Apigee's most valuable component.

I don't see any problems in Apigee where improvements are required.

Apigee is not a solution compatible with public clouds, making it one of its shortcomings where improvements are required.

In the future releases of Apigee, I would like it to offer more cloud compatibility features.

I have been using Apigee for four to five years.

It is a stable solution.

It is a scalable solution.

Apigee's technical support is okay. My company did not have any issues with Apigee's technical support.

I rate the technical support an eight out of ten.

Positive

I haven't used any other solution before Apigee. My company chose to work with Apigee since it offered an enterprise edition, making it an easy-to-maintain solution with live tracking API features.

The product's initial setup phase was not difficult.

The solution is deployed on an on-premises model.

Apigee is a very good product since my company hasn't faced too many issues with it. The tool allows users to look into the performance metrics, dashboards, and proxy performance, which are some of the positives. On the negative side, Apigee is not a cloud-compatible tool because it serves as an API gateway and a lot of systems are connected to it, which was a bottleneck for our company to deal with since we wanted to move to the cloud.

I rate the overall product 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.

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 it for access. for example, if a third-party needs access, they can get it via Apigee.

It's good for development. 

We like that the solution offers easy integration. 

It has a good UI and is user-friendly.

The solution scales well.

It's stable. 

The solution is pretty expensive. 

I've been using the solution for around one year. I haven't used it for that long just yet.

The solution is stable and reliable. the performance is good. There are no bugs or glitches. It doesn't crash or freeze. 

The solution is quite scalable. We can expand it if we need to.

We do not have plans to increase usage at this time.

Support from Google has been good. We've had several people help us, and they have been responsive. 

Positive

The solution is mildly complex in terms of the setup process. However, it isn't too bad. 

We have five people that handle maintenance tasks. We have one manager and two developers that can support the product.

We received training from Google, which ensures we are able to deploy it properly.

The solution is expensive. You can do some negotiation which might help mitigate some costs.

We did not evaluate other products before choosing this solution. 

I'd recommend the solution to others. It is costly but good. 

I'd rate the solution eight out of ten.