Apigee Accelerator
A self-service dashboard for viewing and safely changing Apigee quota configuration, with built-in governance and automatic expiry of temporary changes.
The Problem
Engineers managing API rate limits across dozens of Apigee environments had to hand-edit key-value maps and dig through Git-stored proxy configs just to check or change a quota — with no governance over who changed what or whether temporary increases ever got reverted.
Why Traditional Systems Failed
Existing tools forced a choice: give everyone admin access to complex consoles (risky) or gate everything behind a few experts (bottleneck). Manually edited KVMs and static documentation had no audit trail and no way to guarantee a "temporary" quota bump was ever rolled back.
Solution Architecture
A Flask dashboard backed by two integrations: the Apigee Management API for reading and writing quota key-value maps and computing tiered rate limits (custom > tier 1-3 > default), and Git for both configuration source-of-truth (proxy XML: timeouts, payload limits, load-balancer settings) and an audit trail of every quota change with its requester and expiry. Every data fetch also checks for expired temporary grants and automatically reverts them to default limits, logging the revert.
Interactive Architecture
Hover a node for detail · click to isolate its connections
Dashboard
Core Service
Backends
Every fetch also checks for expired temporary grants and reverts them automatically, logging the revert.
Business Value
Became the self-service system of record for API quota changes across the environment fleet, replacing manual KVM edits with a governed workflow that has a full audit trail and never leaves a forgotten temporary rate-limit increase in place.
Key Learnings
- A write path needs the same governance discipline as a read-only dashboard — every change is logged with who, why, and an expiry, not just applied.
- Auto-expiry is more valuable than manual review: checking for and reverting expired grants on every read keeps configuration honest without relying on anyone remembering to clean up.
- Git works well as both a config source-of-truth and an audit ledger, avoiding the need for a separate database for this workload.