https://aftermarket.dev/tags/afterbridge/ Recent content in afterbridge on Aftermarket.dev Hugo -- gohugo.io en-us Thu, 22 Oct 2026 00:00:00 +0000 https://aftermarket.dev/afterbridge-released-to-serve-old-csv-exports-and-sqlite-files-as-a-json-api/ Thu, 22 Oct 2026 00:00:00 +0000 https://aftermarket.dev/afterbridge-released-to-serve-old-csv-exports-and-sqlite-files-as-a-json-api/ Aftermarket 0.9.0 adds AfterBridge, run as aftermarket bridge. It’s for the app that never got an API. It drops a CSV export into a folder every night, or keeps everything in a SQLite file, and anything else that wants the data has to go and parse the files. So everyone writes their own little parser. One forgets the quoted commas, one reads the file while the app is still writing it, one treats the empty cell as zero. https://aftermarket.dev/case-study-serving-nightly-csv-exports-and-a-sqlite-inventory-as-a-json-api/ Thu, 22 Oct 2026 00:00:00 +0000 https://aftermarket.dev/case-study-serving-nightly-csv-exports-and-a-sqlite-inventory-as-a-json-api/ 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 < 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. https://aftermarket.dev/how-afterbridge-was-tested/ Thu, 22 Oct 2026 00:00:00 +0000 https://aftermarket.dev/how-afterbridge-was-tested/ AfterBridge makes four promises. The files it reads are never written. Nothing a request sends reaches SQL or the file system. A file that is half written is never served. And every answer is exactly what the file holds, values and types alike. Most of the testing went into the third and the fourth, because that’s where reading someone else’s files goes wrong. Half files The main test has a writer rewriting an export over and over, in random pieces, sometimes stopping in the middle of a line, with short pauses, while requests keep coming.