<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>case studies on Aftermarket.dev</title>
    <link>https://aftermarket.dev/tags/case-studies/</link>
    <description>Recent content in case studies 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/case-studies/index.xml" rel="self" type="application/rss+xml" />
    <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>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>Case Study: Serving Nightly CSV Exports and a SQLite Inventory as a JSON API</title>
      <link>https://aftermarket.dev/case-study-serving-nightly-csv-exports-and-a-sqlite-inventory-as-a-json-api/</link>
      <pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/case-study-serving-nightly-csv-exports-and-a-sqlite-inventory-as-a-json-api/</guid>
      <description>This case uses the examples/legacy-exports folder that ships in every download archive, so you can run each step yourself. The shop app is a stand-in. The commands and output below come from a real run of the downloaded aftermarket 0.9.0 on Linux, with the inventory loaded into a real database file (sqlite3 inventory.db &amp;lt; inventory.sql) and served from a copy of the config, bridge-db.yaml, that points at it.
The situation An old shop app has no API.</description>
    </item>
    
    <item>
      <title>Case Study: Getting Through a Vendor Upgrade With AfterConfig Guards</title>
      <link>https://aftermarket.dev/case-study-getting-through-a-vendor-upgrade-with-afterconfig-guards/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/case-study-getting-through-a-vendor-upgrade-with-afterconfig-guards/</guid>
      <description>This case uses the examples/vendor-app folder that ships in every download archive, so you can run each step yourself. The commands and output below come from a real run of the downloaded aftermarket 0.4.0.
The situation A team runs a vendor&amp;rsquo;s app. It reads config.json, and each upgrade replaces that file. The team needs seven changes:
a longer timeout more workers JSON logs no telemetry their own database password a bigger connection pool a body limit the vendor doesn&amp;rsquo;t offer yet They keep those changes in overlay.</description>
    </item>
    
    <item>
      <title>Case Study: Getting Webhooks From an Old App With AfterHook</title>
      <link>https://aftermarket.dev/case-study-getting-webhooks-from-an-old-app-with-afterhook/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/case-study-getting-webhooks-from-an-old-app-with-afterhook/</guid>
      <description>This case uses the examples/legacy-app folder that ships in every download archive, a stand-in for a real old app, so you can run each step yourself. The commands and output below come from a real run of the downloaded aftermarket 0.5.1. The only extras are the sqlite3 program and Go for the receiver.
The situation A small order app has been running for years. It writes the current order to status.</description>
    </item>
    
    <item>
      <title>Case Study: Keeping Changes to a Vendor TOML Config Through an Upgrade</title>
      <link>https://aftermarket.dev/case-study-keeping-changes-to-a-vendor-toml-config-through-an-upgrade/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/case-study-keeping-changes-to-a-vendor-toml-config-through-an-upgrade/</guid>
      <description>This case uses the examples/vendor-app-toml folder that ships in every download archive, so you can run each step yourself. The vendor app is a stand-in. The commands and output below come from a real run of the downloaded aftermarket 0.7.0.
The situation A team runs a vendor&amp;rsquo;s app that reads config.toml. The vendor writes good comments in that file, and replaces it on every upgrade. The team needs seven changes: a longer timeout, more workers, JSON logs, no telemetry, their own database password, a bigger pool, and the weekly report moved to Sunday.</description>
    </item>
    
    <item>
      <title>Case Study: Keeping Old Shop Reports Working After a Schema Change</title>
      <link>https://aftermarket.dev/case-study-keeping-old-shop-reports-working-after-a-schema-change/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/case-study-keeping-old-shop-reports-working-after-a-schema-change/</guid>
      <description>This case uses the examples/legacy-shop folder that ships in every download archive, so you can run each step yourself. The shop is a stand-in. The commands and output below come from a real run of the downloaded aftermarket 0.8.0 on Linux, with sqlite3 3.45.
The situation A small shop app moved from 1.0 to 2.0. The new version renamed customers to accounts and split the name into first and last. It stops deleting accounts and marks them with a deleted_at date instead.</description>
    </item>
    
    <item>
      <title>Case Study: Putting an Old Admin Panel Behind AfterGuard</title>
      <link>https://aftermarket.dev/case-study-putting-an-old-admin-panel-behind-afterguard/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/case-study-putting-an-old-admin-panel-behind-afterguard/</guid>
      <description>This case uses the examples/legacy-admin folder from the code repository: a small stand-in for a real old admin panel, and the guard.yaml and fixture that ship in every download archive. The commands and output below come from a real run of the downloaded aftermarket 0.6.0 in front of that panel.
The situation The panel was written years ago for one office. It has no login. It lists and adds users under /admin/, serves a daily CSV under /reports/ that the billing system pulls, and has a debug page nobody remembers adding.</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>Case Study: Fixing a Moved Exchange Rate Endpoint With Two AfterPatch Rules</title>
      <link>https://aftermarket.dev/case-study-fixing-a-moved-exchange-rate-endpoint-with-two-afterpatch-rules/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/case-study-fixing-a-moved-exchange-rate-endpoint-with-two-afterpatch-rules/</guid>
      <description>This is a worked case on a small stand-in service, built to look like a common kind of break. Every command and every line of output below comes from a real run of aftermarket 0.3.0.
What broke An app shows exchange rates. It calls GET /v1/rate?from=EUR&amp;amp;to=USD and reads rate from the answer. It&amp;rsquo;s installed on devices nobody can update this week.
The rate provider shipped a new version, and three things changed at once:</description>
    </item>
    
    <item>
      <title>Case Study: Moving an Old Client to a New Customer API With AfterAPI</title>
      <link>https://aftermarket.dev/case-study-moving-an-old-client-to-a-new-customer-api-with-afterapi/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/case-study-moving-an-old-client-to-a-new-customer-api-with-afterapi/</guid>
      <description>This case uses the examples/customer-api folder from the code repository, so you can run every step yourself. The commands and output below come from a real run of aftermarket 0.3.0.
The situation A customer service was rewritten, and its v1 API was switched off. One old client still calls v1, and it comes with its own test suite of twelve strict checks. Field names, extra fields, status codes and error messages all count.</description>
    </item>
    
  </channel>
</rss>
