Project
Cloudflare's managed serverless SQLite database, bound directly to Workers.
Cloudflare says D1 has passed 5.5 million databases, with live databases up 15x in a year as of October 8, 2026. Its post lists the design tenets behind the control plane and says operators building on its platform can reuse many of them.
Reality
Azure Front Door charges about $205 a month for a terabyte of static files that Cloudflare Workers serves for $0, per a dev.to list-price comparison. Past the included allowance, each paid Azure route bills by the gigabyte, so the service a site ships through puts the same terabyte at about $78 to $205.
Reality
Many SvelteKit starter kits run Drizzle migrations on every boot, a default that turns into a race once two replicas start at the same moment. A dev.to post moves the writes into one explicit step before traffic and keeps the boot call as a backstop.
Reality
One developer shipping Drizzle ORM on two SvelteKit kits keeps drizzle-kit push in prototyping because it writes no migration history. Production gets generated SQL that is read before it runs, plus a boot-time migrate that multiple replicas can race.
Reality
Cloudflare has shipped four Workers roles at three scopes to all customers, so an agent's API token can now carry one of them for a single application. Resource-level control for D1, R2 and KV is still a plan.
Reality
A week building an image SaaS on Cloudflare Workers produced nine failures. In the five shown in code, two come from the TanStack Start plugin's build behaviour and three from React timing and captcha logic that follow the code anywhere.
Reality
The rig is one Cloudflare Function, one D1 table and an inline script. The part that makes the data mean anything is a movement and duration filter on pointerup, tuned by hand on a site whose only conversion is a phone call.
Reality
The mechanism is RxDB holding a working copy on the device and R2 holding periodic snapshots, so a first sync is one download plus a small delta. Whether it transfers depends on who may hold every row.
Reality
A logarithm replaces both the payment table and the timer that would rewrite every row of it. The concurrency bug it does not remove is the more useful half of the writeup.
Reality