Apigee Reviews

Apigee is a platform for developing and managing APIs.

Overall the solution works well, it is one of the best solutions on the market. There is plenty of support documentation available.

The Apigee cloud admin UI could be more user-friendly by adding a few more features.

I have been working with Apigee for one and a half years.

The solution is highly stable.

We have built an API platform o over 2,000 different partners and all of them are using the gateways.

The technical support is very good.

The installation was not difficult.

I rate Apigee an eight 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.

I have worked on Apigee Edge and Apigee Dev Portal. Specifically, in Apigee Edge, the elements like products, developer, developer apps, and API proxies are interlinked with each other. Another special feature is configuring target servers, proxy config, and Cert related security, which regularizes incoming traffic from cloud users or external applications to internal applications in a secured manner.

It provides secured incoming connections with data and cloud-based API functionality, which results in efficiency and reliability.

Areas like traffic handling of incoming requests, security features between third-parties and Apigee, and between Apigee and internal network servers, resources, or JSON areas, etc.

A full year.

It's user friendly and no issues encountered with stability. Sometimes it may go down due to notified maintenance activity.

No, we can add any quantity of all utilities such as users, API proxies, developers, their apps, etc.

Four out of five.

Previously worked with physical box type solutions. Now using Apigee for API based connectivity along with cloud level access.

It's straightforward, and looks at security configuration, environment setup, etc.

Since it was acquired by Google, we can get a license based on our requirements and the cost level will depend on cloud access and support.

Yes. Analysed features like pricing, support, functionality, background analysis in market, cloud connectivity, etc.

It's a high-end API product acquired by Google. It has lots of functionality and can easily handle technical resources.

The following features are most valuable: API Management, Analytics, Quota, and the Developer Portal.

Being an employee of a service-based company, we have implemented the product for different customers.

Role-based access management needs to be improved. It would also be nice if the solution could be integrated with code versioning systems like Git/Bitbucket.

I have used this solution for more than 2 years.

The APIGEE SaaS offering is quite stable.

I did not encounter any issues with scalability.

On scale of 1-10, I would rate technical support 8.

No, I have not used any other tools.

The on-premises setup is really complex.

As most of the customers say, the tool is a bit expensive.

I did evaluate other options.

The tool is good, easy to use, and has good customer support.

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.

• API security
• Lifecycle management
• Analytics

Data monetization.

Development IDE, especially for Architect Review.

15 months.

Not on Apigee Edge, but few on BaaS.

No issue with SaaS version.

A five out of 10.

Yes, scalability was an issue with the earlier tool.

The SaaS version setup is easy. On-premise version seems to be bit complex.

Pricing options need to be chosen on a case-by-case basis.

Yes. AWS API, 3Scale, and CA Layer 7.

Implementation success would depend on having a good API architecture and design, using analytics, and following best practices of the lifecycle management provided by tool. Technical implementation should support DevOps, too.

I use Apigee Edge to develop and maintain proxy services on REST/SOAP web services. I also monitor transactions over Apigee Analytics.

I develop proxy services for other vendors.

Apigee is very fast in transferring requests and responses between Northbound systems to Southbound systems. It has a very efficient logging system which is easy to maintain. 

Apigee Analytics dashboard is useful to monitor transactions, error percentage, transaction latency, etc.

There are many features, which I have felt are very useful and easy to implement at flows.

Below are some of the points that I would like to highlight:

• I like Service Callout, JSON/XML Threat Protection, and JavaScript callout policy. I find them very useful.
• I found Apigee Analytics dashboard very useful for monitoring.
• Private cloud architecture
• Management APIs are very useful, because we can execute them from our server only.

Maintaining and deploying revisions need to be more defined.

It would be better to have access to the PostgreSQL Database Tables on monetization.