<?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 KSC</title>
		<link>https://sckwon.dev/en/tags/devops/</link>
		<description>Recent content in Devops on KSC</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Sat, 11 Jul 2026 09:00:00 +0900</lastBuildDate>
		
			<atom:link href="https://sckwon.dev/en/tags/devops/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>DevOps Roadmap</title>
				<link>https://sckwon.dev/en/posts/devops-roadmap/</link>
				<pubDate>Sat, 11 Jul 2026 09:00:00 +0900</pubDate>
				<guid>https://sckwon.dev/en/posts/devops-roadmap/</guid>
				<description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;DevOps covers a wide range of topics, which can make it hard to know where to start. This post organizes what to learn in each phase, based on the order things are actually used in production.&lt;/p&gt;&#xA;&lt;p&gt;Rather than completing each phase perfectly before moving on, it&amp;rsquo;s more effective to grasp the essentials and progress to the next stage.&lt;/p&gt;&#xA;&lt;h2 id=&#34;1-foundations--linux-networking-git-shell&#34;&gt;1. Foundations — Linux, Networking, Git, Shell&lt;/h2&gt;&#xA;&#xA;&#xA;&lt;details class=&#34;interview-answer&#34;&gt;&#xA;  &lt;summary&gt;Details&lt;/summary&gt;&#xA;  &lt;div class=&#34;interview-answer-body&#34;&gt;&#xA;    &lt;p&gt;The starting point for DevOps is understanding server environments.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Linux / OS Fundamentals</title>
				<link>https://sckwon.dev/en/posts/linux-os-basics/</link>
				<pubDate>Tue, 07 Jul 2026 09:00:00 +0900</pubDate>
				<guid>https://sckwon.dev/en/posts/linux-os-basics/</guid>
				<description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;Linux is the foundation for understanding server operations and deployment environments. When incidents occur, you always end up checking processes, CPU, memory, disk, networking, logs, and service status.&lt;/p&gt;&#xA;&lt;p&gt;This post organizes the topics you&amp;rsquo;ll frequently revisit in Linux / OS. Beginners can learn the concepts, while experienced engineers can quickly reference commands and decision criteria.&lt;/p&gt;&#xA;&lt;h2 id=&#34;1-processes-vs-threads&#34;&gt;1. Processes vs Threads&lt;/h2&gt;&#xA;&#xA;&#xA;&lt;details class=&#34;interview-answer&#34;&gt;&#xA;  &lt;summary&gt;Details&lt;/summary&gt;&#xA;  &lt;div class=&#34;interview-answer-body&#34;&gt;&#xA;    &lt;p&gt;&lt;strong&gt;Concepts&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;A process is a unit of a running program. The OS allocates independent memory space (code, data, heap, stack) to each process. Processes don&amp;rsquo;t share memory by default, so one crashing doesn&amp;rsquo;t directly affect others.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
