Apigee Reviews

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 just started with the solution and are learning about its functionality and use cases right now. It's a requirement in our company that we have a tool of this nature.

There is less CLI needed compared to other options. It's more user-friendly and easier to navigate. 

Everything is working well. We haven't had issues. 

The solution is stable and reliable. 

I don't have any notes for improvement. I don't need any extra features. 

I just began using the solution. 

The solution has been stable. We haven't had issues since we started using it. There are no bugs or glitches and it doesn't crash or freeze. 

We are using the latest version of the solution. We're new to the product. I'm not sure which deployment we are using. 

I'm a customer and end-user. I'd recommend it to others. So far, using it has been very helpful.

I'd rate the solution eight out of ten.

Apigee is a platform for API management.

Apigee is a pioneer in the industry and has good features and functionalities. It is a good tool for API management and it has more advancements than all other tools in the market in certain areas.

It has many features, such as flexibility, coding writing, and JavaScripting.

I have been using Apigee for approximately four years.

Apigee is stable. In the entire API management world, I feel this is one of the best tools for pure API management. If there are any orchestrations or business processes to be involved, then Mulesoft or Boomi can be used, but comparatively, all the security and governance policies that are available on the dashboards and the reports make Apigee the best tool for pure API management.

The installation is good. I won't say it is complex, but it has many configurations and types of policies that are available. However, it can be easily done.

Apigee is slightly expensive, but again, it can depend on the type of usage. All things considered, it is slightly expensive. 

AWS is winning in the cost category, they have many packages and services but when using all these services together I am not sure what the cost would be.

I have evaluated Mulesoft and Boomi. I have found these two solutions are being used secondarily to Apigee. Additionally, AWS and Azure's Gateways are becoming popular in the market. From the cost perspective, in the two years, AWS gateway is widely being used. These four solutions are widely being used in the market but Apigee is much far ahead than all other tools.

AWS and Apigee have similar features. I don't see any significant change in the difference at the moment. The choice is more about convenience and cost.

I rate Apigee an eight out of ten.

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.

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

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.