Durable Objects: one instance per name
With 1.18, a worker can export a class whose instances each have a name, their own storage and their own WebSockets. How it works in the runner, and what we found on the way.
Read more →Blog
Engineering notes from building a workers platform: measurements, mechanisms, and the failures worth writing down.
One binary: removing nginx, NATS and two services from OpenWorkers
With 1.15, one runner serves HTTP and HTTPS, starts the crons and stores the logs. Seven services became three, and what a single node gives up in return.
Read more →The control plane is just another worker
With 0.15, the OpenWorkers API and dashboard run as a worker on OpenWorkers. What dogfooding-only changes, and what it deliberately forbids.
Read more →Anatomy of a V8 cold start
Startup snapshots save 6%, per-script code caches save 62%. Where the time actually goes when a worker wakes to render a page.
Read more →Running workers-rs without JavaScript
A Cloudflare workers-rs app, one Cargo rename, zero JS glue - served as a native WASM component. Then Go, and what its numbers teach.
Read more →Five engines, one page, one sha256
How a conformance oracle made five JavaScript engines render the same SvelteKit page byte-for-byte, and the bugs it caught - including one in the reference engine.
Read more →Retiring a rusty_v8 fork
Upstream landed the isolate locker our fork existed for. What migrating six V8 majors actually broke, and what a fork should shrink to.
Read more →Introducing OpenWorkers
Self-hosted Cloudflare Workers in Rust.
Read more →