Apigee Reviews

One of our use cases for Apigee was when we were exposing a legacy application that we were using in the past.

As of now, we have not found anything major that needs improvement. It is not something that we are heavily using, it's something that is still in the process of being adopted company wide.

Maybe securing the APIs could be a little bit more straightforward. There might be some room for improvement in the process of securing the applications that we're exposing through the API. We would like additional documentation on this or some examples of how to do it. Overall, we have had to invest more time than expected to do that setup.

It would be good if the Apigee management allowed us to be able to consolidate many operations into a single one for the gateway functionality.

It has been two years that I am using Apigee.

It is stable.

It is scalable.

We have around four users.

There is a team of less than five people for deployment and maintenance.

As of now, we are going through a consolidation process within the company. Oliver Weyman is part of a larger group of companies. We are among the first ones to use it, but the plans for it are still not outlined for the next year, at least. This is something that we will finish figuring out within the next few quarters.

Support is good.

At the beginning the initial setup was very straightforward, but the fine tuning during the setup is something that needs some improvement. The initial setup was pretty straightforward because we were trying not to do very complicated things. The initial setup was easy. But then as we started to grow, we realized that there was some room for improvement, but overall the initial setup was easy and we liked that.

Since it initially started as a POC and then we started moving forward from there, it was not complicated. But had we started with a real life application or with more complex applications or requirements, it probably would have been more difficult for us. But the way that we decided to start and also because of the complexity level, it allowed us to go very smoothly with the first setup and deployment.

The implementation was all internal.

Normally the company tends to do agreements with the vendors, where we are trying to get everything in one single license so as not to add complexity to the licensing. That's what I recommend.

The company started evaluating solutions and we found that we have three other options. One of them was Mashery, the other one I don't remember the name, and the last one was SAP. The company decided to go for Apigee and now there are no plans to go to something else because the process that we take to evaluate and assess the solution is a very thorough process. We try to spend as much time as possible evaluating the pros and cons of the solutions and what issues might come up.

My advice to anyone considering Apigee is to start small and then grow from there. Try not to start migrating big, meaning to consolidate many applications into one single one. I would say to start small and try to run some POCs to make sure that they understand the fine tuning. Because the initial setup was easy but the one thing that needs time is the fine tuning of the setup. That, as I said before, is something that is really important for security. The security is something that I would recommend people look at.

On a scale of one to ten, I would give Apigee a nine out of 10.

We've got quite a large technology footprint and I'm looking after the integration of our banking platform with our payment systems.

The REST API allows for faster user engagement.

The flexibility allows you to quickly run a cloud-native application architecture.

The ability to work across different management solutions in a plug and play fashion would make it easier for faster uptake.

Pricing is an area that can be improved, as it is a little on the higher side. It is more expensive when you compare to open-source products or other vendors.

I think it would be helpful if Apigee had support for voice-activated activities, rather than having to type.

More intelligence in terms of being able to learn from previous activities would be a good addition in the future.

I have been using Apigee for about two years.

Apigee is used on a daily basis in our payment systems.

It has performed relatively well from a scalability perspective.

We have about 15 users in the company. They are a mixture of engineers, architects, and administrators, with the majority being architects.

In cases where we have a problem and need support, we have an agreement in place with the vendor to help us navigate through it. They are good and respond to our issues quickly.

Apigee was our first choice for this type of product.

The initial setup is of medium complexity. End-to-end, we took about a week to get everything ready. This included the account, the proxies, the target endpoints, etc.

We received assistance from the vendor for our implementation.

Our in-house team is responsible for routine maintenance. This includes backup support, uptime support, patching, applying of certificates, etc. It is an ongoing activity and we also work with the business to continuously improve the integration, so that they are getting the value of the capability of Apigee.

My understanding is that there are costs in addition to the standard licensing fees.

My advice for anybody who is considering Apigee is to first do research and an analysis of what they want to use it for, including specific use cases. It is a good tool but it is important to have well-defined requirements to avoid a high implementation cost and rework.

The requirements have to be very well documented and understood by all parties, especially those who will be involved in implementing it. Following this approach is an important step to getting a good return on investment.

I would rate this solution an eight out of ten.

I mainly use Apigee to allow partner applications to consume services outside their organizations, for security, and for creating API proxies.

Apigee's best features are flexibility and breadth of capabilities.

I've been using Apigee for three to four years.

Apigee is stable.

Apigee's scalability is one of its main advantages.

Apigee's technical support is really good, and they have a community forum where we can ask questions and get help.

We previously used WSO2.

The initial setup for the on-prem solution is a little complex, but the hybrid setup is very easy because detailed steps are provided. The hybrid version takes one or two days to install, but the on-prem version takes a minimum of a week.

For on-premises, a consultant is required to install.

Apigee is a good product, and I would recommend it to others. I would rate Apigee eight out of ten.

I use it at home to scan my local drive for malware or viruses. 

I like Apigee's automatic plates.

Apigee's user interface could be more straightforward and have more options. Also, it would be nice if it were ready to work out of the box without so much configuration. Regarding features I'd like to see, they could add self-recovery from the last hour, the last day, etc.

I've used Apigee for around five years.

The stability and performance are both pretty good. However, I have an FFD disc, so I don't see the scans anymore. They're all done overnight.

The version I'm using isn't scalable. It's not the professional version. 

I have never called Apigee support. I haven't had any issues.

Installing Apigee is very simple and only takes two or three minutes.

The home version is completely free.

I rate Apigee seven out of 10. It's a good tool, but not a fantastic tool. I use it because it's simple, it automatically updates, and It hasn't given me any issues. 

We just started with the solution and are learning about its functionality and use cases right now. It's a requirement in our company that we have a tool of this nature.

There is less CLI needed compared to other options. It's more user-friendly and easier to navigate. 

Everything is working well. We haven't had issues. 

The solution is stable and reliable. 

I don't have any notes for improvement. I don't need any extra features. 

I just began using the solution. 

The solution has been stable. We haven't had issues since we started using it. There are no bugs or glitches and it doesn't crash or freeze. 

We are using the latest version of the solution. We're new to the product. I'm not sure which deployment we are using. 

I'm a customer and end-user. I'd recommend it to others. So far, using it has been very helpful.

I'd rate the solution eight out of ten.

We are customers of Apigee. 

This solution offers a lot of flexibility in its features. Other tools like IBM Data Power have limited capability when it comes to features like data control, VPN management and monitoring. 

I think the portal could offer a better user experience. It's functional and does what it's supposed to but it's not user friendly. I'd also like to see better routing features. Currently routing is limited and the setup is complicated. From a VPN management perspective, I think we would like to have more user training available, particularly for advanced users, without having to pay. There is generally a learning curve for advanced usage and configuration, and troubleshooting is a steeper curve. Whenever we have an issue, we're dependent on support. We'd like our personnel to be better trained by Apigee so we can handle issues in-house. 

I've been using this solution for six months. 

The solution is stable and, from an enterprise perspective, it can handle volume which is important for us. 

We have good support from Google. They provide onsite support and everything is available to us. We are happy with the support.

The initial setup is quite easy. 

I recommend this solution. Apigee offers a month free usage so you can play around and explore the product and then make a decision. We had a good opportunity to test things out before purchasing the solution. 

I rate this solution an eight out of 10. 

API/proxy lifecycle workflow for API providers is quite good and one of Apigee's strongest features. Also, like the completeness of the CLI and admin REST services, the Edge engine provides powerful, integrated analytics, which are noteworthy.  

Initial setup was not trivial for customer-managed topology.  Proxy versioning seems a bit confusing/buried in the publishing experience, especially for the URI-based versioning approach.

Not in production, we are still evaluating.

Nothing serious; just a bit complex.

We currently use WSO2 API Manager version 1.9x in production, but the solution is no longer meeting our needs.

If you deploy a 6-node+ topology, there are many steps required for initial setup. I feel most of this setup complexity is limited to the initial install, and the future auto-scaling of the gateway workload will be an easier/smoother experience

Setup was done by an internal team with some coaching by the vendor.

We are a telecom-based organization, so our use cases are generally based on telecom functionalities like the MF APIs. I'm a technical architect and we partner with Google. 

Apigee is a front-layer gateway and it helps to improve our overall performance.
We can repair requests and respond to vacant needs and that's a big help to us. 

Many of the features available are valuable to us including out-of-the-box policies, the vacant creation, throttling and more. We are using authentication and authorization which are also good features. 

Integration should be improved as we'd be able to use solutions such as NewSoft or Del Boomi. It would be helpful if Apigee would lower their licensing costs. I'd like to see a cloud-based solution and some new features similar to those available with TD cloud or Salesforce.

I've been using this solution for over six years. 

The solution is stable.

To date, our use cases have been limited so we haven't had significant scalability requirements. We have no plans for expanding the use of this product. 

On a number of occasions we've needed some immediate help or a quick turnaround, but the technical support response was quite slow. 

Neutral

Initially, we figured out how to deploy the solution on the job and it required some external assistance, but because we've been working with Apigee for so long, deployment is relatively easy for us these days and is carried out in-house. 

Apigee has so many servers nowadays that are based on requirements. Much of the information is available on Apigee documentation which is good. 

I rate this solution eight out of 10.