[paulgb]

(oh hey, author of that article here :))

This is something I've been thinking a lot about as well. A cool approach I've been experimenting with is using a CRDT for the underlying document data, and taking snapshots of the logical clock that correspond to version numbers. If you don't garbage-collect the CRDT, you can then restore the value based on the logical clock.

The CRDT itself can be persisted to S3 or similar, as in that article. We’ve been working on this in the open, so you can follow along: https://y-sweet.dev/

[bostonvaulter2]

Ah, thanks for the link. Yeah a CRDT would be pretty nice although there's soo many constraints that you accept with one.

Thanks for the link to y-sweet! That's pretty sweet! ;)