In this talk from the RavenDB conference, Elemar Júnior is talking about the differences between relational and document databases, and how you can utilize RavenDB for best effect.
I’ll hint that the answer to the question in the title is: Yes, RavenDB.
For the last 40 years or so, we used relational databases successfully in nearly all business contexts and systems of nearly all sizes. Therefore, if you feel no pain using a RDBMS, you can stay with it. But, if you always have to work around your RDBMS to get your job done, a document oriented database might be worth a look.
RavenDB is a 2nd generation document database that allows you to write a data-access layer with much more freedom and many less constraints. If you have to work with large volumes of data, thousands of queries per second, unstructured/semi-structured data or event sourcing, you will find RavenDB particularly rewarding.
In this talk we will explore some document database usage scenarios. I will share some data modeling techniques and many architectural criteria to help you to decide where safely adopt RavenDB as a right choice.
More posts in "RavenDB Conference videos" series:
- (03 Mar 2017) Replication changes in 3.5
- (01 Mar 2017) Delving into Documents with Data Subscriptions
- (27 Feb 2017) Building Codealike
- (23 Feb 2017) Implementing CQRS and Event Sourcing with RavenDB
- (21 Feb 2017) Zapping ever faster
- (17 Feb 2017) Should I use a document database?
- (15 Feb 2017) Know Thy Costs
- (13 Feb 2017) Lessons from the Trenches
- (09 Feb 2017) RavenDB Embedded at Massive Scales
- (07 Feb 2017) RavenDB for the Modern Web Developer
- (03 Feb 2017) Introducing RavenDB 4.0
- (01 Feb 2017) Introducing RavenDB 3.5