<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on cloudmato.com</title><link>https://cloudmato.com/tags/networking/</link><description>Recent content in Networking on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Sun, 14 Jun 2026 18:01:15 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Understanding HTTP/3: Is It Really Better Than HTTP/2?</title><link>https://cloudmato.com/posts/understanding-http3-vs-http2-http1/</link><pubDate>Sun, 14 Jun 2026 18:01:15 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/understanding-http3-vs-http2-http1/</guid><description>&lt;p&gt;Everyone talks about HTTP/3 like it&amp;rsquo;s a free speed upgrade you flip on and forget. It mostly is — but &amp;ldquo;mostly&amp;rdquo; is doing a lot of work in that sentence. HTTP/3 is now used for roughly 35% of all web requests globally [1], so this isn&amp;rsquo;t a research toy anymore. The thing is, almost no one explains &lt;em&gt;why&lt;/em&gt; it&amp;rsquo;s faster, where it actually loses to HTTP/2, and — the question nobody asks — whether your particular site even benefits. Let me walk through it the way I&amp;rsquo;d explain it to a friend over chai.&lt;/p&gt;</description></item><item><title>DNS Records Explained: Why So Many Types Exist (Timeline)</title><link>https://cloudmato.com/posts/dns-records-explained-types-timeline/</link><pubDate>Fri, 12 Jun 2026 10:24:26 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/dns-records-explained-types-timeline/</guid><description>&lt;p&gt;Open up any domain&amp;rsquo;s DNS settings and you&amp;rsquo;ll see a wall of cryptic codes — A, AAAA, MX, TXT, SRV, CAA, SVCB — and it genuinely looks like someone kept bolting random parts onto an old engine. Which, honestly, is &lt;strong&gt;exactly&lt;/strong&gt; what happened. Every single one of these record types exists because the internet hit a wall that the existing records couldn&amp;rsquo;t get past, and once you see that history laid out, the whole mess actually starts to make sense.&lt;/p&gt;</description></item><item><title>What Are WebSockets and How Do They Differ From HTTP?</title><link>https://cloudmato.com/posts/what-are-websockets-vs-http/</link><pubDate>Mon, 08 Jun 2026 10:04:50 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/what-are-websockets-vs-http/</guid><description>&lt;p&gt;I kept hearing &amp;ldquo;use WebSockets for real-time stuff&amp;rdquo; without anyone explaining what actually happens on the wire. So I went and read the RFC, poked at a few servers, and figured I&amp;rsquo;d write down what I found — including the part that confused me the most: whether WebSocket is a protocol of its own or just some clever trick on top of HTTP.&lt;/p&gt;
&lt;h2 class="header-anchor-wrapper"&gt;So what is a WebSocket?
&lt;a href="#so-what-is-a-websocket" class="header-anchor-link"&gt;
&lt;svg
xmlns="http://www.w3.org/2000/svg"
width="1rem" height="1rem" viewBox="0 0 24 24" fill="none"
stroke="currentColor" stroke-width="2" stroke-linecap="round"
stroke-linejoin="round"&gt;
&lt;line x1="4" y1="9" x2="20" y2="9"&gt;&lt;/line&gt;&lt;line x1="4" y1="15" x2="20" y2="15"&gt;&lt;/line&gt;&lt;line x1="10" y1="3" x2="8" y2="21"&gt;&lt;/line&gt;&lt;line x1="16" y1="3" x2="14" y2="21"&gt;&lt;/line&gt;
&lt;/svg&gt;
&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;A &lt;strong&gt;WebSocket is a persistent, full-duplex communication channel between a browser (or any client) and a server, opened over a single TCP connection&lt;/strong&gt; [1]. Full-duplex means both sides can send messages whenever they want — not just in response to a request. That&amp;rsquo;s the part that breaks the usual mental model of the web.&lt;/p&gt;</description></item><item><title>TLS Termination Explained (and Is SSL Really Transport Layer?)</title><link>https://cloudmato.com/posts/tls-termination-explained/</link><pubDate>Sun, 07 Jun 2026 16:16:06 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/tls-termination-explained/</guid><description>&lt;p&gt;Two questions get mashed together constantly: &amp;ldquo;what is TLS termination&amp;rdquo; and &amp;ldquo;is SSL a transport layer thing?&amp;rdquo; People assume the answer to the second is obviously yes — it&amp;rsquo;s literally called &lt;em&gt;Transport&lt;/em&gt; Layer Security, right? Well. That naming has fooled a lot of smart people, and the confusion bleeds straight into how folks reason about termination. So let me untangle both, because once the layer question clicks, termination stops feeling like magic.&lt;/p&gt;</description></item><item><title>Kubernetes Load Balancers: Inside, Outside, or Both?</title><link>https://cloudmato.com/posts/kubernetes-load-balancer-options/</link><pubDate>Thu, 04 Jun 2026 15:30:08 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/kubernetes-load-balancer-options/</guid><description>&lt;p&gt;Everyone setting up a Kubernetes cluster eventually hits the same wall: how do I actually get traffic into this thing? Then the docs mention ClusterIP, NodePort, LoadBalancer, Ingress, Gateway API, MetalLB — and it spirals. Worse, there&amp;rsquo;s a Service &lt;em&gt;type&lt;/em&gt; called &amp;ldquo;LoadBalancer&amp;rdquo; and there are actual load balancers, and they are not the same thing. Let me go through the real options, where each one sits in the stack, and what genuinely makes sense to reach for.&lt;/p&gt;</description></item></channel></rss>