worktop/storage

[lukeed]

Or worktop/kvs or worktop/database
Depends if/how Durable Objects get worked in or if they should be their own separate module.

NOTE@SELF: Port this over from App2

[lukeed]

For now there is worktop/kv which (of course) is KV-specific.

I'm keeping this issue for Durable Objects integration. I've yet to experiment with DOs, so the API for working with them is very much unknown. That said, my current idea is that I'll combine the KV utilities (worktop/kv) with the DO utilities under a single worktop/storage submodule. Then, the current Database KV-class will be renamed to Model and there will be a new Actor class will be added for DO-facing setup. Names are TBD of course, because everything is TBD 🙃

[lukeed]

A new worktop/durable module was added in #80, which means there's no reason for this ticket to remain open. The new module is available under the worktop@next version and will released in the next stable (non-@next) version.

It's possible a new worktop/storage module would surface in the future, but probably not in the way(s) suggested earlier in this ticket.