Long-lived objects in Dynamic Workers: Give each AI-generated app its own database

We announced it a few weeks ago Dynamic workersa new feature of the Workers platform that allows you to quickly load worker code into a secure sandbox. The Dynamic Worker Loader API essentially provides direct access to the core compute isolation primitive that Workers has always been based on: isolates, not containers. Isolates are much lighter than containers and therefore can load 100x faster with 1/10th of the memory. They are so efficient that they can be treated as “disposable”: start one to run a few lines of code, then throw it away. Like a safe version of eval().

Dynamic workers have many possible uses. In the original announcement, we focused on how to use them to execute code generated by AI agents as an alternative to tool calls. In this use case, an AI agent performs actions at a user’s request by writing a few lines of code and executing them. The code is single-use, designed to perform a task once, and is discarded immediately after execution.

But what if you…