How should CouchDB revisions be handled in terms of design?

Question

Nearby, as I can tell, CouchDB changes should not be considered revisions in the meaning of the word documenting . From looking at other messages, they are apparently regarded as temporary data that exists until a coarse compact operation is output.

My question is: if I am interested in using CouchDB to support documents, as well as in the version history of these documents, should I allow processing using CouchDB patches, or do I need to create a layer on top of it that can withstand a compact operation?

I think of the latter, simply because Couch does not replicate document revisions, but only the latest update. This makes me think that the version is the wrong name, as it is more of a data structure to stabilize replication.

Answer 1

You must create this layer because couchdb versions are not a version control system for your data.

'revision' is misleading, as is the 'version', and therefore there are all the names that have been proposed so far. Suggestions are welcome, at least to confirm how difficult it is to call it.