NoSql One-to-Many Relation Examples; Bound And Unbound Cases

What Are The Options To Properly Model 1-to-Many Scenarios And Which One Is Right?

In NoSql data modeling post, I have explained NoSql data modeling and that there are three ways to model one to many relationships. In this post, I will list real-world examples of one to many relationship — both bound and unbound — in which application of different ways of modeling are possible (or not).

[Read More]

NoSql Example Of Separate Collections In One-to-One Relationship; Case Of Specialization And Generalization

When And Why Should Reference Be Used To Link Documents In 1-1 Relation

In my detailed post on NoSql data modeling, I listed down ways of modeling NoSql data (using mongodb collections). For one-to-one relation, usually, it is not apparent why one needs a separate collection instead of embedding everything in single document.

[Read More]

How To Draw NoSql Data Model Diagram?

NoSql, unlike SQL which has ER and class diagrams, has neither names nor constraints for data modeling diagram(s). The obvious reason is the relax rules of NoSql about relationships, which aim to get a developer started with minimum requirements.

[Read More]

NoSql Data Modeling: 1 to 1, 1 to Many, Many to Many

In contrast to SQL, NoSql data modelling allows multiple ways to model 1 to 1, 1 to many and many to many relationships. It does not enforce rules or favors a particular design. The only constraint is application requirements. Coming from SQL background, I struggled modeling Couchbase and MongoDb applications. [Read More]