<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Devops on Besterry — Linux &amp; DevOps Notes</title><link>https://besterry.com/tags/devops/</link><description>Recent content in Devops on Besterry — Linux &amp; DevOps Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 22 Oct 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://besterry.com/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Self-Host vs SaaS: The Actual Tradeoffs</title><link>https://besterry.com/posts/selfhost-vs-saas-tradeoffs/</link><pubDate>Tue, 22 Oct 2024 00:00:00 +0000</pubDate><guid>https://besterry.com/posts/selfhost-vs-saas-tradeoffs/</guid><description>&lt;p&gt;The &amp;ldquo;self-host everything&amp;rdquo; movement has passionate advocates on both sides. Reality is nuanced. Here&amp;rsquo;s the framework I use when deciding.&lt;/p&gt;
&lt;h2 id="cost-isnt-the-main-factor"&gt;Cost isn&amp;rsquo;t the main factor&lt;/h2&gt;
&lt;p&gt;Many self-host advocates lead with cost savings. Usually it&amp;rsquo;s misleading:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;SaaS at small scale is often free or cheap ($0-50/mo)&lt;/li&gt;
&lt;li&gt;Self-hosting on cheap VPS starts around $5/mo&lt;/li&gt;
&lt;li&gt;But self-hosting eats engineer time — 2-10 hours/month for maintenance&lt;/li&gt;
&lt;li&gt;At $100/hr engineering time, self-hosting often costs MORE than SaaS&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Cost-wise, self-hosting wins when you&amp;rsquo;re either:&lt;/p&gt;</description></item><item><title>Terraform State Locking: Why You Need It and How It Goes Wrong</title><link>https://besterry.com/posts/terraform-state-locking/</link><pubDate>Wed, 18 Sep 2024 00:00:00 +0000</pubDate><guid>https://besterry.com/posts/terraform-state-locking/</guid><description>&lt;p&gt;Terraform state without locking is a bug waiting to happen. Two engineers running apply simultaneously can corrupt state in ways that take hours to untangle. Here&amp;rsquo;s what I learned after one such incident.&lt;/p&gt;
&lt;h2 id="why-state-locking-matters"&gt;Why state locking matters&lt;/h2&gt;
&lt;p&gt;Terraform reads state, computes a plan, and writes new state. Without locking, two concurrent runs can:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Both read the same initial state&lt;/li&gt;
&lt;li&gt;Both compute their plans based on it&lt;/li&gt;
&lt;li&gt;Both write conflicting state — last one wins&lt;/li&gt;
&lt;li&gt;Now state doesn&amp;rsquo;t match real infrastructure&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The symptoms are weird: resources exist but Terraform wants to create them again. Or state references resources that were already destroyed.&lt;/p&gt;</description></item></channel></rss>