Cardinality

How many rows match? This determines whether your result grows, shrinks, or stays the same size. Cardinality describes how many rows in one table match rows in another. Understanding cardinality helps you predict what your join results will look like. One-to-One (1:1) Each row in table A matches exactly one row in table B, and vice versa. Example: users and user_profiles tables Result: Same number of rows as each input table. One-to-Many (1:N) Each row in table A can match multiple rows in table B. This is the most common relationship. Example: One customer has many orders Result: More rows than the "one" side table. Alice appears 3 times, Bob 2 times, Carol once. Many-to-Many (N:N) Multiple rows in table A can match multiple rows in table B. This often requires a "bridge" table. Example:

About This Interactive Section

This section is part of the Joins: Beginner lesson on DataDriven, a free data engineering interview prep platform. Each section includes explanations, worked examples, and hands-on code challenges that execute in real time. SQL queries run against a live PostgreSQL database. Python runs in a sandboxed Docker container. Data modeling problems validate against interactive schema canvases. All content is framed around what data engineering interviewers actually test at companies like Meta, Google, Amazon, Netflix, Stripe, and Databricks.

How DataDriven Lessons Work

DataDriven combines four interview rounds (SQL, Python, Data Modeling, Pipeline Architecture) with adaptive difficulty and spaced repetition. Easy problems get harder as you improve. Weak concepts resurface until you master them. Your readiness score tracks progress across every topic interviewers test. Every lesson section ends with problems you solve by writing and running real code, not by picking multiple-choice answers.