<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tcp on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/tcp/</link>
    <description>Recent content in Tcp on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/tcp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted TCP Load Balancing — HAProxy TCP Mode vs Nginx Stream vs Envoy TCP Proxy</title>
      <link>https://www.pistack.xyz/posts/2026-05-20-self-hosted-tcp-load-balancing-haproxy-nginx-envoy-guide/</link>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-20-self-hosted-tcp-load-balancing-haproxy-nginx-envoy-guide/</guid>
      <description>&lt;p&gt;While HTTP load balancing gets most of the attention, many critical services operate at the TCP layer — databases, message queues, game servers, and custom protocols. When you need to distribute raw TCP traffic across backend servers without inspecting the application payload, three open-source tools stand out: &lt;strong&gt;HAProxy TCP mode&lt;/strong&gt;, &lt;strong&gt;Nginx stream module&lt;/strong&gt;, and &lt;strong&gt;Envoy TCP proxy&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
