<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Api-Proxy on Kuldeep Pisda</title><link>https://kdpisda.in/tag/api-proxy/</link><description>Recent content in Api-Proxy on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 18 Jan 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/api-proxy/index.xml" rel="self" type="application/rss+xml"/><item><title>The Hack in Front of the CMS: A Cache and a Checkout on Directus</title><link>https://kdpisda.in/fastapi-proxy-directus-caching-ccavenue/</link><pubDate>Sun, 18 Jan 2026 10:00:00 +0530</pubDate><guid>https://kdpisda.in/fastapi-proxy-directus-caching-ccavenue/</guid><description>&lt;h2 id="the-success-problem-up-close"&gt;The success problem, up close&lt;a class="heading-anchor" href="#the-success-problem-up-close" aria-hidden="true" tabindex="-1"&gt;#&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Chapter 1 ended on a good note with a nasty tail. The throwaway MVP on Directus worked — people came back, finished long talks, and we were climbing toward roughly 2,000 users. But the same thing that proved the bet started to hurt. As traffic grew, the API responses coming out of the CMS got heavy and slow, and the app began to feel sticky on exactly the cheap Android phones our audience actually used.&lt;/p&gt;</description></item></channel></rss>