Database should be partitioned

[christophe-lejeune]

According to my experience with Couchdb, the platform is really efficient when the project starts, but it slow down when you store a lot of documents (as it is the case with Cassandre). After many attempts to speed it up, it appears that such an application falls under what partitions were designed for. For these reasons, I would advise to use partitioned databases for HyperGlosae.

[benel]

Thank you for the idea @christophe-lejeune.
Here is CouchDB manual on partitioned database for further reference.

[benel]

An important decision related to this issue will be the choice of what would be used as a partition ID.

@christophe-lejeune What was it in Cassandre? The diary ID? The user who first created the document?

In Hyperglosae:

• the equivalent of the diary would be the common ancestor of all related documents... When they are several, I suppose it won't break performances...
• I don't think the creator would be a performance gain, since the objective is to read together documents created by different people...

[christophe-lejeune]

I confirm that I would choose the diary. But, currently, Cassandre does not rest on partitioned database yet. Indeed, switching to such a design implies a huge refactoring that I have not undertaken yet. That's why I shared this insight soon. It is easier to build something on a partitioned database than to switch an existing project from one design to another.