This is part 3 of the NoSQL Data Modeling Series. In part one of the series, we covered modeling NoSQL one-to-one relations. and in part two we explored modeling NoSQL one-to-many relations. This is the third and final post and we will dive into modeling NoSQL many-to-many relations.
We model NoSQL many-to-many relations in two ways:
For the second example we'll use related documents and demonstrate full-text search to perform advanced queries against our data.
This is part 2 of the NoSQL Data Modeling Series. In the first part of the series, we covered modeling NoSQL one-to-one relations. In this second part of the series, we will explore modeling NoSQL one-to-many relations. We'll look at two ways to implement NoSQL one-to-many relations. The first uses an embedded NoSQL design pattern, and the second uses a separate collection with a relation field. We will also look at when it is best to use either of these designs.
Tigris provides a transactional NoSQL document database, this allows you to create NoSQL data models representing relations in a few different ways to get the best performance, consistency and ease of use in your application.
In this blog, I show you how to model NoSQL one-to-one relationships using the embedded document and sub-document NoSQL design pattern. We'll get hands-on with Tigris to achieve this, however the NoSQL data modeling design patterns are applicable to other NoSQL databases. We will combine this with Tigris's transactions to make sure that all updates are consistent. I will show how to model NoSQL one-to-many and NoSQL many-to-many relationships in future posts as part of the NoSQL Data Modeling Series.
