<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vantalect Blog</title>
    <link>https://vantalect.com/blog/</link>
    <description>Cloud Design Patterns on AWS and essays on measuring AI-assisted engineering, from Charles Sieg at Vantalect.</description>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vantalect.com/blog/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Retries Without Retry Storms: Backoff, Jitter, and Idempotency Keys</title>
      <link>https://vantalect.com/blog/retries-backoff-jitter-idempotency/</link>
      <guid isPermaLink="true">https://vantalect.com/blog/retries-backoff-jitter-idempotency/</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <author>info@vantalect.com (Charles Sieg)</author>
      <description>A retry is extra load at the worst moment. Backoff, full jitter, a retry budget, and idempotency keys make it safe.</description>
    </item>
    <item>
      <title>Circuit Breakers: Failing Fast So a Slow Dependency Can&#39;t Take You Down</title>
      <link>https://vantalect.com/blog/circuit-breakers/</link>
      <guid isPermaLink="true">https://vantalect.com/blog/circuit-breakers/</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <author>info@vantalect.com (Charles Sieg)</author>
      <description>A slow dependency is more dangerous than a dead one. A circuit breaker with its own small bulkhead turns the first into the second on purpose.</description>
    </item>
    <item>
      <title>Queue-Based Load Leveling: Let the Queue Take the Spike</title>
      <link>https://vantalect.com/blog/queue-based-load-leveling/</link>
      <guid isPermaLink="true">https://vantalect.com/blog/queue-based-load-leveling/</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <author>info@vantalect.com (Charles Sieg)</author>
      <description>A queue lets you size workers for the average load instead of the peak, if you cap the consumers and alarm on the age of the oldest message.</description>
    </item>
    <item>
      <title>Load Shedding and Backpressure: Saying No Early Keeps the Lights On</title>
      <link>https://vantalect.com/blog/load-shedding-and-backpressure/</link>
      <guid isPermaLink="true">https://vantalect.com/blog/load-shedding-and-backpressure/</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <author>info@vantalect.com (Charles Sieg)</author>
      <description>An overloaded service that tries to serve everyone serves no one. Reject excess work early, drop expired requests, and tell callers to slow down.</description>
    </item>
    <item>
      <title>Cache-Aside With Request Coalescing: Surviving the Cold Cache</title>
      <link>https://vantalect.com/blog/cache-aside-request-coalescing/</link>
      <guid isPermaLink="true">https://vantalect.com/blog/cache-aside-request-coalescing/</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <author>info@vantalect.com (Charles Sieg)</author>
      <description>A cache your database cannot survive without is no longer an optimization. Coalesce misses, jitter expiry, and serve stale data while you refresh.</description>
    </item>
    <item>
      <title>Event Fan-Out With Dead-Letter Queues: Publish Once, Fail Alone</title>
      <link>https://vantalect.com/blog/event-fan-out-dead-letter-queues/</link>
      <guid isPermaLink="true">https://vantalect.com/blog/event-fan-out-dead-letter-queues/</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <author>info@vantalect.com (Charles Sieg)</author>
      <description>Fan-out lets each consumer fail alone, but only with its own queue, its own retry policy, and a dead-letter queue that pages someone.</description>
    </item>
    <item>
      <title>CQRS With Read Models: Stop Making One Database Do Two Jobs</title>
      <link>https://vantalect.com/blog/cqrs-read-models/</link>
      <guid isPermaLink="true">https://vantalect.com/blog/cqrs-read-models/</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <author>info@vantalect.com (Charles Sieg)</author>
      <description>When reads and writes want different shapes, scales, or engines, keep one model for commands and build read models from its changes.</description>
    </item>
    <item>
      <title>Static Stability: Designing for the Day the Control Plane Is Down</title>
      <link>https://vantalect.com/blog/static-stability/</link>
      <guid isPermaLink="true">https://vantalect.com/blog/static-stability/</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <author>info@vantalect.com (Charles Sieg)</author>
      <description>A statically stable workload survives an Availability Zone loss without launching, scaling, or reconfiguring anything. Here is the arithmetic.</description>
    </item>
    <item>
      <title>Cell-Based Architecture: Shrinking the Blast Radius</title>
      <link>https://vantalect.com/blog/cell-based-architecture/</link>
      <guid isPermaLink="true">https://vantalect.com/blog/cell-based-architecture/</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <author>info@vantalect.com (Charles Sieg)</author>
      <description>Redundancy protects you from hardware, not from your own bad deploy. Split the workload into independent cells so each failure reaches only one.</description>
    </item>
    <item>
      <title>Observability That Answers Questions: RED, USE, Traces, and SLOs</title>
      <link>https://vantalect.com/blog/observability-red-use-slos/</link>
      <guid isPermaLink="true">https://vantalect.com/blog/observability-red-use-slos/</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <author>info@vantalect.com (Charles Sieg)</author>
      <description>Green dashboards do not mean happy customers. Measure rate, errors, and duration, connect them with traces, and page on SLO burn, not on CPU.</description>
    </item>
    <item>
      <title>The Leverage Factor, Part 2: Defending the Numbers</title>
      <link>https://vantalect.com/blog/defending-the-numbers/</link>
      <guid isPermaLink="true">https://charlessieg.com/articles/leverage-factor-defending-the-numbers.html</guid>
      <pubDate>Mon, 02 Mar 2026 00:00:00 +0000</pubDate>
      <author>info@vantalect.com (Charles Sieg)</author>
      <description>The first leverage article drew hostile mail. This one answers it: what the estimates mean, why the METR study does not apply, the supervisory factor.</description>
    </item>
    <item>
      <title>Agentic Coding and Decision Fatigue: The Cognitive Cost of Supervising AI</title>
      <link>https://vantalect.com/blog/agentic-coding-and-decision-fatigue/</link>
      <guid isPermaLink="true">https://charlessieg.com/articles/agentic-coding-decision-fatigue.html</guid>
      <pubDate>Sat, 28 Feb 2026 00:00:00 +0000</pubDate>
      <author>info@vantalect.com (Charles Sieg)</author>
      <description>Supervising AI agents means hundreds of accept-or-reject decisions a day, and decision quality falls by afternoon. What the science says, and what compensates.</description>
    </item>
    <item>
      <title>The Leverage Factor: Measuring AI-Assisted Engineering Output</title>
      <link>https://vantalect.com/blog/the-leverage-factor/</link>
      <guid isPermaLink="true">https://charlessieg.com/articles/leverage-factor-measuring-ai-engineering-output.html</guid>
      <pubDate>Tue, 24 Feb 2026 00:00:00 +0000</pubDate>
      <author>info@vantalect.com (Charles Sieg)</author>
      <description>Leverage is a small input controlling a large output. For engineering with AI agents, it is senior-engineer hours divided by agent minutes.</description>
    </item>
  </channel>
</rss>