Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

RavenDB Conference Videos: Should I Use a Document Database?

DZone's Guide to

RavenDB Conference Videos: Should I Use a Document Database?

As always, no one database is right for all solutions, but document DBs have an edge when dealing with large amounts of data. Check out the benefits and use cases.

· Database Zone ·
Free Resource

RavenDB vs MongoDB: Which is Better? This White Paper compares the two leading NoSQL Document Databases on 9 features to find out which is the best solution for your next project.  

In this talk from the RavenDB conference, Elemar Júnior discusses the differences between relational and document databases — and how you can utilize RavenDB for best effect.

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 fewer 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.

Get comfortable using NoSQL in a free, self-directed learning course provided by RavenDB. Learn to create fully-functional real-world programs on NoSQL Databases. Register today.

Topics:
databases ,ravendb ,document database ,nosql

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}