[gfodor]

Thank you for releasing this! Had a question: if I have worker code that uses other Cloudflare storage APIs like KV or R2, what would you recommend as far as shimming those calls so this code could run via workerd (but, for example, just use basic process-local in-memory storage for now.) Is that doable? For my use case durability isn’t that important and I’d like to offer people the ability to self host my code via workerd.

[kentonv]

workerd includes implementations of the KV and R2 binding APIs, which convert all your calls into HTTP requests under the hood. You can point that at another Worker or to a separate HTTP service to implement the storage behind them. We plan to provide some example implementations in the future that store to disk or a database.

[gfodor]

amazing, thank you!

[lijogdfljk]

re: self hosting,

I'm curious on the use cases for self hosting? Ie i have a heavy interest in self hosting. I also find workerd very interesting. Though i'm struggling to think of reasons why i'd build my apps around workerd instead of just a process.

If i was dedicated to WASM, Perhaps workerd might be a better solution than wasmer, unsure.

[gfodor]

The use case I'm referring to is where someone (in this case, me) publishes code intended to be run on Cloudflare Workers or self hosted with workerd.

Reasons you'd write first party code targeting workerd would be a different question.