Apigee Reviews

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.

• 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.

We use Apigee an API gateway solution. It can be used in many areas or industries. For example, in Indian, the railway and finance sector, or in Australia, for the Oil Industry.

Apigee is a strong-featured solution. It leads in Gartner Quadrant ratings and it is a full-slated API solution that has the features that an API gateway requires.

I have been using Apigee for approximately three years.

Apigee has been stable.

I have found Apigee to be scalable.

We have more customers using Apigee than other API gateway solutions.

The technical support for Apigee is very good.

There is installation documentation available.

We have standard administrators teams for the deployment. We can also receive support from the Apogee team. If we are unsure of the requirement for deployment, we have one person from Apogee for two months and they will do the job and leave afterward.  

The price of Apigee could be less expensive. The solution can be purchased monthly or annually. 

I would recommend this solution to others, it is a good choice.

I rate Apigee a nine out of ten.

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.

Primarily we do the Apigee implementations for the customer. We are more like a service company. We sell the product and consult with the clients about their needs. There are options for the API gateways and we look at the client's requirements, their budgeting, and then we deliver and install the new solution.  

Apigee makes it nice and easy for the clients and those using the product to access the product's help resources.  

It would help with Apigee if we could make a list of our assets. If the client knows more about all the extensions they can use to work with through the Google cloud and we have an extensions database it would be easier to let them know what is available and we could do more to recommend Apigee for all different kinds of customer needs.  

I have been working with Apigee at this company for the past three years.  

The stability of the product is not an issue.  

We have not had any issues with the product scalability.  

We are actually partners with Google, so we get the best support from them.  

I did have some previous experience with other products in this category before Apigee, like MuleSoft. The main differences between Apigee and MuleSoft are that Apigee is more lightweight and the licensing is also lesser than the MuleSoft. Based on the use case of big clients, the ones who want more services can get them and because the Apigee solution is more lightweight it offers more possibilities for them to use API solutions.  

With Apigee you can bring in some adapters to work with things like business rule engines. So those might create more standardization and help make the investment in Apigee more valuable.  

I tried to do the initial installation and setup a couple of times. It is straight forward and easy. It is just done by calling a couple of CMA (Connection Manager Agent) commands and you can get it up and running.  

What I would recommend for clients who are considering this type of solution depends on the customer's use cases. Since we are Google partners we generally go with Apigee as the solution. But if the client insists that there has to be a lot of orchestration and other integrations need to be done, then we will go with MuleSoft.  

On a scale from one to ten where one is the worst and ten is the best, I would rate Apigee as somewhere around an eight.  

Ease of use during development, deployment, discovery, and usage of Developer portal.

A mature end-to-end model for API distribution and revenue earned through monetization.

One unified solution for different LOBs. Easy interface to monetize and deliver APIs with very easy integration for third-party development environments/delivery.

• Flexible setup
• Pricing and license cost for end-user delivery/ distribution model
• Both on-premise and cloud deployment models are available.
• Highly scalable from any initial topology to horizontal extension.

Technical support model for OPDK should be more exposed and mature in terms of providing support during installation, run, and debug of Apigee in production on OPDK mode.

We use it to build API proxies for securing targeted back-ends with an emphasis on Continuous Integration/Continuous Development (CI/CD).

It has been a potential source of mission-critical customers.

We expect to gain new business opportunities upon providing Apigee services to customers.

• Pragmatic RESTful
• Developer portals
• Continuous Integration/Continuous Development
  
• Tracing tool

I would like them to add features, such as caching and mediation policies.