Apigee Reviews

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.

One to three years.

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.

Public Cloud

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.  

Hybrid Cloud

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.

Less than one year.

It is a platform for the publication of API services, access control, limiting the use of resources, and monitoring consumption.

• Identifies services which are most consumed.
• Identifies possible risks.
• Improves productivity.
• Accelerates development and deployment processes.

• Developer portal 
• Apigee Sense
• Analytics
• Microgateway
  

• Predictive analysis of consumption
• Identification of attacks
• Identification of operational errors
  

One to three years.

We use this product for exposing API's to the digital platform and for B2B.

I think it is the most functional tool on the market. The security is a valuable feature. 

Apigee on premise is quite complex and it is always moving faster. I would advise anyone who is interested, to use the SaaS implementation.

Less than one year.

I have not encountered instability with the product. 

I do not have experience with tech support. 

We are using Apigee for multiple use cases. It serves as the first layer of security for all our backend applications where we have implemented OAuth, OIDC, and OAuth 2.0, along with rate limiting and contingent protection. Another use case is as a load balancer for the backend application. We also utilize it as a monetization tool. We've exposed various services to partners, allowing them to consume these services which are monetized based on consumption.

I use Apigee as an on-premises solution. It provides all the necessary capabilities for current technologies, enabling communication and translation between protocols, along with supporting stringent security features. These are the main reasons I use Apigee. For API security, I am using OIDC along with OAuth 2.0 and content protection, including GSM protection and XML thread protection.

In the on-premises solution, there is a need for implementing WebSockets and HTTP2. Some API gateways, like Kong, have already adopted these features. Apigee should also incorporate these capabilities, especially in the on-premises version.

I have been using Apigee for more than ten years.

Overall, the feature and product implementation did not present many challenges. The product support team is cooperative and provides insights and solutions when needed. The setup process for Apigee is straightforward, especially for those who understand integration technologies.

I have not faced any performance issues with Apigee. It has been stable in my experience.

In my experience, Apigee is scalable.

The customer service and support are cooperative and effective in providing insights and solutions during challenges.

Neutral

I have worked on Mulesoft, not extensively but I have experience with it. Apigee's product cost is high compared to other products, and certain features need improvement to maintain market leadership.

The setup process for Apigee is very straightforward. Anyone knowledgeable in integration technologies can easily implement the solution.

In my recent project, I migrated thousands of services from an existing platform to Apigee. I created a skeleton API proxy based on requirements and used tools and mocks to build the framework. In six months, I implemented all current services on the Apigee platform.

The only notable return on investment is the market reputation of Google as a leading player. Customers believe security and performance challenges will be resolved more quickly with Google products.

Apigee's product cost is quite high compared to other products. Customers think that going with Google ensures quick resolution of security or performance issues.

I have worked on Mulesoft, although not extensively. Mulesoft ESB, API Gateway, or Flex Gateway offer a suite of solutions, unlike Apigee, which provides only the Apigee gateway in the on-premises solution.

I would recommend Apigee, specifically the cloud solution, to access all recent features rather than the on-premises version. Overall, I rate Apigee as a seven out of ten.

On-premises