<?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: Ira Murphy</title>
    <description>The latest articles on DEV Community by Ira Murphy (@murphy_90).</description>
    <link>https://dev.to/murphy_90</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4210577%2F138dc7df-ab1b-49be-9080-29d17ea93761.jpg</url>
      <title>DEV Community: Ira Murphy</title>
      <link>https://dev.to/murphy_90</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/murphy_90"/>
    <language>en</language>
    <item>
      <title>What I actually use Cloud Run for (and what I don't)</title>
      <dc:creator>Ira Murphy</dc:creator>
      <pubDate>Thu, 29 Oct 2026 01:20:29 +0000</pubDate>
      <link>https://dev.to/murphy_90/what-i-actually-use-cloud-run-for-and-what-i-dont-1n2j</link>
      <guid>https://dev.to/murphy_90/what-i-actually-use-cloud-run-for-and-what-i-dont-1n2j</guid>
      <description>&lt;p&gt;I've been running small services on Cloud Run for about a year now. Not a big migration story, just the honest list of where it fits and where it doesn't.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it's genuinely good at
&lt;/h2&gt;

&lt;p&gt;Internal webhooks. We have a handful of integrations that get maybe a hundred requests a day, each spike is unpredictable, and the rest of the time nobody is calling them. Cloud Run scales to zero, so the bill is basically nothing and I don't have to think about a VM.&lt;/p&gt;

&lt;p&gt;Scheduled jobs that used to be cron on a box. Cloud Scheduler hitting a Cloud Run service with a shared secret is boring and reliable, which is exactly what I want for a nightly job.&lt;/p&gt;

&lt;p&gt;Small internal tools: a form that writes to a sheet, a service that reformats a file and drops it in a bucket. The kind of thing where the code is fifty lines and the deployment used to be a whole afternoon.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I don't use it for
&lt;/h2&gt;

&lt;p&gt;Anything with a long-running connection. WebSockets are possible but I'd rather not fight with the request timeout and eventual cold starts. If the service needs to hold a connection for minutes, I put it somewhere else.&lt;/p&gt;

&lt;p&gt;Stateful things. Cloud Run gives you no guarantees about which instance handles the next request, so anything that needs a local cache or a local file needs to be designed around that from day one. I learned this the hard way with a SQLite experiment that worked perfectly on my laptop and fell apart the moment two instances existed.&lt;/p&gt;

&lt;p&gt;GPU workloads. Not the right product, and pretending otherwise is how you end up debugging someone else's scheduler.&lt;/p&gt;

&lt;h2&gt;
  
  
  The part people skip: cold starts
&lt;/h2&gt;

&lt;p&gt;For low-traffic internal tools, cold starts are the whole story. The first request after idle can take a few seconds, and for a user clicking a form that feels broken. Two fixes that actually helped: keep the container small (multi-stage build, scratch or distroless base), and set a minimum instance count of 1 for anything a human waits on. The second one costs money, but less than you'd think for a small instance.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd tell someone starting
&lt;/h2&gt;

&lt;p&gt;Start with one small service and no min instances. Watch the cold starts for a week, and only then decide what deserves a minimum instance. The default configuration is a reasonable starting point, and most of the tuning advice you read online is for traffic you don't have yet.&lt;/p&gt;

</description>
      <category>cloud</category>
      <category>devops</category>
      <category>googlecloud</category>
    </item>
    <item>
      <title>Rewriting a glue script in Rust: was it worth it?</title>
      <dc:creator>Ira Murphy</dc:creator>
      <pubDate>Tue, 27 Oct 2026 15:40:13 +0000</pubDate>
      <link>https://dev.to/murphy_90/rewriting-a-glue-script-in-rust-was-it-worth-it-5723</link>
      <guid>https://dev.to/murphy_90/rewriting-a-glue-script-in-rust-was-it-worth-it-5723</guid>
      <description>&lt;p&gt;I had a ~200-line bash script that glued together a few AWS CLI calls, did some retries, and wrote a report. It worked, but nobody wanted to touch it.&lt;/p&gt;

&lt;p&gt;I rewrote it in Rust over a weekend. The honest verdict:&lt;/p&gt;

&lt;p&gt;Good:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Typed config and real error handling&lt;/li&gt;
&lt;li&gt;Retries with backoff that I actually trust&lt;/li&gt;
&lt;li&gt;A binary I can drop on any machine&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Bad:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Compile times for a trivial tool&lt;/li&gt;
&lt;li&gt;AWS SDK is a lot of dependency surface&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Would I do it again? For a tool other people run, yes. For a one-off, probably not — I'd write it in Python and spend the time on tests instead.&lt;/p&gt;

&lt;p&gt;I'm learning Rust more seriously now. The borrow checker stopped feeling like an enemy around week three, which I'm told is normal.&lt;/p&gt;

</description>
      <category>rust</category>
      <category>devops</category>
      <category>automation</category>
    </item>
  </channel>
</rss>
