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 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…
Van Maseey·Jul 27Switching from Claude to Kimi K3: A Developer’s Migration Guide (API, Prompts, and Tooling)Claude has been the gold standard for reasoning-heavy developer workflows — code generation, architecture design, and long-form analysis…
InLevel Up CodingbyGirish Dhamane·Jan 7Kill Your Legacy API Without Breaking Things.Your old API is a ghost that haunts your development velocity. Here’s how to exorcise it.
Rachit·Jan 2From MuleSoft to Azure: Practical Learnings from a Large-Scale API MigrationMigrating APIs is rarely just a technical task. It’s part archaeology, part guesswork, and part decision-making under uncertainty…A response icon1
