<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes on Gaurav.dev</title><link>/tags/kubernetes/</link><description>Recent content in Kubernetes on Gaurav.dev</description><generator>Hugo</generator><language>en-US</language><copyright>© 2026 Gaurav. Built with care and clean code.</copyright><lastBuildDate>Sat, 30 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Containers, Serverless, or Edge: Put Each Workload in the Right Place</title><link>/posts/containers-serverless-edge-deployment/</link><pubDate>Sat, 30 May 2026 00:00:00 +0000</pubDate><guid>/posts/containers-serverless-edge-deployment/</guid><description>&lt;p&gt;Modern applications rarely need one universal deployment model. A web frontend, webhook handler, scheduled pipeline, inference service, and long-running worker behave differently. Containers, serverless functions, and edge runtimes are tools for placing those workloads where their operational characteristics fit.&lt;/p&gt;&#10;&lt;h2 id="containers-a-portable-unit-of-execution"&gt;Containers: a portable unit of execution&lt;/h2&gt;&#10;&lt;p&gt;Docker packages an application with its runtime and system dependencies, making development, CI, and production more consistent. Containers suit APIs, workers, scheduled jobs, and services with predictable resource needs. They allow control over process behaviour, networking, files, and dependencies without coupling the application completely to one platform.&lt;/p&gt;</description></item></channel></rss>