https://taskfused.com/tags/sqlite/ Recent content in Sqlite on TaskFused.com Hugo en-us Sun, 18 Oct 2026 00:00:00 +0000 https://taskfused.com/first-taskfused-release-runs-duplicate-requests-once-and-survives-worker-crashes/ Sun, 18 Oct 2026 00:00:00 +0000 https://taskfused.com/first-taskfused-release-runs-duplicate-requests-once-and-survives-worker-crashes/ <p>Some work gets asked for more than once. Someone double-clicks Export. A client times out and sends the request again while the first one is still running. Ten dashboards open at nine and all want last month&rsquo;s report. Each copy costs the same CPU, the same API credits and the same database time as the first, and when copies overlap they can trip over each other.</p> <p>TaskFused 0.1 is a small Go engine that runs that work once. You name each piece of work. The first request with a name creates an operation, saved to a local SQLite file before anyone hears about it. Equal requests after that join the same operation, wait with it, and get the same result. Once the work is done, later requests get the stored result straight away.</p> https://taskfused.com/how-taskfused-was-tested-with-killed-workers-and-injected-storage-faults/ Sun, 18 Oct 2026 00:00:00 +0000 https://taskfused.com/how-taskfused-was-tested-with-killed-workers-and-injected-storage-faults/ <p>TaskFused makes one promise above the others: work that two requests share is done once and kept safe, even when the process doing it dies. That&rsquo;s easy to claim and easy to get wrong, so most of the tests try to break it. They kill real processes, make the storage fail on purpose, and drop connections at awkward moments.</p> <p>Every result below comes from the files in <a href="https://github.com/taskfused/taskfused/tree/main/test/results">test/results</a>, recorded from version 0.1.0 on a two-core Linux cloud machine with Go 1.24 and SQLite 3.50.4, with every change flushed to disk. The same tests run on every push, on Linux and macOS.</p>