Computer Science · Grade 11

Active learning ideas

Introduction to NoSQL Databases

Active learning helps students grasp NoSQL databases because the concepts are abstract and benefit from direct interaction with data structures. Comparing schema designs and solving real migration problems make the differences between relational and NoSQL systems tangible and memorable.

• Ontario Curriculum Expectations
• CS.HS.D.5

• 25–45 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Case Study Analysis
• 30 min · Pairs

Pairs: Schema Comparison Challenge

Provide sample datasets for a blog app. Pairs sketch relational schemas with tables and foreign keys, then redesign using document and key-value NoSQL models. Discuss advantages in scalability and flexibility for each.

Differentiate between relational and NoSQL database models.

Facilitation Tip

During the Schema Comparison Challenge, provide a printed side-by-side table of a relational schema and a document schema to help students visualize differences before they discuss.

What to look for

Provide students with two brief descriptions of data storage needs for hypothetical applications. Ask them to identify which application would benefit more from a relational database and which from a NoSQL database, and to briefly justify their choices.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

Activity 02

• Case Study Analysis
• 45 min · Small Groups

Small Groups: Use Case Analysis Stations

Set up stations for e-commerce, social feeds, and logging apps. Groups match scenarios to database types, justify choices with pros and cons, then rotate and critique peers' decisions.

Analyze scenarios where a NoSQL database would be more appropriate than a relational one.

Facilitation Tip

At each Use Case Analysis Station, give students a short scenario and a timer to focus their discussion on scalability and flexibility before they rotate.

What to look for

Pose the question: 'Imagine you are building a new application that needs to store user profiles with potentially diverse information fields. What are the primary advantages and disadvantages of using a document database versus a traditional relational database for this task?' Facilitate a class discussion on their reasoning.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

Activity 03

• Case Study Analysis
• 35 min · Whole Class

Whole Class: Migration Simulation

Display a relational dataset on the board. Class votes on NoSQL target type, then collaboratively maps fields while noting challenges like denormalization. Simulate queries before and after.

Predict the challenges of migrating data between different database types.

Facilitation Tip

In the Migration Simulation, assign clear roles like data architect, application developer, and database administrator to make the transformation process collaborative and realistic.

What to look for

Present students with a list of database characteristics (e.g., fixed schema, high scalability, complex queries, ACID compliance). Ask them to sort these characteristics into two columns: 'Typically Relational' and 'Typically NoSQL'. Review their responses for common misconceptions.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

Activity 04

• Case Study Analysis
• 25 min · Individual

Individual: Playground Prototyping

Students use free online MongoDB or Redis playgrounds to insert varied data and run queries. Note differences from SQL syntax and reflect on when each excels.

Differentiate between relational and NoSQL database models.

Facilitation Tip

For Playground Prototyping, provide a sandbox environment with sample data so students can immediately test queries without setup delays.

What to look for

Provide students with two brief descriptions of data storage needs for hypothetical applications. Ask them to identify which application would benefit more from a relational database and which from a NoSQL database, and to briefly justify their choices.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

A few notes on teaching this unit

Teachers should avoid presenting NoSQL as universally superior or simpler than relational systems. Instead, use contrasting examples to show that each model solves specific problems. Research shows that hands-on schema design and query practice prevent oversimplification and misconceptions about data relationships. Encourage students to reflect on when strict schemas help and when flexibility matters most.

Successful learning shows when students can explain why NoSQL fits certain use cases better than relational databases and when they can design simple NoSQL schemas for given scenarios. They should also recognize that performance and structure depend on workload and data patterns, not on the database type alone.

---

Watch Out for These Misconceptions

• During the Schema Comparison Challenge, watch for students assuming NoSQL databases always outperform relational ones in speed.

  Use the provided comparison table to guide students to examine read/write patterns and transaction types, emphasizing that relational databases often handle complex joins better.

• During Playground Prototyping, watch for students believing NoSQL has no structure or relationships at all.

  Have students build nested documents and run queries to demonstrate embedded relationships, then discuss how this structure differs from relational joins.

• During the Migration Simulation, watch for students expecting to reuse relational queries directly in NoSQL.

  Ask groups to rewrite a sample relational query into NoSQL syntax and discuss why data reshaping is necessary, highlighting query language differences.

---

Methods used in this brief

• Case Study Analysis