Go on TaskFused.com

Cache Stampede Protection With TaskFused, One Rebuild When a Busy Page Expires

Sun, 18 Oct 2026 00:00:00 +0000

A news site’s front page is built from a dozen slow queries, so it’s cached for five minutes. At the moment the cache entry expires, three hundred readers are loading the page. Every one of them misses the cache, and every one starts the same dozen queries. The database, which was fine a second ago, is suddenly doing three hundred times the work, pages time out, and the timeouts make readers reload. That’s a cache stampede, sometimes called the thundering herd.

First TaskFused Release Runs Duplicate Requests Once and Survives Worker Crashes

Sun, 18 Oct 2026 00:00:00 +0000

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’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.

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.

Monthly Report Exports With TaskFused, Built Once When Ten Managers Click at 9am

Sun, 18 Oct 2026 00:00:00 +0000

On the first working day of the month, every regional manager opens the dashboard and clicks Export on last month’s sales report. The report is the same for all of them. It reads two million order rows, groups them, draws six charts and writes a PDF, which takes about forty seconds of database time. Ten clicks in the same minute means ten copies of that work, ten heavy queries fighting over the same tables, and a dashboard that crawls for everyone else.

Paid AI Calls With TaskFused, One Model Call Billed When Three Parts of an App Ask

Sun, 18 Oct 2026 00:00:00 +0000

A user uploads a 40-page contract and the app wants a summary. The browser asks for it when the page opens. The search indexer asks for it a few seconds later, because summaries make good snippets. And the user, impatient, hits Refresh. Three requests, one document, and each one would send the whole contract to a language model and pay for every token of it, three times.

AI calls are the clearest case for doing work once. They’re slow, often ten or twenty seconds for a long document, so duplicates overlap a lot. They’re billed per token. And the answer for the same document, model and prompt doesn’t need to be made twice.