Spike: Strong relations in Cloudant & CouchDB

[bajtos]

Research what tools are offered by CouchDB and Cloudant for ensuring referential integrity.

Come up with a proposal on how LoopBack applications should implement the following relations:

• 1-N (hasMany)
• N-1 (belongsTo)
• 1-1 (hasOne/belongsTo)

For example, we can recommend referencesMany or embedsMany, but also find out that a completely new relation type is needed.

See #2127 for wider context and #1718 (comment) for explanation of strong vs. weak relations.

Acceptance criteria

• A document explaining what mechanisms are offered by CouchDB & Cloudant to preserve consistency (integrity). (Start by studying Cloudant documentation and guides to build this understanding yourself.)
• A proposal: what LoopBack relations we want to recommend for CouchDB and Cloudant
• Arguments showing why we recommended the chosen relations, why other relations won't work with Cloudant/CouchDB. (This will build on top of the document from the first task.)
• User stories to implement the missing relation types identified as needed. If needed, create spike stories to figure out implementation details of some/all of these relation types.
• A pull request to update the overview created in Docs: what relation types will work well with my database? #2341 with our recommendation (item 2) and our arguments (item 3). If we end up recommending relation types that are not implemented yet, then the overview should be updated with links to GH stories tracking these missing features.

[jannyHou]

Timebox to 5 days

[stale]

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

[stale]

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.