<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sidecar-Proxy on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/sidecar-proxy/</link>
    <description>Recent content in Sidecar-Proxy on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/sidecar-proxy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Service Mesh Sidecar Proxies: Envoy vs Linkerd2-proxy vs NGINX Data Plane</title>
      <link>https://www.pistack.xyz/posts/2026-06-01-self-hosted-sidecar-proxies-envoy-linkerd-nginx-guide/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-01-self-hosted-sidecar-proxies-envoy-linkerd-nginx-guide/</guid>
      <description>&lt;p&gt;Service meshes separate network concerns from application code by injecting a sidecar proxy alongside each service instance. This proxy handles service discovery, load balancing, TLS termination, observability, and traffic control — all without modifying your application. But under the hood, these capabilities depend on the sidecar proxy itself.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
