Apigee Reviews

API gateway tool and management of API solutions. This tool is extremely helpful for discovery, self-service of API solutions.

• Allowed us to convert from SOAP to RESTful patterns
• Improved security/throughput/management
• Throttling is also useful as well as management console tools to track performance.

• API gateway tool
• API developer tool
• Visualization tools to measure and manage the performance of APIs. 

I would like to see a long-term direction for the overall architecture (similar to what WSO2 has done), in that all three areas — pub/sub, events, and APIs — are treated as part of a continuum, instead of treating each as separate topics.

We use the solution as a platform to integrate different APIs and provide authentication, authorization, and performance security services.

The solution's most valuable feature is its ability to integrate APIs for various industrial sectors, including telecom, banks, and multinational companies.

They should improve the solution's monitoring tools for on-premises environments. Also, they should make all the essential features available for the private cloud.

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

The solution is highly scalable. I rate its scalability as a ten.

I rate the solution's initial setup process as a seven.

The solution is advanced. It works efficiently compared to other solutions, such as MuleSoft. I highly recommend it out of all the integration platforms. I rate it as an eight.

This is our major service when we have services and need an API gateway. They allow us to expose these services to clients.

The solution offers good customization. It's very easy to customize in general. 

You can integrate with things very well. 

The caching is good.

You can add basic flows with ease. 

The Google CMS is a great tool. 

The solution is stable. 

Technical support has been decent. 

We are considering scalability regarding using a centralized environment, and the documentation seems to indicate it's not easy to integrate with Kubernetes or deploy into a cluster. 

It's not using SPA, single page applications, like Angular. 

There isn't very good monitoring right now. We need better performance monitoring.

We need it to offer better debugging, so if there is slowness in the flow, it's not easy to fix. You have to use other tools to debug.

I've used the solution for four years. 

The stability is good. I'd rate it nine out of ten. It is very reliable. There are no bugs or glitches and it doesn't crash or freeze. We've had no issues on this front. 

We have around eight people that directly work with the solution. They are four developers, two engineers, and two support staff. 

The scalability is good. I'd rate it five out of ten. It's deployed on the VM. You cannot scale up in some areas as you might hit a limit. Then, there are peak hours, and that might be different as well. You might hit a wall. 

We've dealt with technical support in the past. They've handled a few tickets. However, I have never directly dealt with them. I have not seen any complaints in regard to the service they provide. 

Positive

We did not use a different product previously. 

I didn't handle the deployment. I don't handle that aspect of the solution. 

We do have a team that manages and administers the solution. 

There might have been some assistance from the Apigee support team during implementation. 

The pricing isn't something that I deal with. I don't know the exact cost. 

We are currently looking into other solutions. We want to see how others stack up in terms of pricing, stability, scalability, et cetera. 

I am using the latest version of the solution. 

I'm not sure if I would recommend the solution to others. I still need to make comparisons between this and other options. I'm trying to decide if I should stick with Apigee or move to something else.  

So far, I'd rate the solution eight out of ten. It has a high rating on Gartner. 

Our primary use case is for security but also the mediation that goes with it.

The most valuable feature is monetization.

I would like to see SOAP services and socket-based connectivity developed. Apigee is known for exposing the REST API but not the SOAP API. Our clients are requesting these two features and we do have a workaround we use, but an upgrade in these two areas would be great. I would like to see more integration for example Enterprise Service Bus and this will help Apigee gain more popularity.

I have been working with Apigee for the past six years.

Apigee is a stable product. We have had existing customers for the past four or five years now.  

Technical support is alright but I have mixed criticism. Sometimes you get answers very quickly and on time, but in some scenarios when there is a product issue it takes time. If there is anything that is not implemented and they need some time to implement it, then it takes them months. If the error is something that is a known issue they reply back quickly.

Apigee is more straightforward and flexible, with implementation and designing. Other products currently on the market are more complex overall to sustain. The time it took us to set up was around two to three months.

There is one main reason we went with Apigee and that is the importance of the Gartner and Forester ratings. Apigee is on top of all the Gartner and Forrester ratings. The other reason is because of the smooth operational perspective.

If customers are trying to do long-term planning, and want to apply monetization on their APIs, then Apigee will be the best in this situation. I would rate Apigee a nine out of ten.

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.

Our organization currently has twenty Apigee end-users. We use the solution for API management of financial and e-commerce domains.

Apigee is relatively easy to use for developers.

I have been using Apigee for six years.

Apigee is a stable solution.

The SaaS version of Apigee is quite scalable. The hybrid version is also scalable depending on your requirements.

I am satisfied with the support offered by Apigee.

The initial setup is not straightforward, particularly for hybrid solutions. It is easier to manage the managed services or SaaS-based versions.

The implementation takes time. The production setup includes TLS among other things, and the management and operationalizing take time as well.

We implemented the solution in-house.

Apigee's licensing costs more than other solutions. Some add-on packages are sold separately. For example, monitoring is not included in the standard package of Apigee Edge.

Anyone considering Apigee as a solution should start small and increase usage with experience. Start with a centralized small team and expand based upon the maturity model that Apigee has and recommends. I would rate this solution an eight out of ten.

If the budget is not a concern then I will choose to go with Apigee over WSA-2, but if it is then I would prefer the latter solution. Apigee is quite pricey. The price is a thorny issue as there is little room for negotiation. 

Unlike WSA, Apigee does not have a partnership model, something which makes it a bit easier for companies such as ours to go with the former solution. 

While I cannot comment definitively on the partnership issue, as the company has yet to get back to me, I can say that this issue and the one of the pricing are why I choose to rate the solution as a six out of ten. 

The stability is fine. 

Apigee has better scalability than WSA. 

While the technical support seems fine, I cannot comment on this with certainty, as we did not go ahead with implementation of the solution. Had we gone ahead with a partnership with Apigee, then I would be in a better position to do so. 

If the budget is not a concern then I will choose to go with Apigee over WSA-2, but if it is then I would prefer the latter solution. Apigee is quite pricey. The price is a thorny issue as there is little room for negotiations.

If the budget is not a concern then I will choose to go with Apigee over WSA-2, but if it is then I would prefer the latter solution. Apigee is quite pricey. The price is a thorny issue as there is little room for negotiations.

Unlike WSA, Apigee does not have a partnership model, something which makes it a bit easier for companies such as ours to go with the former solution.

Apigee has better scalability than WSA. 

We are customers of Apigee.

I rate Apigee as a six out of ten because of its pricing. 

In my previous company, I used Apigee after modernization to manage client APIs.

Apigee is a great product with good feedback and recommendations from clients.

It is best to ask a developer about the areas for improvement in Apigee, as I'm a content writer, though the pricing for the product was a bit higher.

Apigee would also need developers or a dedicated team for deployment. I also found it challenging to manage sometimes.

My last project with Apigee last December.

Apigee is a stable product.

The company only used Apigee. It didn't use any other solutions.

As a writer, I didn't set up Apigee. Another team set it up.

Compared to other products, Apigee had higher pricing.

I used Apigee for my customer, but I no longer work for the company.

I'm a content writer and was involved in researching and creating documentation about Apigee for a client.

The majority of the clients had fifteen to twenty users of Apigee.

My rating for Apigee is seven out of ten.

The company was an Apigee partner.