ICCT logo

Internal academy

ICCT Training Library

Data & Automation

Database Platforms: PostgreSQL and MongoDB

Compare relational and document-style databases so students can choose the right storage model, write stronger queries, and explain the tradeoffs behind each platform.

Intermediate 3 credits 50+ guided hours 5 weeks Modules: 3 Projects: 2

Easy Interactive curriculum

Data Arcade for short, easy-to-digest learning

This course breaks big data & automation ideas into short missions, plain-language definitions, and interactive practice rounds. Compare relational and document-style databases so students can choose the right storage model, write stronger queries, and explain the tradeoffs behind each platform.

Class missions: 3 10 minutes per topic Lab + quiz + homework + game

Class mission

Choosing the data model

Minutes: 20

Big idea: Start with the shape of the problem instead of the popularity of the tool. We keep it simple, hands-on, and easy to explain back.

10 min

Relational thinking in PostgreSQL

PostgreSQL means a powerful database used for reliable data storage and queries In this topic we use it for tables, keys, and reporting-friendly normalization.

Quick picture: imagine using this in operational records.

Mission: use PostgreSQL to practice tables, keys, and reporting-friendly normalization.

PostgreSQL Model Database MongoDB
10 min

Document thinking in MongoDB

MongoDB means a database that stores information more like documents than rows In this topic we use it for nested records, flexible structures, and quick iteration.

Quick picture: imagine using this in content catalogs.

Mission: use MongoDB to practice nested records, flexible structures, and quick iteration.

MongoDB Model Database PostgreSQL

Word wall

Terms made easy

PostgreSQL

a powerful database used for reliable data storage and queries

Model

the brain-like engine an AI tool uses to answer and create things

Database

a place where information is stored in an organized way

MongoDB

a database that stores information more like documents than rows

Lab mission

Lab Mission

Design the same program catalog once as a relational model and once as a document model.

  1. Look at one example from operational records and point to where PostgreSQL shows up.
  2. Build one tiny version that uses PostgreSQL and Model in the right place.
  3. Tell a teacher or partner what you changed, what worked, and what you would improve next.
Homework

Homework: teach PostgreSQL in your own words, then create relational schema with one example, one picture, or one tiny screenshot.

Quick quiz

Check understanding in a friendly way

Game mode

Term Match Sprint

Matches: 0 / 4

Match each word to the right meaning as fast as you can.

Words
Meanings

Pick a word, then pick the matching meaning.

Outcomes

What students should leave with

  • Explain when relational structure is a better fit and when document structure is more practical.
  • Write core queries and modeling decisions in both PostgreSQL and MongoDB contexts.
  • Design data storage with reporting, flexibility, and maintenance in mind.

Reference map

Core topics to cover

Relational modeling Document modeling Indexes Joins Aggregation Schema evolution Data tradeoffs

Module sequence

ICCT lesson flow

Module 1

Choosing the data model

Lessons: 2

Start with the shape of the problem instead of the popularity of the tool.

Relational thinking in PostgreSQL

tables, keys, and reporting-friendly normalization

Document thinking in MongoDB

nested records, flexible structures, and quick iteration

Checkpoint lab

Design the same program catalog once as a relational model and once as a document model.

Module 2

Querying for real work

Lessons: 2

Use each platform to answer the kinds of questions teams actually ask.

SQL joins and reporting queries

combining tables for operational reporting

Document aggregation and filtering

extracting useful views from nested records

Checkpoint lab

Answer a shared reporting prompt in both platforms and compare the workflow.

Module 3

Scale, change, and maintainability

Lessons: 2

Think ahead about how the storage choice affects the future team.

Indexes and performance basics

making common queries faster

Schema evolution and long-term support

how data models change over time

Checkpoint lab

Write a recommendation memo for which platform should back a new internal content service.

Capstone prompts

Projects students can actually ship

Hybrid Data Design

Plan a system that uses relational storage for reporting and document storage for content flexibility.

Platform Recommendation Brief

Choose the best database for one school workflow and justify the decision with clear tradeoffs.