Over a million developers have joined DZone.

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

Learn how to move from MongoDB to Couchbase Server for consistent high performance in distributed environments at any scale.

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.

Want to deliver a whole new level of customer experience? Learn how to make your move from MongoDB to Couchbase Server.

databases ,ravendb ,document database ,nosql

Published at DZone with permission of Oren Eini, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.


Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.


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

{{ parent.tldr }}

{{ parent.urlSource.name }}