This is part 2 of the Tigris Data Modeling Series. In the first part of the series, we covered modeling one-to-one relations. In this second part of the series, we will explore modeling one-to-many relations. We'll look at two ways to implement one-to-many relations. The first uses an embedded 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 document database, this allows you to model 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 get up and running with Tigris and how to model one-to-one relationships using the embedded document and sub-document pattern. We will combine this with Tigris's transactions to make sure that all updates are consistent. I will show how to model one-to-many and many-to-many relationships in future posts.
