<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bunny-Net on Kuldeep Pisda</title><link>https://kdpisda.in/tag/bunny-net/</link><description>Recent content in Bunny-Net on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 16 May 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/bunny-net/index.xml" rel="self" type="application/rss+xml"/><item><title>Syncing Two Object Stores: Migrating Terabytes While Users Stream</title><link>https://kdpisda.in/syncing-two-object-stores-live-media-migration/</link><pubDate>Sat, 16 May 2026 10:00:00 +0530</pubDate><guid>https://kdpisda.in/syncing-two-object-stores-live-media-migration/</guid><description>&lt;p&gt;The last chapter ended with a decision, not an action. We had outgrown the Wasabi-plus-Cloudflare stack that had saved us a small fortune, and I had picked Bunny.net — Bunny Storage for the files, Bunny CDN in front — as the place our 3.5 TB of media was going to live. Deciding is the easy part. The hard part is the sentence I had to say next: &lt;em&gt;we are going to move roughly 3.5 terabytes of video from one object store to another, and at no point during that move can a single one of our 30,000 users notice.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>The 3.5 TB Reckoning: Our Cheapest Setup Was Our Biggest Risk</title><link>https://kdpisda.in/the-3-5-tb-reckoning-moving-to-bunny/</link><pubDate>Sat, 09 May 2026 10:00:00 +0530</pubDate><guid>https://kdpisda.in/the-3-5-tb-reckoning-moving-to-bunny/</guid><description>&lt;p&gt;For about eighteen months, the cheapest line on our infrastructure bill was also the most dangerous one. Our media stack — Wasabi for object storage, Cloudflare in front of it as the CDN, and a 600-dollar Ubuntu desktop with an NVIDIA card quietly transcoding video in the corner of an office — was saving us thousands of dollars a month over the AWS setup it replaced. It was also, at roughly 3.5 TB of media and 30,000 users, quietly becoming the wrong &lt;em&gt;shape&lt;/em&gt; for every vendor whose plan it leaned on.&lt;/p&gt;</description></item></channel></rss>