<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sai Krishna</title>
    <description>The latest articles on DEV Community by Sai Krishna (@sai_krishna_3399).</description>
    <link>https://dev.to/sai_krishna_3399</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3911386%2Fd67b271f-d96e-4f13-bb2a-35427d03e06d.jpg</url>
      <title>DEV Community: Sai Krishna</title>
      <link>https://dev.to/sai_krishna_3399</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sai_krishna_3399"/>
    <language>en</language>
    <item>
      <title>Uptime Isn’t Enough — My Shift from SRE to FinOps</title>
      <dc:creator>Sai Krishna</dc:creator>
      <pubDate>Mon, 04 May 2026 06:01:00 +0000</pubDate>
      <link>https://dev.to/sai_krishna_3399/uptime-isnt-enough-my-shift-from-sre-to-finops-2f0b</link>
      <guid>https://dev.to/sai_krishna_3399/uptime-isnt-enough-my-shift-from-sre-to-finops-2f0b</guid>
      <description>&lt;p&gt;Hey Dev.to 👋&lt;/p&gt;

&lt;p&gt;I’ve spent the last several years working as a Staff Site Reliability Engineer, focused on keeping systems reliable, scalable, and — most importantly — up.&lt;/p&gt;

&lt;p&gt;Like many SREs, my world revolved around:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;SLAs, SLOs, and error budgets&lt;/li&gt;
&lt;li&gt;Incident response and postmortems&lt;/li&gt;
&lt;li&gt;Observability, automation, and resilience&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And while uptime is critical… I started noticing something:&lt;/p&gt;

&lt;p&gt;👉 We rarely talked about the cost of reliability.&lt;br&gt;
⸻&lt;/p&gt;

&lt;p&gt;The Shift&lt;/p&gt;

&lt;p&gt;As systems scale, so do cloud bills.&lt;br&gt;
And at some point, I realized:&lt;/p&gt;

&lt;p&gt;Keeping systems up is only half the problem — keeping them cost-efficient matters just as much.&lt;/p&gt;

&lt;p&gt;That’s what pulled me toward FinOps.&lt;/p&gt;

&lt;p&gt;Not as a replacement for SRE — but as a natural extension of it.&lt;br&gt;
⸻&lt;/p&gt;

&lt;p&gt;Why FinOps?&lt;/p&gt;

&lt;p&gt;Because:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Overprovisioning is easy under pressure&lt;/li&gt;
&lt;li&gt;“Just scale it” often hides inefficiencies&lt;/li&gt;
&lt;li&gt;Reliability decisions directly impact cost&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And yet, cost is often treated as someone else’s problem.&lt;/p&gt;

&lt;p&gt;It shouldn’t be.&lt;/p&gt;

&lt;p&gt;⸻&lt;/p&gt;

&lt;p&gt;Where I’m Headed&lt;/p&gt;

&lt;p&gt;I’m currently exploring:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Cost-aware architecture patterns&lt;/li&gt;
&lt;li&gt;Rightsizing and workload optimization&lt;/li&gt;
&lt;li&gt;Bridging engineering and finance conversations&lt;/li&gt;
&lt;li&gt;Building a culture where cost is a first-class metric
⸻&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What to Expect Here&lt;/p&gt;

&lt;p&gt;I’ll be sharing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Practical FinOps learnings from an SRE perspective&lt;/li&gt;
&lt;li&gt;Real-world trade-offs between reliability and cost&lt;/li&gt;
&lt;li&gt;Tools, strategies, and mistakes along the way&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;⸻&lt;/p&gt;

&lt;p&gt;Let’s Connect&lt;/p&gt;

&lt;p&gt;If you’re working in:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;SRE / Platform Engineering&lt;/li&gt;
&lt;li&gt;Cloud Infrastructure&lt;/li&gt;
&lt;li&gt;FinOps or cost optimization&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;…I’d love to learn from you.&lt;/p&gt;

&lt;p&gt;⸻&lt;/p&gt;

&lt;p&gt;Less downtime. Less waste. Better systems.&lt;/p&gt;

&lt;p&gt;Let’s build that together 🚀&lt;/p&gt;

</description>
      <category>finops</category>
      <category>kubernetes</category>
      <category>linux</category>
      <category>aws</category>
    </item>
  </channel>
</rss>
