<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Jon St.John</title><link>https://staging.jonstjohn.com/blog/</link><description>Recent content in Blog on Jon St.John</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 11 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://staging.jonstjohn.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Building This Site: Hugo, Go, and Cloud Run</title><link>https://staging.jonstjohn.com/blog/building-this-site-hugo-go-cloud-run/</link><pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate><guid>https://staging.jonstjohn.com/blog/building-this-site-hugo-go-cloud-run/</guid><description>&lt;p&gt;This site is static content generated by &lt;a href="https://gohugo.io"&gt;Hugo&lt;/a&gt; and served
by a small Go binary, packaged into a container and deployed to Cloud Run.
No framework, no server-side rendering at request time — just a build step
and a file server.&lt;/p&gt;</description></item><item><title>CockroachDB Multi-Region: Picking the Right Survival Goal</title><link>https://staging.jonstjohn.com/blog/cockroachdb-multi-region-survival-goals/</link><pubDate>Tue, 14 Jul 2026 00:00:00 +0000</pubDate><guid>https://staging.jonstjohn.com/blog/cockroachdb-multi-region-survival-goals/</guid><description>&lt;p&gt;One of the first design decisions you&amp;rsquo;ll make when deploying CockroachDB across
multiple regions is choosing a &lt;strong&gt;survival goal&lt;/strong&gt;. It sounds like a small setting,
but it quietly determines how your cluster behaves during a region outage — and
how much latency you pay for that guarantee on every write.&lt;/p&gt;</description></item><item><title>Debugging Transaction Contention in CockroachDB</title><link>https://staging.jonstjohn.com/blog/debugging-cockroachdb-transaction-contention/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://staging.jonstjohn.com/blog/debugging-cockroachdb-transaction-contention/</guid><description>&lt;p&gt;Transaction contention is usually invisible until it isn&amp;rsquo;t — throughput looks
fine, then a handful of hot rows turn into a queue of blocked transactions and
your p99 latency falls off a cliff. CockroachDB ships good tooling for this,
but it&amp;rsquo;s easy to miss if you don&amp;rsquo;t know where to look.&lt;/p&gt;</description></item></channel></rss>