In NoSql data modeling I analyzed NoSql data modeling and ways to model many to many relationships. In another post I added a few examples of 1-to-many bound and unbound cases. Presently, I’ll illustrate bound and unbound cases for many-to-many. [Read More]
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’ve explained NoSql data modeling and that there are three ways to model one to many relationships. In this post I’ll 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’s not apparent why one needs a separate collection instead of embedding everything in single document. In this post I’ll address this and share an example. [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 NoSql’s lack of hard and fast relationship rules, which aims to get a developer started with minimum requirements. [Read More]
NoSql Data Modeling: 1 to 1, 1 to Many, Many to Many
Surprisingly, data modeling for NoSql databases doesn’t get much traction compared with SQL. 1 to 1, 1 to many and many to many; all can be modeled multiple ways. No favoring of a particular choice, no required normalization. The only constraint is application requirements. [Read More]