<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Tech Blogs on Ishan Jain</title>
		<link>https://www.bloodraven.in/writing/</link>
		<description>Recent content in Tech Blogs on Ishan Jain</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Thu, 30 Jul 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.bloodraven.in/writing/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>From Huffman to OpenObserve: Why Your 10GB Log File Fits in 3GB</title>
				<link>https://www.bloodraven.in/writing/from-huffman-to-openobserve-why-your-10gb-log-file-fits-in-3gb/</link>
				<pubDate>Thu, 30 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://www.bloodraven.in/writing/from-huffman-to-openobserve-why-your-10gb-log-file-fits-in-3gb/</guid>
				<description>&lt;p&gt;Every SRE has run &lt;code&gt;gzip&lt;/code&gt; on a log file and watched 10GB collapse into 3GB. It feels like magic. It is not. It is a handful of very old, very simple ideas about redundancy, and once you understand them, the storage numbers behind modern observability tools stop looking like marketing and start looking like arithmetic.&lt;/p&gt;&#xA;&lt;p&gt;Let me walk from first principles up to how a tool like OpenObserve turns those principles into a 140x cost gap.&lt;/p&gt;</description>
			</item>
			<item>
				<title>One Valkey, Multiple Tenants: Per-Database Isolation on Kubernetes</title>
				<link>https://www.bloodraven.in/writing/one-valkey-multiple-tenants-per-database-isolation-on-kubernetes/</link>
				<pubDate>Wed, 27 May 2026 00:00:00 +0000</pubDate>
				<guid>https://www.bloodraven.in/writing/one-valkey-multiple-tenants-per-database-isolation-on-kubernetes/</guid>
				<description>How Valkey 9.1.0&amp;rsquo;s per-database ACL selector lets you run multiple microservices off one shared cache instance, with hard access boundaries between them.</description>
			</item>
			<item>
				<title>Stop Asking for a DevOps Roadmap. Read This Instead</title>
				<link>https://www.bloodraven.in/writing/stop-asking-for-a-devops-roadmap.-read-this-instead/</link>
				<pubDate>Tue, 19 May 2026 10:00:00 +0530</pubDate>
				<guid>https://www.bloodraven.in/writing/stop-asking-for-a-devops-roadmap.-read-this-instead/</guid>
				<description>&lt;h2 id=&#34;stop-asking-for-a-devops-roadmap-read-this-instead&#34;&gt;Stop Asking for a DevOps Roadmap. Read This Instead&lt;a class=&#34;heading-anchor&#34; href=&#34;#stop-asking-for-a-devops-roadmap-read-this-instead&#34; aria-label=&#34;Link to this section&#34;&gt;&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;People who reach out to me and ask &amp;ldquo;give us a roadmap of becoming a DevOps engineer&amp;rdquo; or &amp;ldquo;what was your roadmap&amp;rdquo; - I go blank. What was my roadmap? I end up saying: learn Docker, K8s, Terraform, or AWS.&lt;/p&gt;&#xA;&lt;p&gt;So I sat down and wrote my thoughts. If I needed to start again with no memory of being a DevOps engineer and read this blog, I should be able to get all the skills required to be good enough.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The Curious Case of Docker Hardened Images</title>
				<link>https://www.bloodraven.in/writing/the-curious-case-of-docker-hardend-images/</link>
				<pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate>
				<guid>https://www.bloodraven.in/writing/the-curious-case-of-docker-hardend-images/</guid>
				<description>An investigative look at Docker Hardened Images: what changed in December 2025, how DHI compares to distroless and Wolfi, and what the operational tax really looks like.</description>
			</item>
			<item>
				<title>The Curious Case of Request and Limit on AWS EKS Fargate</title>
				<link>https://www.bloodraven.in/writing/the-curious-case-of-request-and-limit-on-aws-eks-fargate/</link>
				<pubDate>Sun, 02 Nov 2025 14:53:00 +0530</pubDate>
				<guid>https://www.bloodraven.in/writing/the-curious-case-of-request-and-limit-on-aws-eks-fargate/</guid>
				<description>&lt;p&gt;If you&amp;rsquo;re running containers on AWS EKS with Fargate, you might have encountered a surprising reality about how billing works. Let me share a scenario that trips up many engineers:&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-scenario&#34;&gt;The Scenario&lt;a class=&#34;heading-anchor&#34; href=&#34;#the-scenario&#34; aria-label=&#34;Link to this section&#34;&gt;&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;You have a pod with the following resource specifications:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code class=&#34;language-yamlThe&#34; data-lang=&#34;yamlThe&#34;&gt;resources:&#xA;  requests:&#xA;    cpu: 100m&#xA;    memory: 500Mi&#xA;  limits:&#xA;    cpu: 4000m&#xA;    memory: 8000Mi&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;At first glance, you might think: &amp;ldquo;Great! My pod will use minimal resources (100m CPU, 500Mi memory) but can burst up to 4 vCPUs and 8GB when needed.&amp;rdquo;&lt;/p&gt;</description>
			</item>
			<item>
				<title>The Most Practical Way to Get Started on AWS: Build a Producation Grade Cloud Setup</title>
				<link>https://www.bloodraven.in/writing/the-most-practical-way-to-get-started-on-aws-build-a-producation-grade-cloud-setup/</link>
				<pubDate>Wed, 17 Sep 2025 10:00:00 +0530</pubDate>
				<guid>https://www.bloodraven.in/writing/the-most-practical-way-to-get-started-on-aws-build-a-producation-grade-cloud-setup/</guid>
				<description>&lt;h2 id=&#34;the-most-practical-way-to-get-started-on-aws-build-a-producation-grade-cloud-setup&#34;&gt;The Most Practical Way to Get Started on AWS: Build a Producation Grade Cloud Setup&lt;a class=&#34;heading-anchor&#34; href=&#34;#the-most-practical-way-to-get-started-on-aws-build-a-producation-grade-cloud-setup&#34; aria-label=&#34;Link to this section&#34;&gt;&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;When people say ‘learn AWS,’ it’s easy to get lost in a sea of services. In reality, most real-world architectures start with a VPC, subnets, instances, storage, and permissions.&lt;br&gt;&#xA;In this guide, we’ll build a secure, production-style setup step-by-step — and we’ll do it four ways:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;AWS Console&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;AWS CLI&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Bash Automation Scripts&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Terraform&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;what-you-will-gain-after-doing-this&#34;&gt;What You Will Gain After Doing This&lt;a class=&#34;heading-anchor&#34; href=&#34;#what-you-will-gain-after-doing-this&#34; aria-label=&#34;Link to this section&#34;&gt;&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Hands-on experience with core AWS services&lt;/li&gt;&#xA;&lt;li&gt;Learn how to automate (CLI, scripts, Terraform)&lt;/li&gt;&#xA;&lt;li&gt;Cover security best practices (bastion, private DB, IAM roles, S3 VPC endpoints)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;aws-architecture-diagram&#34;&gt;AWS Architecture Diagram&lt;a class=&#34;heading-anchor&#34; href=&#34;#aws-architecture-diagram&#34; aria-label=&#34;Link to this section&#34;&gt;&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://www.bloodraven.in/images/aws-architecture.png&#34;&#xA;     alt=&#34;AWS Architecture&#34;&#xA;     loading=&#34;lazy&#34; decoding=&#34;async&#34;&gt;&#xA;&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
