Apigee Reviews

We primarily use the solution for API management. We use the solution with open banking, and we are managing our customer's cloud, on-premises, and Apigee environments. 

The solution is great in general. There are many categories of APIs that need to be maintained. It helps maintain and add rules to manage open banking. 

The solution is stable.

The initial setup isn't too complex.

It can expand well. Google seems to be moving into the cloud more than on-premises and the cloud makes scaling easier.

Apigee deals with APIs. However, most of our clients need more tailoring done to the solution.

Google isn't enthusiastic about supporting older versions. Google is now trying to move all of its clients to X within the cloud. However, some still want on-premises. 

I've been using the solution for about four years. I've used it for a while. 

The solution is stable. However, it depends on the release, the customer, and the sophistication of the infrastructure. 

We have had some issues with bugs in the product itself. 

The solution is scalable.

We have three banking clients on the solution. 

The amount of users depends on the customer. Some use it internally. Others expose the API to clients. Some have more than a billion APIs. Some have less. 

The technical support is not the best. It does depend on the size of the customer. Larger customers tend to get more attention. 

The ease of setup depends on the level of sophistication of the clients. It can be rather simple; however, the more complex the infrastructure, the more difficult the setup can be. 

We do both cloud and on-premises deployments. The length of deployment depends on the customer. It depends on the kind of network or the organization. It can take a few months up to a year.

We have a strong knowledge of the flow and the templates. For us, it's pretty straightforward. 

There is a team of six people that can assist with deployment and consulting with clients.

There are different models that customers can choose from. They have a subscription model. 

I'm a consultant. 

We are using a few different versions of the solution.

I'd recommend the solution to others.

It'd rate the solution eight out of ten. 

Apigee brings a lot of projects, including development projects. For example, when an oil company is swiping a card in the palm station for payment of oil. As it swipes, it hits the database, and Apigee manages the entire process with the help of dedicated proxies. Managing those proxies is very easy, and Apigee makes proxy management very simple.

We have found APA management and API health monitoring valuable.

The solution can be improved by simplifying the account creation process.

We have been using the solution for a year and a half and are currently using version eight.

The solution is stable.

The solution is scalable, and multiple users utilize it in our organization.

I rate customer service and support as six out of ten.

Neutral

We previously did not use any other solutions.

I rate the complexity of the initial setup as medium. The deployment method is based on the company's contract, and approximately ten people are required for deployment.

We have seen a return on investment.

I rate the solution a seven out of ten. The solution is good, but the account simplification process can be improved. I advise users considering this solution to go for it because it has many API management features, including the health log error-finding tool and developing a new proxy.

We have a legacy and non-legacy databases that are both on-premises and off-premises.

Apigee is used to connect to any Google-based applications that are available. In addition, we are experimenting and testing in other environments.

I'm a CIO in consulting.

Apigee has proven to be one of the best of the breed. Others are attempting to innovate and are succeeding. So we don't know how innovations will be distributed, Azure, Amazon. Amazon, without a doubt, is lagging, but I've recently heard in the reinventing that they're working on a lot of API-related innovations. So you can't say that they'll be lagging behind as they are catching up.

We are experiencing some performance issues. Except in terms of performance, we can't find anything that needs improvement. This is something that we are trying to understand, and we will fix it soon.

I'm dealing with the Google and Apigee teams directly, so I can't go into specifics. But I believe we will be able to fix it sooner rather than later. It will be one of the most extensive implementations. And while we did not find any performance issues during testing and development, we did find some in production. We will be in a position to fix it soon.

Our environment consists of multiple clouds. The usual question is whether you have a single environment or a multi-cloud environment. What I've answered is applicable to all multi-cloud scenarios. I haven't specifically mentioned the Apigee-related issues. In CA Cloud, that is Google, I am working in a multi-cloud environment with settings and cross-components.

More platform integration, lower prices, and improved performance are all potential improvements; however, when it comes to standardization, all of them are converging on standardization, but, my criteria are more performance-based.

Either one is focusing on the API or on alternative exchanges that can improve performance. As a result, making a choice of API and the use cases that surround it, as well as how the implementation is done for scale, can be difficult at times. When we talk about the scale, there are definitely a lot of considerations that must be understood, and one of them is performance, which is our primary focus area.

If you are going to use APIs or even exchanges, you should be more concerned with performance.

I have been dealing with Apigee for quite a long time before it was part of Google. It's been approximately three years.

The stability of Apigee is one of the best of the breed.

The scalability of Apigee is good.

Apigee will be implemented in over 100 hospitals.

We have been working closely with technical support, and everything is fine.

We are also collaborating with Amazon teams and some of the standardization committees to help standardize APIs.

The integration of Apigee was straightforward.

It is not an installation, it's an integration. Apigee is integrated rather than installed.

The number of people needed to maintain this solution is determined by the project's, and the complexity of the situation.

Apigee is subject to licensing fees.

Typically, the customer is internal, so it is accounted for in the integrated budgets.

I have other affiliations. Like, I am associated with Cloud Security Alliance, which is a nonprofit organization. And I am also part of ISO SC 38. SC38 has a PWI, a preliminary work initiative on API management. And that goes as the advisory at a global level for a standardization. This topic is not only of my interest, but it is my passion.

I would recommend this solution based on the use case they have.

I would rate Apigee a nine out of ten.

We are working on some client POC where we have all the workloads deployed on Google Cloud. We wanted a gateway that was more like an API Management tool. We wanted to manage all our APIs centrally in one place. For example, we can route the traffic. We can limit, we can perform throttling, we can have the security checks like the authentication mechanism implemented centrally. We can also have a reverse proxy to our service endpoint.

I like implementing different policies, for example, rate-limiting policy. We can create a custom rate-limiting policy, and we can have an application-specific rate-limiting policy. That's what we're implementing or using, and I like that feature.

More documentation on the Open Banking Standard will help. For example, WSO2 supports the Open Banking API, but I can't find relevant documentation from Apigee. I'm not sure whether Apigee even supports the Open Banking Standard. If they do, then I think they have left out the documentation for that. For example, WSO2 has extensive documentation and training available to everyone. In that sense, I think, Apigee can improve.

I've been using Apigee for a few months.

It's a stable product. It's easy to manage, and we have implemented it for our production deployment.

Apigee is a scalable solution.

I never tried reaching out to tech support because the documentation is good. The documentation is available, and there is some training available on Udemy and the product site. These nicely describe how to deploy or set up different policies, which was enough for us.

The installation is straightforward. You just need to get a license for Apigee and then configure the reverse proxy. Once you have the reverse proxy configured, you have to set up whatever policies you want. One or two guys were able to install, deploy, and host our reverse proxy for our endpoint within a day.

We went through the documentation and the website and deployed the solution ourselves.

All these technologies are using Google Cloud for hosting our microservices, and we trialed Apigee. We were also using WSO2, an open-source API management tool, but as everything is on Google Cloud, we chose Apigee.

If your workload is already deployed on Google Cloud, integration is very easy. Even if your services are hosted in some other cloud, like AWS, I think you can use Apigee, but I haven't tried that approach. 

On a scale from one to ten, I would give Apigee a seven. 

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.

We are resellers of Apigee and also use it internally. The most common use case is monetization for the APIs. I'm the sales manager and we are resellers of Apigee.

The ability to convert from language to language using the same tool without needing different developer teams to deploy is a valuable feature. It doesn't require a lot of skill to run Apigee and the security features are good. This is a powerful tool for API management. 

The only disadvantage with Apigee is that they lack market presence. I think they may have limited resources. IBM's strategy is stronger on the marketing level. 

I believe they're working on adding some integration features that are currently lacking. 

I've been using this solution for three years. 

The solution is very stable even in very complicated environments. 

The solution is scalable and it's great for enterprise companies.

Technical support is good. Google team has many teams can support it. And there is a lot of partners ecosystem who understand and implement and support strategy as well.

I previously worked with IBM Connect but I prefer Apigee. It provides all the features and requirements for AI management.

The initial setup is very straightforward and can be done by anyone. 

The licensing cost is very reasonable and it gives you unlimited transactions.

I would recommend testing this solution for a month or so. It's easy to implement and easy to use. I rate the solution nine out of 10 - the one point reduction is because of the marketing strategy. 

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.