Apigee Reviews

I use Apigee basically for API management to manage all my APIs.

The number of internal users in my organization is significant, as we are not providing access to any external users, only our internal Allstate users.

I have experience in Apigee API Management.

Apigee is market standard currently, as it is the number one product compared to any other product, and it has different policies, built-in API management policies provided by Apigee, with over 50 plus policies available.

The impact of Apigee's analytics on my decision-making process is quite helpful because it includes monetization features, allowing me to charge for each API transaction.

Apigee supports handling different API traffic patterns with a lot of features, which are advantageous.

There is room for improvement with Apigee as OPDK private cloud enhancements have stopped, focusing only on Apigee hybrid and Apigee X, with Google no longer adding new features to OPDK private cloud.

I am not currently utilizing AI in the private cloud with Apigee, but I'm unsure about hybrid and Apigee X.

I have been working with Apigee for around seven years.

The deployment process took six to eight hours manually, and if we use automation, it took three to four hours.

I completed everything by myself without any help during the deployment process.

Regarding stability, Apigee is stable, and I would rate it an eight.

Scalability is also similar; I can rate it an eight as the feature is present.

Google technical support is not that good nowadays, but it was better earlier. In the past two years, I have been experiencing less assistance, and I would give a rating of five to six out of ten.

Neutral

I am not into MuleSoft API management; I have experience in Apigee API Management.

Initially, the setup has some difficulty because you have to know the manual installation procedure, but once you are comfortable with manual installation, we can proceed with automation.

A team is required for maintenance, with at least two people in each shift, totaling a minimum of 10 people.

I am referring to Google Apigee.

I am mostly working with Google services, specifically Google API Management.

It is beneficial to use Apigee, and I can confidently say that.

I would recommend Apigee to other organizations if they are considering AI, as it will be helpful; they have already added AI features into the Apigee docs for users to search queries and issues efficiently.

Considering pros and cons, I rate Apigee a seven out of ten overall.

Maintenance is required for Apigee; 24/7 maintenance is necessary.

I am currently working only with Apigee and do not use any other API management tools or security products.

We are using Apigee in several scenarios across different environments. It serves as our main gateway for APIs, facilitating communication with both external and public entities. This includes complete capabilities like security, implementing various features, high availability, and monetization. Apigee is extensively customized to meet our needs.

The features for API security have been significant with Apigee. We are currently migrating from Google on-premise to Google Cloud for even more advanced security solutions. 

Although Apigee’s analytics capability is not as strong as expected, we rely on Elasticsearch to monitor traffic, which provides high visibility and control and surpasses Apigee in certain features.

Analytics is one of the areas needing enhancement, specifically more visibility and control over traffic to improve capacity management and high availability. 

The replication process between Master and Slave for disaster recovery takes too long. Dependencies on analytics impact the performance of the user interface, which should be separate. 

The complex setup process on-premises, especially with multi-node installations, could also be improved. 

Additional control in product declarations, based on operations like POST and GET, is needed.

I have been working with Apigee for up to six or seven years.

Apigee is stable, and we have had the system running on Apigee servers for more than four years without any stability issues.

Scalability for the runtime domain, including routers and message processors, is almost straightforward, however, adding extra Cassandra databases is complex.

Technical support from Google is not satisfactory. Unless the issue is highly escalated, most support cases receive pre-made answers. This results in a disappointing experience as the support team seems to start from scratch with each case.

Neutral

The setup process, particularly on-premises with multi-node installations or data centers, is not straightforward and requires careful handling.

Apigee is high-priced, suitable for large enterprises where the benefit aligns with the cost.

There is a product called Gravitee that tries to compete with Apigee, however, I don't know much about it.

I rate Apigee at eight out of ten. 

I recommend it, especially to large enterprises, for its strategic benefits, even though technical support and costs are areas of concern.

Mainly for my previous customer, Apigee was used for API management.

Apigee served as a central hub for API management, allowing multiple applications to reside on a single platform, which enhances security. It helped manage potential threats by providing a single point of contact to stop communication in threat cases.

Apigee helps with API security and management. It is easy and fast to implement solutions and offers scalability when required. It also provides secure ways to implement policies for authentication and authorization.

There is room for improvement in v-logging for each transaction. Additionally, Apigee only allows validation of transactions up to a four-hour period, which requires manual hovering over the date and time. The error notification count is also limited by licensing, which could be improved.

I have been using Apigee for close to four years.

There have been very few issues, making Apigee a stable solution.

Apigee is scalable as it can accommodate increasing demands and requirements.

Apigee's customer support is excellent. They are responsive and provide assistance even during production issues, joining calls to resolve problems.

Positive

I haven't worked with other API management tools at this client. I can compare it with WebMethods, which only supports specific applications. This is unlike Apigee, which allows communication directly from other applications.

The cloud application setup is straightforward, whereas the on-premises setup faced complications with clustering and containerization, coupled with security restrictions.

A small team of four people was involved in the deployment, including network, installation, and developer roles, with initial assistance from Apigee.

The primary return on investment is enhanced security and centralized management of multiple applications, providing a single point to handle both routine and exceptional API communications.

My understanding is that Apigee is perceived as slightly costly compared to other tools in the market, however, the features it offers justify the cost.

I have theoretical knowledge of MuleSoft and Dell Boomi but not practical experience. We also considered UiPath and webMethods yet have not implemented them.

Apigee offers significant advantages like a single hub for API management in varied environments, supporting communication flexibility across different applications.

I'd rate the solution nine out of ten.

Neutral

I’m involved in all the R&D work, building solutions, and designing architectural designs that include Apigee and other open-source API managers. As a Google partner, my major focus is on Apigee. Another API manager, WSO2, is open source and suitable for organizations that cannot afford Google Cloud Platform services. However, I mainly use Apigee in my integration, modernization, and architectural designs.

I ensure that customers and organizations have an integration layer in their modernization journey and that layer needs an API gateway. The solution provides a complete API management solution and is one of the most important in the industry. It offers three deployment models: cloud-based, on-premises, and hybrid. I have skills and experience in building, installing, configuring, and managing all three deployment models.

Apigee is the heart of the architectural design for building an integration layer in our digital transformation projects. Organizations need an integration layer to connect their legacy backend services with the external world, such as Fintechs. This layer must be secure, not just a simple pass-through or gateway.

It must have all the capabilities of a management solution, handling all API calls with an API-first architectural design. Without an API-first approach, organizations can't connect with external parties, isolating them from the rest of the world.

An API gateway is essential for this, and it needs a management solution with a mediation layer, orchestration layer, security, and protocols. The solution must also support translation and mediation functionalities, such as easily converting JSON to XML and vice versa.

The solution, Gartner's top-ranked API management solution for seven consecutive years under Google Cloud, provides immense power and utilities.

There are three different deployment models. One is a completely SaaS-based. This deployment model is unique because organizations don't face any deployment challenges. Everything is deployed on Google Cloud, and the customer is securely connected via VPN, eliminating the need for on-prem deployment infrastructure costs. It's very user-friendly and cost-effective.

The next feature is the hybrid deployment model. This model's management layer is on the cloud, while the runtime is on-prem. This is ideal for banks or financial institutions that don't want their data on the cloud. They can keep their secure data on-prem while the management tasks, which don't require customer information, are handled in the cloud.

Then there's the on-prem solution. The versatility of the deployment models is a major feature. Another important feature is the security, traffic monitoring, analytics, and mediation layer. The solution's orchestration layer is robust, ensuring complete control of all API payload data. It offers analytics, security policies, and around 50 to 70 pre-built policies. Its low-code platform makes it easy for any software engineer to operate and manage within an organization. Policies can be applied to APIs through a simple drag-and-drop interface, and writing a policy is straightforward with pre-written codes and templates.

The third significant feature is the integrated developer portal. This portal provides developers with a smooth experience in utilizing APIs on the gateway. It offers an easy registration process, a comfortable API catalog, and a sandbox environment for testing and experimenting with APIs. These features, combined with the right orchestration layer, complete security protocols, drag-and-drop policy maintenance, and deployment versatility, make Apigee the number one ranked API management system in the industry.

The solution has an integrated developer portal that supports various content management systems like Drupal, Nginx, Angular, and more, allowing customized developer portals. For example, we recently built a dynamic, user-friendly developer portal for Network International, the largest payment integrator in the UAE, using Drupal. This portal is crucial in onboarding developers, showcasing APIs for fintech companies, and facilitating API monetization.

One feature of the developer portal is the version control mechanism, which keeps all previous versions alongside the latest ones. Another notable feature is multi-tenancy, which allows developers to select their region during registration and provides a consistent experience across different geographical placements.

The analytics and monitoring capabilities in Apigee enhance API performance enormously. You cannot manage your API layer effectively without the right analytics and monitoring tools. If you don't know which APIs are causing issues or spikes, you can't address them properly. For instance, a spike arrest policy helps by setting thresholds on certain APIs to prevent DDoS attacks and ensure resource utilization.

Apigee offers many out-of-the-box analytics and reports and the ability to build custom reports. These reports help you understand which APIs are used the most or the least, which generate more revenue, and which developers are most active.

The analytics also give a complete picture of developer engagement, showing which regions have the most active developers and which APIs are used the most in different geographical areas. This helps in managing the API ecosystem effectively.

Security analytics are also available, helping you monitor and address potential threats. The platform even provides monetization analytics, showing which APIs generate the most revenue.

GCP is improving the regular version control. There have been some challenges when we talk about the hybrid deployment model. For example, some runtime services' data was available only on the cloud, but financial institutions and other customers have requested more on-site data storage. This is especially important in regions where Google data centers are unavailable, such as certain areas in Africa, Asia, and the Middle East.

Google is working proactively to move more runtime services on-premise while keeping only the management services in the cloud. It is replacing competitors like IBM and MuleSoft in many organizations. 

Google's documentation side could be better, providing clearer and more comprehensive information for users. Improvements in supporting languages are also needed, such as better support for Java SDKs, which are not pre-built. Additionally, more pre-built policies need to be available.

While these features may not be available on other platforms either, Apigee, being ranked number one, can potentially exceed customer expectations. More customer-friendly deployment strategies for hybrid models, especially securing data and minimizing management plane interaction, could also be beneficial. Apigee already meets many of the finest requirements in the market for cloud-based solutions.

I have been using the product for more than a year. 

Once Google took over, the reputation of Google Cloud significantly boosted Apigee. It is a Google product, and Apigee will play a huge role in showcasing GCP products at the upcoming Google Next exhibition. With GCP's enhanced support backing the solution, stability challenges are a thing of the past. When we provide Apigee to an organization, it comes with GCP's enhanced support, including user-friendly SLAs and global support, ensuring queries are addressed promptly.

Google provides level one and level two support, ensuring SLAs are met. For level three support, professional service providers ensure the platform's stability and effectively handle downtime.

The solution is ideal for scalability because it is designed with an API-first architecture. It supports microservice-based architecture and integrates with Kubernetes platforms, which offer auto-scaling, auto-healing, and other resource management features. This makes Apigee crucial for organizations looking to advance their digital transformation.

GCP's support is top-notch. However, improvements need to be made to the SLAs. 

Positive

The number of resources needed depends on the deployment model. For the SaaS-based model, you typically need two to five highly skilled resources who understand GCP foundation, integration, and configuration. Building the product and organization on GCP is straightforward, but you need a skilled team.

For a cloud-based deployment model, neither a lot of time nor many resources are required. However, you need more resources and a higher skill set for a hybrid deployment. The most demanding is the OPDK (on-premise solution) deployment. This requires a complete Kubernetes team because you must set up bare metal machines or virtual machines, install Kubernetes, build clusters, and then deploy Apigee on those clusters. You also need to create and manage logical and physical environments.

It's not difficult to maintain because two types of major support are provided: GCP enhanced support, which is entirely platform-based, and level three support, which covers configuration and installation. The difficulty level increases with the complexity of the deployment model. Hybrid deployments are in the middle, while on-prem deployments have limitations and challenges.

The maintenance can be top-notch if you've got the right partner, like Abacus. We provide a one-month babysitting period for our clients to ensure everything runs smoothly, and we train their engineers to handle maintenance themselves if they don't need ongoing support. Maintenance varies based on the deployment design. For instance, maintaining an on-prem deployment on bare metal machines is easier than on virtual machines, but that's a bit more technical.

Apigee brings customers a significant return on investment. By implementing Apigee as their API management system, organizations can connect with the external world, collaborate with fintechs, and expand the reach of their services across various applications and platforms. This opens new revenue streams through the API economy, where APIs can be monetized. Every API call generates potential revenue, allowing organizations to capitalize on their digital assets.

The solution is a bit expensive. It's not for organizations in the early stages of their lifecycle but is more suited for mid- to enterprise-level platforms. Pricing varies by deployment model, with SaaS being the cheapest, costing around $100,000 per year for a subscription. For hybrid and on-prem deployments, the price increases. The on-prem model includes a license and additional installation and configuration professional service costs, which can be at least $40,000 to $60,000 for the initial setup. While it's not cheap, it offers long-term value and can be worthwhile.

I rate the overall product a ten out of ten. 

We work on open source and commercial integration tools like MuleSoft, Boomi, and Informatica. We recommend Apigee as one of the options for API management solutions due to cost efficiency. We are an integration service provider, and our customers look for cost-effective API management solutions.

Apigee provides catalog management, onboarding of new customers, an API portal, and security features. These are the functionalities that most of our customers are looking for when handling their traffic management and security needs. Despite the higher cost of Apigee, it is recommended for government organizations who prefer in-house solutions on their local servers. Apigee's analytics capabilities aid in monitoring and optimizing APIs, which are also beneficial for our operations.

I am not in a position to give any recommendations for additional features or improvements at this point.

The technical support for Apigee is good.

Positive

Deploying Apigee is straightforward and does not involve significant difficulties.

Apigee is costlier compared to other solutions. For government organizations, especially those that do not want cloud-based solutions and prefer on-premise implementations, we recommend WSO2 due to its cost-effectiveness and suitability for private cloud environments.

We work with integration tools like MuleSoft, Boomi, and Informatica. Some customers use Microsoft API management for small implementations and others prefer APIGEE.

I rate Apigee eight or nine out of ten. The ease of deployment and integration with other systems is satisfactory. Overall, while Apigee offers many valuable features, its high pricing can impact its adoption by cost-sensitive organizations. I rate the overall solution eight or nine out of ten.

We are implementing Oracle API Platform Cloud Service and using Apigee for enterprise solutions, particularly focusing on minimal technical dependency and integration capabilities suitable for banking and retail domains.

Our plan is to have Apigee and Oracle work together for our enterprise needs.

The drag-and-drop and click-through functionalities, alongside minimal code requirements, make Apigee valuable. It is intuitive and user-friendly.

There is potential for improvement in specific domain integrations, such as standard integration capabilities needed for banking or retail sectors.

Additionally, AI could be incorporated for more conversational APIs and to assist integration processes.

We have been using Apigee for more than a month.

We have not faced any stability issues with the solution so far.

We haven't tested scalability yet, but it is expected to be okay as Apigee is an industry leader.

Google's customer service has been very good and supportive. I haven't encountered any issues.

Positive

We have used solutions similar to Apigee in the past but did not provide specific names.

The initial setup was relatively straightforward and only took days.

Typically, one person is enough to deploy it with minimal dependency on technical teams.

I would rate it a nine out of ten.

It is mainly used for business applications.

Some of the essential aspects that organizations consider when selecting a product like ETG, which offers tracing tools, bug tracking, AI capabilities, scalability, and performance-related features, include strong community support. Having a robust community can be invaluable for finding solutions to various problems, especially during migrations and other challenges. Large companies tend to favor such products because of their established user communities and excellent support. While there may be alternative products with advanced API management features, they often fall short in terms of the support they provide, making products like Apigee a preferred choice.               

The product offers numerous features, but our organization primarily utilizes only a few of them. While I focus on the essential features required for my work, I'm aware that there are many other features within the product that I rarely or never use. Therefore, when evaluating the overall performance and capabilities of the product, it's not outstanding. The features we do find valuable work well, but there might be shortcomings in other areas. To provide meaningful feedback or identify weaknesses, I would need to have a comprehensive understanding of how the product supports a diverse range of customers and their experiences. Otherwise, it wouldn't be fair or practical to pinpoint specific issues.

I have been using Apigee for the past four years.

It is a stable product.

It is a scalable product.

I have used other solutions such as WS02 and Westworld API Management.

It is straightforward until and unless there aren’t any custom installations. Dealing with issues can be challenging, especially when custom installations are involved. Problems may arise with components not responding, leading to overall system malfunction. Installation failures, interruptions, and errors are common issues encountered in this context.

Normally it takes one to two hours. But when problems arise, it can take up to one week.

It is an expensive solution.

If you have numerous applications and high traffic, Apigee is a strong choice for its excellent features and outstanding performance. However, if your requirements are minimal and you don't need many features, there are other competitive API management products available. These alternatives can be more cost-effective. If you're looking for an open-source option and don't have critical applications that necessitate specific features, then Apigee is a suitable choice.

I would overall rate it an eight out of ten. 

Our main purpose of using Apigee is to standardize API development and management. It offers features like portal limits, rate limits, and OpenAPI specs for creating APIs securely. It ensures adherence to security rules before creating proxies on platforms.

The most valuable features of Apigee for me are analytics, security, ease of use, and integration capabilities. Additionally, built-in cache, Key-Value Maps, and Q-value mappings enhance performance and flexibility.

Apigee could improve by integrating with more identity providers and offering a default authentication module. This would streamline user authentication processes, allowing for easier integration with directory providers like Ping Server or Active Directory.

I have been working with Apigee for three years.

I would rate the stability of Apigee as a nine out of ten.

I would rate the scalability of Apigee as a seven out of ten.

Tech support for Apigee has been somewhat delayed at times, requiring escalation for prompt assistance. There were instances where we had to wait for a few days before receiving a response from the support team. I would rate the support as a seven out of ten.

Neutral

Apigee deployment is straightforward, though it can take some time, especially with added security measures. Maintenance is easy, with good support from the team.

Apigee is expensive with a yearly license.

Apigee analytics provides insights into API response times, error rates, and performance. It helps identify areas for improvement and troubleshoot issues, enhancing overall API performance monitoring.

Apigee supported our organization in meeting compliance and regulatory requirements by customizing the tool to align with our specific needs. They guided the building and implementation of solutions according to our compliance standards.

Before using Apigee, consider your organization's security and compliance requirements, especially if they are strict. Evaluate if Apigee aligns with the regulations of your country or location.

Overall, I would rate Apigee as an eight out of ten.

The bank embarked on a journey towards open banking solutions, particularly in the realm of online banking and medical services. This initiative prompted the need for a gateway solution, and after careful consideration, the bank chose Apigee as its API management platform. Since then, the collaboration with Apigee has proven beneficial, leading to ongoing improvements and learning experiences for the teams involved.

We find great value in the ability to segregate distinct projects within the system and extract security statistics. Its flexibility allows seamless management of different products, showcasing scalability to handle extensive solutions. Whether dealing with hundreds or thousands of nickel services, this configuration enables us to sustain ongoing work effectively, ensuring real and efficient management of diverse IT projects.

Our focus on improvement primarily revolves around security, differing somewhat from the Connect endpoint. We've encountered challenges in leveraging Connect functionality, prompting us to explore additional tools, such as Fergus, to address implementation and security issues.

I have been working with it for four years.

The stability issue occurred once in a real-life scenario at the bank, causing a downtime of approximately one hour, leaving the entire bank without internet access. This incident was not typical of a bank, and other companies might view it as an isolated event. Occasionally, a service may slow down due to factors like migration, causing disruptions within the timeframe of a timeout.

The system is scalable; however, achieving scalability involves updating numerous properties and parameters. While it is manageable, the learning curve proved significant, and we gained insights through collaboration with a team of three during the development process.

The initial setup is relatively complex. While it may require learning, trial, and understanding, once you reach an advanced level, it becomes a more personalized experience.

The deployment process involves sharing JSON or Slack commands, and the subsequent steps are then taken over by the company from the Apigee, initiating the process from scratch or refreshing it.

Overall, I would rate it seven out of ten.