0:0037:53

What Is NoSQL?

Heather Maga 37:53 2020

In NoSQL, the database stops checking your data and the developer takes over

A relational database rejects a record that breaks its rules; a NoSQL database typically does not, and checking the data falls to whoever writes the code. Heather Maga, a software developer who teaches database systems at Loyalist College, explains what that trade buys in flexibility and scaling. The harder question she tackles: when should related data live inside one document, and when should it be linked?

Learn the four NoSQL types and a checklist for choosing between embedding and referencing data

Watch on YouTube

In short

Heather Maga gives a no-code, beginner overview of NoSQL databases: what schemaless means, the four main types and how they compare with relational schemas. She explains how to decide between embedding and referencing related data, and why scalability, cost, flexibility and availability lead teams to adopt NoSQL.

“So, NoSQL, very briefly, is a database that does not use SQL to access the data stored within it.”
“So, it's up to the developer in the front end to make sure that the required information is saved into the database in the correct format.”

What you will learn

  • Distinguish a fixed relational schema from a schemaless NoSQL design and know who enforces the data rules in each.
  • Identify the four main NoSQL types: key-value, document, column and graph.
  • Decide when to embed related data and when to reference it, based on access patterns, relationship type and change frequency.
  • Weigh scalability, cost, flexibility and availability when considering a move to NoSQL.
  • Spot two common starting points: new projects expecting rapid growth and NoSQL layers that serve APIs over legacy relational databases.

Details

Level
Beginner
Format
Talk
Technical depth
Introductory technical
For
Student, Early career, Career changer
Length
37:53
Published
July 2020

Questions this talk answers

What is a NoSQL database?

It is a database that does not use SQL to access its data and is schemaless, so its structure can change over time and documents can have different attributes.

What are the main types of NoSQL databases?

There are four main types: key-value, document, column and graph databases.

When should related data be embedded and when should it be referenced?

Embed data that is queried together, weak entities such as invoice line items, and one-to-one or one-to-few relationships. Reference for one-to-many and many-to-many relationships, entities that change at different frequencies or are not queried together, and entities used by many others.

Why would an organization consider moving to NoSQL?

Growing data and user volumes slow response times and put availability at risk on a single server. NoSQL scales out across servers, many major options are open source, attributes are easy to add, and a cluster keeps running if one server fails.

Who is responsible for data integrity in a NoSQL database?

For data going in, the responsibility lies with the software, meaning the programmer or developer who writes the data to the database.

About this talk

No code! No deep-dives. This talk will be a basic overview for people that do not have experience with NoSQL databases. I will cover general information about what NoSQL is, how it fits into modern development, and how it compares to traditional relational database schemas.

I won't be going into specifics but instead, be giving you the jump start you need to explore the concepts further on your own. This means you do not need any prior knowledge of NoSQL but it would be useful to have some knowledge of traditional relational databases.

Topics

Related talks

Browse the library