Apigee Reviews

This solution provides us with a good gateway for API Management and versioning. It gives us easy to map backend version services, and additional security and policies can be adopted.

We are achieving five thousand TPS (Throughput per second) on peak load, and managing thousands of proxies against K8s cluster services.

I have found the most valuable features to be tracing a proxy, and managing proxy versions and revisions via the Edge UI component.

Drag and drop of features would be more beneficial, rather than manually working on the configuration and updates.

We are using Apigee as the API gateway. We also use it for our preparation. We use the API for security and a lot of other tasks. Our customer use cases don't have any legacy systems. We're using Apigee, however, Apigee doesn't provide for a subscribe-publisher capability. It meant Kafka was just to provide the matching capabilities of Apigee. However, mainly we consider this solution as the API gateway and management system.

The security provided by the solution is excellent. 

It provides for an on-prem setup. That's very important for us. As the regulation of communication policies. To be able to provide the telecom companies that tool and install their products on-prem for easy management via cloud inside Saudi Arabia is great. 

The solution provides very good mitigation capabilities.

The integration could be improved within the solution. There is a need to pay more attention to this. 

It would be ideal if the solution could provide publishing capabilities as API middleware.

We've just been using the product for a few months for a new project we are working on. It hasn't been that long.

The solution provides a very stable solution for us.

Our mother company has been using Apigee for maybe five years now. I talk with them about making assessments for selecting an API gateway solution. They didn't have any issues with scalability or monitoring. Apigee was perfect for them. We didn't face any issue with it in terms of scalability or even tenability. It's very easy to scale. 

As an integrator, we have about five different clients who use this solution. They have a different number of users.

The technical support for the solution is pretty good. We're satisfied with the level of support Google provides. They are knowledgeable and responsive.

The initial setup isn't complex. The setup configuration offers a very simple approach for developing and deploying services in Apigee. It's straightforward. It's easy for our developers to apply a lot of services while offering a faster time to market.

Apigee is not cheap. It's expensive. At the same time, our company is already buying an enterprise license so any company inside the group can use it. In general, however, it's pricey.  

We're just a customer. We don't have a business relationship with Google.

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

Whether of not this is a good solution for a company depends on a lot of criteria. The budget itself needs to be considered, for example. Apigee is perfect. They provide good support. People from Google are very cooperative as well. They listen for feedback on features. 

They don't provide a partnership to just any company. You need strong criteria to get a partnership and to be able to support and feature the license. I like this, to be honest with you. That's already making our implementation easy. We're only dealing with companies that know how to do work in Apigee setup and installation and configuration and they have a long history of providing strong criteria. In general, I recommend Apigee.

We are using Apigee as our API gateway.

The most valuable features are scalability and technical support.

The definition of the APIs should improve because you can't easily validate the inputs and outputs. Better functionality for validating inputs and outputs would be helpful.

I have been using Apigee for four years.

We are working with a SaaS model and we install the on-premises model version also.

Apigee is a very stable product.

The scalability is incredible. We make an average of 22 million API calls.

We have less than ten people who are developers.

We have plans to increase usage in the future.

The technical support is very good and we are satisfied with it. They respond very quickly and I like it.

I have used several solutions previously, such as IBM API Connect, WSO2 API Manager, and many other API solutions.

It is not suited for small companies. It's expensive.

For a bank, it would not be expensive, but to implement this solution for a smaller company such as an insurance company, it would be too expensive.

The pricing is complicated and not flexible.

The older versions are more suited for small to medium-sized companies. You can no longer pay €20,000 per year.

This is a very good API tool.

I think that this solution is very good in some use cases but not very good for some small companies. It can be complicated for licensing and pricing. This is a product that I can recommend otherwise.

I would rate this solution an eight out of ten.

The solution is primarily used for developing and publishing internally IPA (80% of the time). The other 20% of the time the product is used to create and develop an ecosystem with various partners.

Our clients would best be able to speak to that. As we just assist them in the process, it's not on us to divulge such details.

The developer portal is very useful to customers.

The mediation aspect of the solution is very good.

Technical support is pretty good. We are pretty happy with their service overall.

The solution is flexible and offers good customization capabilities.

In general, the product isn't too technical.

The pricing of the solution could be improved upon. We'd like it if it was less costly.

The solution needs something that supports real-time streaming.

Our customers are users of the solution; we don't use it directly.

There are close to 60 users at the moment. They are from the development team, the application team, and managers mostly.

We have not spoken to our clients about increasing usage or scaling the product. I am unsure of their future plans in that regard.

We have used technical support in the past. They have been pretty helpful. There's a mission team that deals with them mostly. I don't have much information beyond that.

I am unsure if our clients used a different solution previously. I don't have access to that information.

The initial setup is pretty straightforward. It's not overly complex. A company shouldn't have any issues setting everything up.

We did a hybrid deployment, the entire process took us less than a month. It's not a long, drawn-out process.

We are consultants. We can assist our clients with the deployment process if they need help.

The cost structure could be adjusted to make the pricing more reasonable. If they improved, likely they would ope themselves to many more markets.

We don't directly use the solution we are a service company so we help our customers use the product. We are consultants.

I can't say which version of the solution we're using at this time.

I'd advise other organizations that you have value any solution beyond a price comparison with other API management solutions. You will need to look at APS strategies needed in the organization and the importance of creating API products. Once that strategy is laid out you can put the right resources in place. Basically, everyone needs to have a plan first before investing in an API management solution.

In terms of Apigee, more exposure of the platform to wider stakeholders will definitely help in modeling best practice principles into EPA communication and evolution.

I would rate the product at a nine out of ten.

There's always room for improvement. However, it's not heavily technical. There's a lot of flexibility for developers to bring in customization. It's not rigid. If you have a team looking at APS cases, products, and you, how a corresponding APA team strategy, Apigee as a platform is very good. It's quite a comprehensive option.

There are plenty of use cases. My clients were using for internal API management as well as external API management, including subscription models and pre-payment models.  Essentially, it was for using internal data and selling external data.

Apigee gives you plenty of opportunities to set up your workspace depending on how you want to manage your APIs. This is something that the majority of clients like.

What my clients don't like is that the on-premises solution is not being treated and maintained as well as the cloud solution.

I know that they are working on the integration of no-code and low-code solutions to make it more accessible to users that have no technical background. This is something that I find very interesting and they should continue working on that.

I was working at a client site where Apigee was being used. I have two years of experience in this environment.

Stability-wise, I haven't observed any major issues with the product.

It is pretty scalable and we haven't reached any limits so far. We have thousands of users. There are a few hundred active internal users, a few thousand developers, and far more external users.

I haven't been involved in any interaction with support.

I would like to see the implementation of further options for billing because as it is now, the opportunities you have in terms of a package are limited. You don't have the choice of too many billing models, which is an issue that needs to be worked on.

My clients have a monthly pricing model.

If you compare this to Microsoft Azure API Management, Apigee is a bit better because Microsoft has no real built-in solution.

I would rate this solution an eight out of ten.

We are a solution provider and Apigee is one of the API management products that we implement for our customers. Most of our clients want to expose their APIs to their consumers and they need to have a generic infrastructure for it. At the same time, they want it to be scalable as well as highly secure.

We have been able to fulfill all of our use cases with Apigee.

Tracing in Apigee is a very good feature.

The scalability and performance are both very good.

As it is now, the rotation of certificates is a manual task and is something that can be improved. It only has to be done once every two or three years, but I would state that there is still room for improvement.

We have been working with Apigee for five years.

The last time we had a disturbance was a year and a half ago, and it was due to an AWS infrastructure failure. Apigee was not to blame for it. For the most part, it has a very high availability.

We have some very large customers that make a billion API calls a month and we have never heard any complaints about scalability. It's not an issue.

About half of our clients are mid-sized companies, with approximately 5,000 employees, whereas the other half is made up of companies that are bigger than that. 

We have engaged multiple times with Google's technical support. I can't say that they're necessarily very quick in their response. It can take a couple of days. That said, they're very knowledgeable and to the point. In the five years that we have been working with them, we have built a big network with them.

We use several similar solutions including Mulesoft, SAP, and Azure. Mulesoft is the one that we use the least and try to replace it with other systems. Out of ten customers, we have two using Azure, six using Apigee, and the final two using SAP.

The initial setup is very straightforward and we perform it as a service for our clients. Normally, it takes us about a week to get it fully operational with all of the rules in place, and fully onboarded.

When it comes to deployment, we have variety with our customers. 60% of them will use a cloud-based deployment, while the remaining 40% work on-premises. We are now just engaging the first customers using the new hybrid model from Apigee.

We perform the deployment and maintenance of Apigee for our clients.

My advice for anybody who is implementing Apigee is to use it as an API platform, and not as a full-stack integration platform.

I would rate this solution a nine out of ten.

The solution is primarily used for managing the interactions between channels, customer experience systems, and other systems.

The API management on the solution is very good. It's likely the most valuable aspect of the solution for us.

The pricing is okay.

It is possible to scale the solution.

The solution isn't really lacking any features.

The user interface could be better. It could be easier to navigate and more user-friendly.

The pricing model could be improved. Things can get expensive for larger companies, or organizations that are growing.

The solution should offer more training to partners. It would help in the understanding of the product by quite a bit.

I've been using the solution for three or four years at this point. It's been a while.

The stability of the solution is okay. We haven't run into any issues.

Larger customers typically have 14-20 users on the product.

For large transactions, the commercial model is proving to be a constraint to some of our customers. For example, they're asking, when the scale grows, the commercial option becomes expensive. Some of our customers, for example, ask for an alternative approach due to the cost of the commercial model.

That said, you can scale. It's not a challenge in terms of doing it, it's just a challenge in terms of cost.

I've never really had to contact technical support, and therefore can't really speak to their level of assistance.

Typically, if I need assistance, I turn to Google or forums and I seek help online that way.

The initial setup is straightforward. It's not overly complex. A company shouldn't run into issues setting it up and rolling it out.

I'm part of a services organization. There are various developers, and Apigee users tend to be more than 300 people from our organization. In terms of support, there are 40 people. These are split across different customer organizations.

We are an integrator and can implement the solution for our clients.

The pricing starts off okay, however, for enterprise-level organizations, or companies that are scaling, the price can rise and become costly. If you don't scale too big, the pricing is fair.

We are systems integrators. We aren't just end-users.

In general, I would rate this solution at an eight out of ten. If the pricing in relation to scaling was better, or if they offered better partner training, I would rate them higher. There aren't really any features lacking and we're largely happy with the product.

Apigee has many features in their feature bucket. When you get in touch with their sales team for sure you’ll get to know these :). Some which I liked most and which makes this product stand out are:

Developer portal

It is a Drupal-based portal for onboarding of developers and catering your API documentation. They have this feature called Smart Docs, which allows developers to not only get to know the API documentation but directly make the request and see the response. They have the ability to consume OpenAPI specs formerly know as Swagger Spec. Considering the fact that it is based on Drupal, the portal gives you damn good control on the documentation, content delivery, and developer onboarding. With a little customization, you can integrate any kind of workflow into this portal.

Monetization

Monetization is another good feature which provides a revenue model around your APIs. Many of the enterprises are looking for these kinds of options, get their offerings as API and generate revenue out of it. Apigee provides a complete end-to-end solution for monetization of your APIs. They have different revenue models and packaging models such as freemium, hit rate, revenue sharing and your custom models based on your transactions criteria. Get to know this in more details at http://docs.apigee.com/monetiz...

Analytics

This another great feature of the platform. They capture the details of all the incoming and outgoing traffic of your APIs. Based on 300+ default dimensions you can generate beautiful and insightful reports on usage and consumption of APIs. This can also be used to find out performance and errors troubleshooting. They have default reports for proxy performance, target performance, error analysis, cache performance, latency analysis, developer engagement and traffic composition. On top of these, you can generate custom reports based on the dimensions captured by Apigee.

Another feature of analytics is that you can add your own dimensions and do business analytics on top of API analytics. Being acquired by Google, we can expect that Google will add some good features around it or maybe they will push this component to Google’s analytics engine. All of the analytics data is exposed as APIs so you can consume this in your programs and develop any kind of workflows or applications around it. Dig into it at http://docs.apigee.com/analytics-services/content/analytics-services-overview.

BaaS

BaaS is based on Apache’s Usergrid, which provides a back end as a service. This is a No-SQL database and gives you ample flexibility with a RESTful interface for data storage. Apart from being a data store BaaS also has features, such as push notification, geolocation, docial graphs and RBAC user management. This is a wholistic back end for any mobile app. Get to know more on this at http://docs.apigee.com/app-ser...

This platform has opened the doors for a different line of business altogether. We are now able to monetize our features and deliver them easily through APIs. Since the advent of mobile and IoT, we are focusing on providing an easy interface for third parties and developers, and Apigee has given us a head start in that direction.

The installation and management of this product are still a clumsy task. They are developing the monitoring feature based on influx DB and Grafana, but it still has a way to go before it can be used in a production environment. The documentation for OPDK on different component integration is not available or not sufficient. Since it is based on various open sourced projects, we might have to depend on the fixes provided by those components rather than Apigee directly fixing the issues.

I have used this product for more than 2 years.

I have worked with versions 14.16.05 to 14.17.01. The latest version as of this writing is 14.17.05 which brings in many good features and some fixes and security patches. The details of this version can be found out at their release notes page. http://docs.apigee.com/release-notes/content/apigee-release-notes

This a stable solution as long as you don’t meddle with the topology of your installation. You have to follow the strict start and stop sequences in case you need to add or remove some nodes.

This is an easily scalable product based on your needs and loads on the system. Almost all components can be scaled horizontally which gives it an edge over other options available in this domain. However, you will have to make sure that you follow the guidelines and strict steps, as documented by Apigee, for adding or removing the nodes for a specific component.

Technical support is really good, as long as you provide them complete details and causes of system failure. If you are a cloud customer then you might not have to deal with support as frequently, but for OPDK customers you either need to have your own technical team to manage your infrastructure or get one of the service providers to do it for you. Apigee provides complete operational and developer training programs, though they will charge you good money for these.

I haven’t quite used any other product in API domain other than Apigee. Although I have worked once with Akana, it was for a different use case altogether.

The setup is completely dependent on what you choose. If you go for the on-cloud version there is no setup needed. Within a week your API development will kick in and you can see the system live.

But for OPDK customers this will be a tedious task. They have some pre-requisites such as firewalls that need to be opened and, based on what topology you want, what is your expected use of the platform and how you want to mold it as per your enterprise security guidelines. These will govern the installation and initial setup of the platform.

Based on your usage of the APIs you can take a decision to go with either an on-cloud or OPDK version. Get in touch with the sales representatives of Apigee.

For on-premise, they usually offer Enterprise plans with different licensing options. Apigee also has a tie-up with SAP where SAP sells Apigee on-premise and On-cloud versions. Apart from rebranding SAP, it also adds some security from the SAP software delivery front. If you are looking to get an API platform and have Apigee as an option, then do evaluate your usage and requirements, as Apigee provides great features based on your requirements.
Check out the pricing and features details at https://apigee.com/api-management/#/pricing.

Set goals for future enhancement and extensions as this platform provides a lot of features that you can leverage to build different lines of business. Start with a small or medium scale topology and, based on the analysis of platform usage, you can always scale it to your need.

Apigee is among the leaders in API platforms. They have been in the API field since the time it was introduced. Constant innovation and introduction of new features into the product faster than the competition makes them one of the leaders. Also, now that Apigee is part of Google, we can foresee a good road map ahead for this platform. For sure, Google will have their input regarding the features and will try to make it more compatible with Google’s existing infrastructure such as Google Engine and Google Cloud Platform.