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

Model Your Relational Database Data as NoSQL Document Data [Video]

DZone's Guide to

Model Your Relational Database Data as NoSQL Document Data [Video]

If you've spent your life working with SQL, it might be tempting and jarring to consider the alternatives. Here's a video showing one developer's look at the other side.

· Database Zone
Free Resource

Traditional relational databases weren’t designed for today’s customers. Learn about the world’s first NoSQL Engagement Database purpose-built for the new era of customer experience.

When I'm presenting at events, I often get questions around data modeling. It is common to interact with developers that work with relational databases, but who are very interested in NoSQL. I, for example, started my database career with an Oracle and Microsoft SQL Server database. Having become familiar with structured RDBMS data, the concept of NoSQL was very strange. What does your data look like?  How do you query it?

In this video I put together, I give a quick overview on some ways to model data in Couchbase.  I list a simple RDBMS example and convert it to JSON document format. In the end, I query it and it is like there was no switch between databases.


Although the above video doesn't go into everything, it should be enough to put you on a solid path.  If something still doesn't make sense, I encourage you to put a question in the comments section.

For information on using these NoSQL documents in your application, check out the developer portal for examples.

Related Refcard:

Learn how the world’s first NoSQL Engagement Database delivers unparalleled performance at any scale for customer experience innovation that never ends.

Topics:
modeling ,microsoft sql server ,json ,relational databases ,sql ,path ,database ,nosql ,data modeling ,rdbms

Published at DZone with permission of Nic Raboy, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}