<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>afterdiff on Aftermarket.dev</title>
    <link>https://aftermarket.dev/tags/afterdiff/</link>
    <description>Recent content in afterdiff on Aftermarket.dev</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aftermarket.dev/tags/afterdiff/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AfterDiff Gets a Live Shadow Mode to Test New Versions on Real Traffic</title>
      <link>https://aftermarket.dev/afterdiff-gets-a-live-shadow-mode-to-test-new-versions-on-real-traffic/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/afterdiff-gets-a-live-shadow-mode-to-test-new-versions-on-real-traffic/</guid>
      <description>Aftermarket 0.10.0 adds aftermarket shadow. It&amp;rsquo;s AfterDiff, but on live traffic instead of a recording.
Replay is good at one thing. You record what a client sends, play it to the old and the new version, and read the differences. But a recording only holds what happened while it ran. The odd request that comes once a week isn&amp;rsquo;t in the file, and neither is the client nobody remembered.
Shadow puts the new version next to the old one while real users keep going.</description>
    </item>
    
    <item>
      <title>Aftermarket Fixes Five Shadow Mode Bugs Found in Review</title>
      <link>https://aftermarket.dev/aftermarket-fixes-five-shadow-mode-bugs-found-in-review/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/aftermarket-fixes-five-shadow-mode-bugs-found-in-review/</guid>
      <description>Aftermarket 0.10.1 is a fix release for aftermarket shadow, the live mode of AfterDiff that came out earlier today. A second reviewer went through it looking for ways to break its promises, and found five real bugs. None of them touched what clients get back from the primary. They were about what the candidate got and what the report said.
Here&amp;rsquo;s the list.
Stopping made the candidate look broken. On Ctrl-C, shadow waits a while for queued copies and then stops.</description>
    </item>
    
    <item>
      <title>How Shadow Mode Holds Up Under Load With Sampling and a Full Queue</title>
      <link>https://aftermarket.dev/how-shadow-mode-holds-up-under-load-with-sampling-and-a-full-queue/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/how-shadow-mode-holds-up-under-load-with-sampling-and-a-full-queue/</guid>
      <description>Shadow mode makes one promise above the others: the candidate can never slow down or break what clients get. On a quiet service that&amp;rsquo;s easy. This case puts it under steady load, with a candidate that can&amp;rsquo;t keep up, to see what gives and what the report says about it.
The pair is the same as in the Datasette case study: Datasette 0.65.5 as the primary and 1.0a41 as the candidate, serving the same parks database.</description>
    </item>
    
    <item>
      <title>Shadow Mode Recipes for Testing a New Version on Live Traffic</title>
      <link>https://aftermarket.dev/shadow-mode-recipes-for-testing-a-new-version-on-live-traffic/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/shadow-mode-recipes-for-testing-a-new-version-on-live-traffic/</guid>
      <description>Short, practical setups for aftermarket shadow, each one run before it went here. The commands come from runs of the downloaded 0.10.1 against Datasette, JSON Server and the customer-api example, recorded under test/results/case-studies/shadow in the code repository. In all of them the primary is the version clients use today and the candidate is the new one.
Shadow a rewrite Start with reads only. That&amp;rsquo;s the default, and it can&amp;rsquo;t change anything on the candidate:</description>
    </item>
    
    <item>
      <title>Shadowing the JSON Server Rewrite With Reads and Writes</title>
      <link>https://aftermarket.dev/shadowing-the-json-server-rewrite-with-reads-and-writes/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/shadowing-the-json-server-rewrite-with-reads-and-writes/</guid>
      <description>JSON Server gives you a full REST API from one JSON file, and a lot of front-end projects and test suites lean on it. Version 1.0, still in beta, is a rewrite, and its own README asks you to expect breaking changes. That makes it a good subject for shadow mode: a team on 0.17.4 wants to know what its client would see on 1.0 before the switch, including for the requests that change data.</description>
    </item>
    
    <item>
      <title>Testing a Datasette Upgrade on Live Read Traffic With Shadow Mode</title>
      <link>https://aftermarket.dev/testing-a-datasette-upgrade-on-live-read-traffic-with-shadow-mode/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/testing-a-datasette-upgrade-on-live-read-traffic-with-shadow-mode/</guid>
      <description>Datasette is an open source tool that publishes a SQLite database as a website and a JSON API. Its 1.0 line has been in alpha for a while, and the changelog says plainly that the JSON API is getting a new design before 1.0 ships. If you have scripts or dashboards reading a Datasette instance, you&amp;rsquo;d want to know what they will see before you upgrade it.
This case puts aftermarket shadow in front of the current stable release, 0.</description>
    </item>
    
    <item>
      <title>AfterTest and AfterDiff Released to Record Traffic and Compare Versions</title>
      <link>https://aftermarket.dev/aftertest-and-afterdiff-released-to-record-traffic-and-compare-versions/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/aftertest-and-afterdiff-released-to-record-traffic-and-compare-versions/</guid>
      <description>Aftermarket 0.3.0 adds two tools that work as a pair. AfterTest, run as aftermarket record, saves real traffic as test fixtures. AfterDiff, run as aftermarket replay, sends those fixtures to two versions of a service and tells you where the answers differ.
The first two tools fix things. These two answer the question that comes before any fix: what actually changed? A new release, a migrated service or a rewritten endpoint can look the same in the docs and still answer differently.</description>
    </item>
    
    <item>
      <title>Case Study: Catching a Renamed Field Before Release With AfterTest and AfterDiff</title>
      <link>https://aftermarket.dev/case-study-catching-a-renamed-field-before-release-with-aftertest-and-afterdiff/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/case-study-catching-a-renamed-field-before-release-with-aftertest-and-afterdiff/</guid>
      <description>This is a worked case on two small stand-in versions of an orders service. Every command and every line of output below comes from a real run of aftermarket 0.3.0.
The question A team is about to replace version 1 of an orders service with version 2. The release notes say nothing about the API. Clients they don&amp;rsquo;t control call it every day. Before switching, they want to know: does v2 answer the same questions the same way?</description>
    </item>
    
    <item>
      <title>How AfterTest and AfterDiff Were Tested With Secrets in Every Request</title>
      <link>https://aftermarket.dev/how-aftertest-and-afterdiff-were-tested-with-secrets-in-every-request/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/how-aftertest-and-afterdiff-were-tested-with-secrets-in-every-request/</guid>
      <description>A recorder sits on real traffic and writes it to disk. So it makes two promises, and the tests go after both. It must not change a single byte on the way through. And no secret may end up in the file.
Not a byte changed One test sends 300 random requests straight to a test server and then through record, and compares what each side saw. The traffic is deliberately awkward: binary bodies, gzip, chunked bodies, bodies of unknown length, %2F and ü in paths, ; in query strings, HEAD, 204 and 304.</description>
    </item>
    
  </channel>
</rss>
