Googlers is a company that creates products intended to create opportunities for an extensive audience, regardless of their location across the globe. The company values diverse perspectives, imaginations and non-conformity to predefined norms and impossibilities. The goal is to build products while incorporating uniqueness of each individual involved in this process, aiming to make their products accessible and useful to all.
Do You Manage Peer Insights at Google?
Access Vendor Portal to update and manage your profile.
One of Apigee's biggest strengths was how it combined most of the essential API management capabilities in a single soltution. You can design, secure, deploy, and analyze APIs without having to rely on multiple tools. Security features like OAuth and traffic policies were straightforward to implement, and the built-in analytics provided valuable insights into usage patterns. Its integration with Google Cloud alo made it relatively easy to manage APIs across different environments.
Apigee simplifies API security and management with built in features, eliminating custom coding needs. it offers time saving design tools and enables flexible context bases call routing enhancing overall API efficiency and development.
1. Policy-driven protection. This makes it simple and straightforward to enforce multiple types of authentication and a variety of traffic controls at the gateway layer, rather than having to write and push that logic onto every service in your stack. 2. Threat Protection w/ OWASP aligned controls. The built-in policies focused on the OWASP API Top 10 Risks helped us to mitigate actual risk without spending endless cycles churning over security controls. 3. Governance for multi-team programs. The ability to implement RBAC with Apigee's proxy/product model helped us to separate responsibilities cleanly within the management tool. It's always a plus when a security product follows security principles.
When we first started with Apigee, the learning curve was quite steep, especially for teams without prior experience with API gateways. Over time, we also found that some of our advanced use cases - such as deep system integrations and complex hybrid deployments - were difficult to implement without significant customization. As our API ecosystem grew, the cost model also became a bigger consideration. Additionally, the user interface and developer portal, while functional, sometimes felt less intuitive than we expected.
Apigee pricing model can be expensive for high volume use, with addes costs for advanced features. Its limited customization options for performance and specific issues pose challenges
1. As with any tool like this, there is often a risk of policy sprawl. Given the amount of customization that is available, it can be easy to get lost in the weeds setting up per-proxy rules. 2. Tuning rate limiting is a powerful feature set, but it is finicky and needs to be implemented carefully to consider burst traffic. 3. The biggest issue, however, is that it is expensive. The base API management pricing is not bad, but specifically with the Advanced API Security if you have multiple environments with high traffic loads your costs can quickly exceed your initial expectations.