Skip to Navigation
One of the primary differences between a relational database and a document database is the way that you model your data.
In a relational database there are well known patterns that are called normal forms. The aim is to reduce duplication to make sure that you record a piece of data once. The downside is when you need to actually check where the data is. It becomes a lot harder to track it because you may have to go through multiple hoops.
The classic example is to show the name of the user on an invoice.
The invoice does not contain the name of the user, only the invoice ID so when your database is reading it, it also has to look up the users record.
Using a Document Database model, there are a lot of features in RavenDB that effectively handle many of the challenges relational databases force upon you to make your life a lot easier.
There are many ways you can model your data with RavenDB using attachments, counters, and Time Series. RavenDB is built so you can even model your data using indexes.
In this webinar, RavenDB CEO Oren Eini shows you how to model your data with the next generation of database.
You will learn:
- How relational databases are modeled
- The challenges these databases present developers
- How you can use RavenDB to model your data
- Taking advantage of indexes, Time Series, attachments, and other features to model your data
