We’ve been building an editing experience on top of yjs and y-websocket running as server from the bib directory.
Specifically - this is currently being used a collaboration cache, and is something that can re restarted, migrated etc, without worrying about the data, as that is being stored elsewhere, by syncing contents from individual rooms.
I came across https://github.com/yjs/ydb, which actually seems to be a database built with yjs, but has not seen activity in some time. It is also lacking documentations.
Provided I’m looking for a “single node” data store of yjs documents that can be the final store for end documents, is ydb a good choice? Specifically,
- is there a backing store option (can I plugin in postgres or mysql or other managed db node)
- I don’t care about horizontal scaling - simple vertical scaling can fit my usecase.
- is the internal data schema of yjs frozen? so that this data will be accessible for the foreseaable future of yjs?
Right now I’m investing in dumping room data as json and storing it, but I can skip that if ydb is a reasonable option for it.
Is there any help I can offer on above?