<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Devops on Ansh Wasan</title>
    <link>/tags/devops/</link>
    <description>Recent content in Devops on Ansh Wasan</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>© {year}</copyright>
    <lastBuildDate>Wed, 14 Jan 2026 21:31:26 +0530</lastBuildDate>
    <atom:link href="/tags/devops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Docker for Backend Developers: A Practical Guide</title>
      <link>/blog/docker-for-backend-developers/</link>
      <pubDate>Sun, 15 Dec 2024 00:00:00 +0530</pubDate>
      <guid>/blog/docker-for-backend-developers/</guid>
      <description>Docker has revolutionized how we develop, ship, and run applications. As a backend developer, understanding Docker is essential. Let&amp;rsquo;s explore how to containerize your backend apps.&#xA;Why Docker? &amp;ldquo;It works on my machine&amp;rdquo; - We&amp;rsquo;ve all heard this. Docker solves this by packaging your application with all its dependencies.&#xA;┌─────────────────────────────────────┐ │ Docker Container │ ├─────────────────────────────────────┤ │ Your Application │ │ Runtime (Node.js, Python, Java) │ │ Dependencies │ │ System Libraries │ │ OS (Linux) │ └─────────────────────────────────────┘ Core Concepts Images vs Containers Image → Blueprint (like a class) Container → Running instance (like an object) Dockerfile A Dockerfile is your recipe for building an image:</description>
    </item>
  </channel>
</rss>
