Aftermarket on SoftDevStudio.com

Aftermarket Adds AfterAPI to Keep Old Clients Working on a New API

Tue, 20 Oct 2026 00:00:00 +0000

Aftermarket has its second tool. AfterAPI, run as aftermarket adapt, is for the day a whole API gets replaced and a client still expects the old one. AfterPatch fixes one field or path at a time. AfterAPI has you write each old endpoint in terms of the new one: {id} moves from the old URL into the new, a short template rebuilds the old response from the new one, and status codes and error bodies get mapped back. A mapping applies fully or not at all, so anything it can’t translate safely passes through as sent and gets logged.

Aftermarket Adds AfterTest and AfterDiff to Record Traffic and Compare Versions

Tue, 20 Oct 2026 00:00:00 +0000

Aftermarket now has four tools. The new pair answers the question that comes before any repair: what actually changed? AfterTest, run as aftermarket record, is a proxy that changes nothing and saves each request and answer as a test fixture. Credentials, cookies and keys such as api_key are blanked as REDACTED in the file, and a config can add more fields, while the real traffic keeps the real values. AfterDiff, run as aftermarket replay, sends the recording to two versions of a service and lists every difference by field. It sends only reads unless told otherwise, so it can’t change data on a live service.

Aftermarket Launches With AfterPatch, a Proxy That Repairs HTTP Traffic by Rules

Mon, 19 Oct 2026 00:00:00 +0000

Aftermarket, the studio’s twenty-third project, is about the work that happens after software ships: the proxy rule that renames a field, the shim that keeps an old client alive, the patch nobody can test. It gives that work a name and a set of tools, all under one aftermarket command. Ten are planned. The first one is out.

AfterPatch 0.1.0 sits between a client and a service that neither side can change, and fixes the traffic with YAML rules short enough to review. A rule picks traffic by method, path, query, headers, status and content type. It can move an endpoint, set or drop headers, and rename, copy, set or delete JSON fields going in and out. The example it was built around is an old client calling /api/v1/customer?id=7 against a new service that only knows /api/v2/customers/7. Two rules make them talk again, and the quick start runs it in five minutes. A dry run shows what the rules would change on live traffic, and an audit log records every change without a single value in it.