API Gateway Migration
Migration from Google Apigee to Kong, including custom gateway and plugin development.
Problem
Reduce vendor lock-in and gain flexibility over gateway behavior that a managed product could not offer.
Architecture
Kong as the edge gateway with custom plugins for authentication, transformation, and policy enforcement, fronting internal services.
Technical challenges
Achieving behavioral parity with the existing gateway, migrating routes safely, and extending the gateway with custom logic.
Solution
Route-by-route migration with parity checks, custom Kong plugins for platform-specific needs, and staged rollout to limit blast radius.
Scale
Fronts platform-wide API traffic.
Lessons learned
Owning the gateway layer unlocked platform capabilities, but parity and staged rollout were essential to migrate safely.
Want to talk through the engineering behind systems like this?
Start a conversation