Connecting to production: the architecture of remote bindings

This post details the architecture of Cloudflare's new remote bindings feature for Workers. It explains how the local development environment (workerd) now translates binding calls to remote resources (like KV, R2, D1, AI) by proxying requests to production runtime instances. This is achieved by leveraging the existing service binding architecture, where platform Workers communicate with authored Workers via HTTP or JSRPC. For JSRPC-backed bindings, websockets and Cap'n Web are used for communication. The post also outlines how this functionality is integrated into tools like Vite and Vitest.