<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Lvs on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/lvs/</link>
    <description>Recent content in Lvs on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 11 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/lvs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted LVS Load Balancing: IPVS, Keepalived, and Linux Virtual Server (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-11-self-hosted-lvs-load-balancing-ipvs-keepalived-linux-virtual-server-guide/</link>
      <pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-11-self-hosted-lvs-load-balancing-ipvs-keepalived-linux-virtual-server-guide/</guid>
      <description>&lt;p&gt;When your application outgrows a single server, load balancing becomes the critical infrastructure layer that distributes traffic across multiple backend nodes. While solutions like HAProxy, NGINX, and Envoy dominate the Layer 7 (application layer) conversation, the Linux kernel includes a powerful Layer 4 (transport layer) load balancer that handles billions of packets per second with near-zero overhead: &lt;strong&gt;Linux Virtual Server (LVS)&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
