Monotonic growth and deletion

[micrology]

This looks great. However, I don't see any way of pruning the database, so as clients create and edit docs, the persistence element will store an increasing amount of data in the attached database, with no option to ever prune it. Potentially the volume of data could become enormous (this is also true of all the y-websocket variations I have seen). This would be a problem if the code was used in a production environment with large numbers of users performing large numbers of edits.

What should be discarded and when will depend on the use case, but if I have understood this right, it wouldn't be possible to discard data using this backend as currently implemented.

[kapv89]

Hey ... So if you look at the main branch ... updates are pruned when they are fetched by combining them into a single update if the number of updates are above a certain size. This is the same strategy as followed by y-leveldb. In the external_api_persistence branch, you can implement the backend api in such a way that it prunes updates while reading and/or writing ... (would suggest while reading because of the bature of reads and writes)