<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Video-Streaming on Kuldeep Pisda</title><link>https://kdpisda.in/tag/video-streaming/</link><description>Recent content in Video-Streaming on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 11 Apr 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/video-streaming/index.xml" rel="self" type="application/rss+xml"/><item><title>The 1,500 Dollar Day: The Egress Bill That Reframed Our Whole Strategy</title><link>https://kdpisda.in/the-1500-dollar-cloudfront-egress-bill/</link><pubDate>Sat, 11 Apr 2026 10:00:00 +0530</pubDate><guid>https://kdpisda.in/the-1500-dollar-cloudfront-egress-bill/</guid><description>&lt;p&gt;When I moved transcoding to AWS MediaConvert, I wrote — almost as a footnote — that I had traded a compute problem for a bill I now had to watch. The compute problem was solved: uploads encoded in parallel, the queue stopped climbing, my Celery workers went back to doing app work. The bill was the part I had waved at and moved past. This chapter is that footnote coming to collect.&lt;/p&gt;</description></item><item><title>A 20-Minute Video Weighed 1.2 GB, So We Built Our Own Streaming</title><link>https://kdpisda.in/in-house-video-streaming-ffmpeg-s3-cloudfront-ecs/</link><pubDate>Sat, 28 Mar 2026 10:00:00 +0530</pubDate><guid>https://kdpisda.in/in-house-video-streaming-ffmpeg-s3-cloudfront-ecs/</guid><description>&lt;p&gt;The last stretch of work made the platform quick — a heavy course page that used to take thirty seconds now answered in about two hundred milliseconds, and the API felt solid enough to build real features on. So we finally turned to the thing we had been deliberately ignoring since the very early days: video. Back when we were still proving people would pay, I had left a landmine in the product on purpose. A single 20-minute course lesson was a 1.2 GB HD file, and we served that same giant file to everyone.&lt;/p&gt;</description></item><item><title>The 1.2 GB Video We Chose Not to Fix</title><link>https://kdpisda.in/the-video-we-chose-not-to-fix/</link><pubDate>Wed, 28 Jan 2026 10:00:00 +0530</pubDate><guid>https://kdpisda.in/the-video-we-chose-not-to-fix/</guid><description>&lt;p&gt;The FastAPI proxy had done exactly what I built it to do. It kept the course screen fast, bolted CCAvenue payments onto the edge, and carried us from 2,000 users to roughly 6,000 in three months with about one in ten paying. But the proxy fixed the wrong end of the pipe. It made the &lt;em&gt;metadata&lt;/em&gt; fast. It did nothing for the thing users actually came for: the video. And the video had a problem I could not cache my way out of.&lt;/p&gt;</description></item></channel></rss>