Why NoSQL on GCP matters - Quick Recap

Recall & Review

beginner

What is NoSQL and how does it differ from traditional SQL databases?

NoSQL is a type of database that stores data in flexible ways like documents or key-value pairs, unlike SQL databases that use fixed tables and rows. This makes NoSQL better for handling large, changing, or unstructured data.

beginner

Why is NoSQL important for cloud applications on GCP?

NoSQL on GCP helps apps handle lots of data quickly and scale easily as users grow. It supports flexible data types and real-time updates, which are common needs in modern cloud apps.

intermediate

Name two NoSQL services offered by Google Cloud Platform.

Google Cloud offers Firestore and Bigtable as NoSQL services. Firestore is good for mobile and web apps with real-time syncing. Bigtable is great for big data and analytics.

intermediate

How does NoSQL on GCP support scalability?

NoSQL databases on GCP automatically handle more users and data by spreading data across many servers. This means apps stay fast and reliable even when demand grows.

beginner

What types of applications benefit most from using NoSQL on GCP?

Apps that need to store lots of different data types, update data in real-time, or handle huge amounts of data like gaming, IoT, and social media apps benefit most from NoSQL on GCP.

Which of the following is a NoSQL database service on GCP?

A Cloud Firestore

B Cloud SQL

C Cloud Spanner

D Cloud Storage

Cloud Firestore is a NoSQL document database service on GCP. Cloud SQL and Spanner are relational databases, and Cloud Storage is for file storage.

Why might a developer choose NoSQL over SQL on GCP?

A To use fixed table schemas only

B To avoid scaling the database

C To handle flexible and unstructured data easily

D To store only small amounts of data

NoSQL databases are designed to handle flexible, unstructured data, unlike SQL databases which require fixed schemas.

What is a key benefit of using NoSQL databases on GCP for cloud apps?

A Automatic scaling with demand

B Manual server management

C Only supports SQL queries

D Requires fixed data models

NoSQL databases on GCP automatically scale to handle more users and data without manual intervention.

Which GCP NoSQL service is best for real-time syncing in mobile apps?

A Cloud Bigtable

B Cloud Firestore

C Cloud SQL

D Cloud Dataproc

Cloud Firestore supports real-time syncing, making it ideal for mobile and web apps.

NoSQL databases are especially useful for applications that:

A Have fixed, structured data only

B Do not need to scale

C Only run on local machines

D Require flexible data models and fast scaling

NoSQL databases handle flexible data and scale quickly, which is important for many cloud applications.

Explain why NoSQL databases are important for modern cloud applications on Google Cloud Platform.

Think about how apps need to grow and change quickly in the cloud.

Describe the main differences between NoSQL and SQL databases and why you might choose NoSQL on GCP.

Consider how data is stored and how apps grow.

Practice

1. Why is NoSQL often chosen on Google Cloud Platform (GCP) for certain applications?

easy

A. Because it handles flexible and rapidly changing data well

B. Because it requires complex server management

C. Because it only supports structured data

D. Because it is slower than traditional databases

Solution

1. Step 1: Understand NoSQL data handling

   NoSQL databases are designed to store flexible, semi-structured, or unstructured data that can change quickly.

2. Step 2: Relate to GCP use case

   On GCP, NoSQL services like Firestore and Bigtable support fast-changing data without rigid schemas.

3. Final Answer:

   Because it handles flexible and rapidly changing data well -> Option A

4. Quick Check:

   NoSQL = flexible, fast-changing data [OK]

Hint: NoSQL = flexible data, not rigid tables [OK]

Common Mistakes:

• Thinking NoSQL requires complex server management
• Assuming NoSQL only supports structured data
• Believing NoSQL is slower than SQL

2. Which GCP NoSQL service is best described as a document database?

easy

A. Cloud Spanner

B. Cloud Bigtable

C. Cloud SQL

D. Cloud Firestore

Solution

1. Step 1: Identify document database on GCP

   Cloud Firestore stores data as documents in collections, making it a document database.

2. Step 2: Differentiate from other services

   Cloud Bigtable is a wide-column store, Cloud SQL and Spanner are relational databases.

3. Final Answer:

   Cloud Firestore -> Option D

4. Quick Check:

   Document DB on GCP = Firestore [OK]

Hint: Firestore = document DB, Bigtable = wide-column [OK]

Common Mistakes:

• Confusing Bigtable as document DB
• Choosing relational DBs like Cloud SQL
• Mixing Spanner with NoSQL services

3. Given this code snippet using Firestore on GCP:

doc_ref = firestore_client.collection('users').document('user123')
doc_ref.set({'name': 'Alice', 'age': 30})
user = doc_ref.get().to_dict()
print(user['name'])

What will be printed?

medium

A. user123

B. Alice

C. 30

D. None

Solution

1. Step 1: Understand Firestore document creation

   The code sets a document with fields 'name' and 'age' under 'users/user123'.

2. Step 2: Retrieve and print the 'name' field

   The get() call fetches the document, and user['name'] accesses the 'name' value, which is 'Alice'.

3. Final Answer:

   Alice -> Option B

4. Quick Check:

   Print user['name'] = Alice [OK]

Hint: Set then get document fields to print values [OK]

Common Mistakes:

• Printing document ID instead of field
• Confusing field names
• Assuming None if document exists

4. You try to write data to Cloud Bigtable but get an error. Which mistake likely caused it?

table = bigtable_client.table('my-table')
row = table.row('row1')
row.set_cell('cf1', 'name', 'Bob')
row.commit()

medium

A. Missing column family 'cf1' creation before setting cell

B. Using wrong row key format

C. Calling commit() before set_cell()

D. Bigtable does not support string values

Solution

1. Step 1: Check Bigtable column family setup

   Bigtable requires column families to exist before writing cells; 'cf1' must be created first.

2. Step 2: Verify code sequence and data types

   Row key format is valid, commit() is correctly called after set_cell(), and Bigtable supports string values.

3. Final Answer:

   Missing column family 'cf1' creation before setting cell -> Option A

4. Quick Check:

   Column family must exist before writing [OK]

Hint: Create column family before writing cells [OK]

Common Mistakes:

• Forgetting to create column family
• Assuming commit() order is wrong
• Thinking Bigtable rejects strings

5. You want to build a scalable app on GCP that needs to store user profiles with flexible fields and also handle millions of fast writes per second. Which combination of NoSQL services should you choose?

hard

A. Use Cloud SQL for profiles and Cloud Spanner for writes

B. Use Cloud Bigtable for profiles and Cloud Firestore for writes

C. Use Cloud Firestore for flexible profiles and Cloud Bigtable for high-speed writes

D. Use Cloud Spanner for both profiles and writes

Solution

1. Step 1: Match data needs to NoSQL services

   Cloud Firestore handles flexible, document-based user profiles well.

2. Step 2: Match write speed needs

   Cloud Bigtable supports massive scale and very fast writes, ideal for high throughput.

3. Step 3: Evaluate other options

   Cloud SQL and Spanner are relational and less suited for flexible schema or extreme write speed.

4. Final Answer:

   Use Cloud Firestore for flexible profiles and Cloud Bigtable for high-speed writes -> Option C

5. Quick Check:

   Firestore + Bigtable = flexible + fast writes [OK]

Hint: Firestore for flexible data, Bigtable for speed [OK]

Common Mistakes:

• Choosing relational DBs for flexible schema
• Swapping Firestore and Bigtable roles
• Ignoring write speed requirements