Shubhojit Dasgupta·Oct 16Four Problems Every Apigee-to-Kong Migration Must SolveThe series map: eleven posts in four arcs, each arc one category of problem a large Apigee exit has to solve, and where to start
Shubhojit Dasgupta·Oct 16Custom Plugins Are a Presales DecisionThe plugin budget is fixed before the project starts: a decision ladder for every “we need a custom plugin”, and what to do when you need…
Shubhojit Dasgupta·Oct 16Two Pipelines, One GatewayA spec pipeline that only commits, a policy pipeline that patches and deploys, and tagged lanes so no sync deletes another team’s work
Karim Moussa·Oct 14How to deploy Highly Available Kong API Gateway ?Kong API Gateway, highly available, on plain VMs
Shubhojit Dasgupta·Oct 13Token Exchange in an Apigee ExitHow partners keep their own identity provider when Apigee’s OAuth goes, why Kong should verify their tokens before exchanging them, and the…
Shubhojit Dasgupta·Oct 13Two Credential Bridges: Verifying Against Apigee or Holding Credentials in KongMoving partners onto Kong before their Apigee credentials change: verify the key at Apigee, or hold it in Kong
Shubhojit Dasgupta·Oct 13Products Before AppsMapping Apigee API Products and credentials into Kong once, before the first partner moves
Shubhojit Dasgupta·Oct 8When the Credentials Live in the IdP, Not KongZitadel tokens in Kong: per-route scopes, tier quotas and the revocation window
Shubhojit Dasgupta·Oct 8The Real IP Isn’t the Real CallerClosing the identity loop for partner rate limits in Kong behind F5
Shubhojit Dasgupta·Oct 5When a CDN or WAF Sits in Front of F5Keeping client IPs trustworthy in Kong as the proxy chain and the trusted ranges grow
