Objective

To gain hands-on experience with four distinct NoSQL database models (Key-Value, Columnar, Document, and Graph) and to understand the specific use cases and architectural trade-offs associated with each.

A Quick Word of Encouragement: This will be our longest and most diverse lab. We are going to move quickly through four different types of NoSQL databases. The goal is not to become an expert in any single one, but to experience firsthand how their different data models feel and what kinds of problems they are designed to solve. Don't worry about mastering every command; focus on the core concepts and the "aha!" moments.

Start Where You Are

In Lab D, you worked extensively with the relational model, where data is organized into structured tables with rows and columns. That is the foundation for a vast number of applications.

Now, we will explore the "post-genre" world of NoSQL. Think back to Chapter 3, where we saw different data formats like CSV, JSON, and hierarchical text. NoSQL databases are built to store and query data in these alternative formats, often prioritizing scale and flexibility over the strict consistency of traditional relational systems. Each model you interact with today is a different answer to the question: "What is the most efficient way to organize this specific type of data?"

For this lab, your submission will consist only of the required screenshots, your response to one of the reflection questions, and a brief paragraph on your overall experience.

Part A: The Key-Value Store with Redis

We begin with the simplest model: the key-value store. It functions like a massive, distributed dictionary or luggage tag system. You have a unique key, and you store a value. It's incredibly fast and scalable.

Step 1: Sign Up for a Free Redis Account:

Step 2: Add Data Using the Redis Insight Tool: