<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Operational Excellence on Todd's Builder Blog</title><link>https://todd.ekenstam.dev/categories/operational-excellence/</link><description>Recent content in Operational Excellence on Todd's Builder Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Todd Ekenstam</copyright><lastBuildDate>Tue, 10 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://todd.ekenstam.dev/categories/operational-excellence/index.xml" rel="self" type="application/rss+xml"/><item><title>Beating the “Gate Rush”&lt;br&gt;&lt;small&gt;Why Slow Start Matters for Resiliency and Operational Excellence&lt;/small&gt;</title><link>https://todd.ekenstam.dev/posts/202602-slow-start/</link><pubDate>Tue, 10 Feb 2026 00:00:00 +0000</pubDate><guid>https://todd.ekenstam.dev/posts/202602-slow-start/</guid><description>&lt;p&gt;When a new pod comes online, it often experiences a &lt;em&gt;gate rush&lt;/em&gt;: it’s declared “Ready,” immediately receives its full share of production traffic, and then falls over—spiking latency, throwing transient 5xx/504s, or flapping readiness. This is especially common for warm-up–sensitive services (JVM class loading/JIT, cache population, connection pool establishment, TLS handshakes, model loading, etc.).&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://todd.ekenstam.dev/posts/202602-slow-start/featured.webp"/></item></channel></rss>