There is a chance of lost updates when working with separate association documents instead of storing associations in-entity in CouchDB. The reason is that we need to re-read association documents when e.g. merging an entity passed back from a client application. Unlike for entity revisions we don't have a "handle" to the association document's revision in such a case, so I'm not quite sure how to address the issue.