<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>K8s on nyadgar.com</title>
		<link>https://nyadgar.com/tags/k8s/</link>
		<description>Recent content in K8s on nyadgar.com</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 20 Jan 2025 15:50:12 +0200</lastBuildDate>
		
			<atom:link href="https://nyadgar.com/tags/k8s/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Scaling gRPC With Kubernetes (Using Go)</title>
				<link>https://nyadgar.com/posts/scaling-grpc-with-kubernetes-using-go/</link>
				<pubDate>Mon, 20 Jan 2025 15:50:12 +0200</pubDate>
				<guid>https://nyadgar.com/posts/scaling-grpc-with-kubernetes-using-go/</guid>
				<description>&lt;h2 id=&#34;the-tech&#34;&gt;The Tech&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://grpc.io/&#34;&gt;&lt;code&gt;gRPC&lt;/code&gt;&lt;/a&gt; is a strong player in microservices-based systems.&#xA;Leveraging &lt;a href=&#34;https://protobuf.dev/&#34;&gt;Protocol Buffers&lt;/a&gt; for well-defined API contracts,&#xA;fast serialization (about &lt;code&gt;X5&lt;/code&gt; faster than &lt;code&gt;JSON&lt;/code&gt;), smaller payloads, and the use&#xA;of streams (thanks to &lt;code&gt;HTTP/2&lt;/code&gt;). It&amp;rsquo;s easy to see why this technology for&#xA;real-time microservice communication is a good choice.&lt;/p&gt;&#xA;&lt;h3 id=&#34;http2&#34;&gt;HTTP/2&lt;/h3&gt;&#xA;&lt;p&gt;Unlike a typical REST API that&amp;rsquo;s built on top of &lt;code&gt;HTTP/1.1&lt;/code&gt;, &lt;code&gt;gRPC&lt;/code&gt; is built on top of&#xA;&lt;code&gt;HTTP/2&lt;/code&gt;. The most noticeable feature of &lt;code&gt;HTTP/2&lt;/code&gt; is the ability to perform &lt;em&gt;server push&lt;/em&gt;.&#xA;This feature allows servers to asynchronously &lt;em&gt;push&lt;/em&gt; data to the client before the client&#xA;asks for it. &lt;code&gt;gRPC&lt;/code&gt; leverages &lt;em&gt;server push&lt;/em&gt; to support &lt;em&gt;streams&lt;/em&gt;, a key feature that separates &lt;code&gt;gRPC&lt;/code&gt;&#xA;from any other &lt;code&gt;HTTP/1.1&lt;/code&gt;-based API. Because of that, &lt;code&gt;HTTP/2&lt;/code&gt;&#xA;requires a long-lasting &lt;code&gt;TCP&lt;/code&gt; connection between the client and the server.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
