Up to this point you have met relational, NoSQL, and hierarchical databases one at a time. This topic places them side by side so you can see how their structures, schemas, query languages, scaling behavior, and consistency guarantees differ — and, more importantly, why those differences matter when someone has to pick one for a real system.
There is no "best" database. A rigid schema that feels restrictive in one project is exactly what protects financial records in another; a flexible document store that speeds up a startup's prototype can quietly allow inconsistent data later. The goal here is to build a mental checklist of selection criteria: What does the data look like? How will it be queried? How much will it grow? How costly is an inconsistent read?
As you watch the two videos below, keep a comparison table in your notes with columns for structure, schema flexibility, query power, scalability, and integrity. Note the vocabulary each speaker uses (normalization, joins, ACID, horizontal versus vertical scaling, eventual consistency) and jot down the example use cases they mention — you will be asked to justify database choices for similar scenarios later in this module.
An IBM Technology explainer that contrasts relational databases with non-relational (NoSQL) alternatives. Based on its title and description, it is likely to walk through how tables, rows, and columns with predefined schemas compare to document, key-value, and other non-relational structures, and to touch on where each approach performs well in terms of flexibility, scale, and the kind of querying it supports.
IBM Technology produces concise, vendor-neutral conceptual overviews, and this one maps directly onto the structural differences, schema flexibility, and query power subtopics by addressing the core relational-versus-NoSQL contrast at the heart of this comparison.
A ByteByteGo video framed around the practical question of how to choose a database for a given system. From its title and the channel's system design focus, expect a tour of major database families and the criteria engineers weigh — data shape, query patterns, scale and performance demands, and consistency requirements — with example scenarios that match categories to workloads.
ByteByteGo is widely used for system design preparation and specializes in exactly this decision-making framing, making it a strong fit for the scalability trade-offs, ideal use cases, and key selection criteria subtopics.
Together these videos reinforce the comparison and selection outcomes of this module. The IBM Technology video supports MO2 and MO3 by clarifying how relational and non-relational models organize data differently and how that drives schema, query, and scaling trade-offs, while reinforcing the vocabulary introduced in MO1. The ByteByteGo video extends this toward MO4 and MO5 by modeling how practitioners weigh criteria and match database types to concrete application and industry scenarios. Watched in sequence, they move you from understanding the differences to being able to justify a choice.
These videos were chosen from YouTube on October 2, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.