<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Load-Balancing on Home</title><link>http://www.bala-krishnan.com/tags/load-balancing/</link><description>Recent content in Load-Balancing on Home</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 17 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://www.bala-krishnan.com/tags/load-balancing/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a load balancer in Go, part 1</title><link>http://www.bala-krishnan.com/posts/24-steer-load-balancer/</link><pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate><guid>http://www.bala-krishnan.com/posts/24-steer-load-balancer/</guid><description>I&amp;rsquo;ve spent a lot of time on the operating side of load balancers. I&amp;rsquo;ve read NGINX configs, stared at ALB target group health, and wondered why one pod was getting all the traffic. But I&amp;rsquo;d never actually written one. So I&amp;rsquo;ve started building a small HTTP load balancer in Go called steer, in phases, so I can understand each piece before adding the next one.
This post is about phase 1, which is the smallest possible version: a load balancer with exactly one backend.</description></item></channel></rss>