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.