Bigtable schema design in GCP - Mini Project: Build & Apply

Bigtable Schema Design for User Activity Tracking

📖 Scenario: You are building a system to track user activities on a website. Each user can perform multiple actions like login, logout, and page views. You want to store this data efficiently in Google Cloud Bigtable.

🎯 Goal: Create a Bigtable schema design that organizes user activity data by user ID and timestamp, with columns for action type and details.

📋 What You'll Learn

Create a table schema with a row key combining user ID and timestamp

Define column families for 'activity' data

Include columns for 'action' and 'details' under the 'activity' column family

Use a timestamp format that allows sorting by time

💡 Why This Matters

🌍 Real World

Bigtable is used in real-world applications to store large amounts of time-series or user activity data efficiently.

💼 Career

Understanding Bigtable schema design is important for roles in cloud data engineering and backend development working with scalable databases.

1

Create the initial table schema

Create a Bigtable table schema with a row key named row_key that combines user_id and timestamp as a string. Define a column family called activity.

GCP

# Define the table schema with row_key and activity column family
# Your code here

Hint

Use a dictionary named table_schema with keys row_key and column_families.

2

Add columns for action and details

Add columns action and details under the activity column family in the table_schema dictionary.

GCP

table_schema = {
    'row_key': 'user_id#timestamp',
    'column_families': ['activity'],
    # Add columns 'action' and 'details' under 'activity'
    'columns': {
        'activity': []
    }
}
# Your code here

Hint

Use a nested dictionary for columns with activity as key and list of columns as value.

3

Define the timestamp format for sorting

Add a variable timestamp_format and set it to the string 'YYYYMMDDHHMMSS' to represent the timestamp format used in the row_key for sorting by time.

GCP

table_schema = {
    'row_key': 'user_id#timestamp',
    'column_families': ['activity'],
    'columns': {
        'activity': ['action', 'details']
    }
}

# Define timestamp format for sorting
# Your code here

Hint

Use a string variable named timestamp_format with the exact value 'YYYYMMDDHHMMSS'.

4

Complete the Bigtable schema design

Add a final key description to the table_schema dictionary with the value 'User activity tracking schema with row key as user_id and timestamp'.

GCP

table_schema = {
    'row_key': 'user_id#timestamp',
    'column_families': ['activity'],
    'columns': {
        'activity': ['action', 'details']
    },
    # Add description key here
}

timestamp_format = 'YYYYMMDDHHMMSS'
# Your code here

Hint

Add the description key with the exact string value to table_schema.

Practice

1. What is the main purpose of designing a row key carefully in Bigtable schema design?

easy

A. To balance load and enable fast queries

B. To store large binary files

C. To create multiple databases

D. To encrypt data automatically

Solution

1. Step 1: Understand the role of row keys in Bigtable

   Row keys uniquely identify rows and determine data distribution across nodes.

2. Step 2: Analyze the impact of row key design

   Good row key design balances load and speeds up queries by avoiding hotspots.

3. Final Answer:

   To balance load and enable fast queries -> Option A

4. Quick Check:

   Row key design = balance load + fast queries [OK]

Hint: Row keys control data distribution and query speed [OK]

Common Mistakes:

• Thinking row keys store data themselves
• Confusing row keys with column families
• Assuming row keys encrypt data

2. Which of the following is the correct way to group related columns in Bigtable?

easy

A. Using multiple row keys

B. Using separate tables

C. Using column families

D. Using indexes

Solution

1. Step 1: Recall Bigtable's data organization

   Bigtable organizes columns into column families to group related data.

2. Step 2: Identify the correct grouping method

   Column families group related columns for performance and management.

3. Final Answer:

   Using column families -> Option C

4. Quick Check:

   Related columns = column families [OK]

Hint: Group related columns with column families [OK]

Common Mistakes:

• Confusing row keys with column grouping
• Thinking indexes group columns
• Using separate tables unnecessarily

3. Given a Bigtable with row keys designed as userID#timestamp, what is the main benefit of this design?

medium

A. It enables efficient queries for a single user's recent activity

B. It groups all data by timestamp only

C. It allows fast retrieval of all users' data at once

D. It prevents any data duplication

Solution

1. Step 1: Analyze the row key format

   The row key combines userID and timestamp, so rows are sorted by user and time.

2. Step 2: Understand query benefits

   This design allows quick access to recent activity for a specific user by scanning a key range.

3. Final Answer:

   It enables efficient queries for a single user's recent activity -> Option A

4. Quick Check:

   Row key userID#timestamp = fast user recent queries [OK]

Hint: Row keys with userID first speed user-specific queries [OK]

Common Mistakes:

• Assuming it groups all users' data together
• Thinking it only sorts by timestamp
• Believing it prevents duplication

4. You notice that your Bigtable cluster has hotspots causing slow queries. Which schema design change can help fix this?

medium

A. Use a sequential numeric row key

B. Add a random prefix to the row key

C. Group all columns into one column family

D. Remove timestamps from row keys

Solution

1. Step 1: Identify cause of hotspots

   Sequential row keys cause data to cluster on few nodes, creating hotspots.

2. Step 2: Apply solution to distribute load

   Adding a random prefix spreads data across nodes, balancing load and reducing hotspots.

3. Final Answer:

   Add a random prefix to the row key -> Option B

4. Quick Check:

   Random prefix = balanced load, fewer hotspots [OK]

Hint: Randomize row keys to avoid hotspots [OK]

Common Mistakes:

• Using sequential keys which cause hotspots
• Grouping columns doesn't fix hotspots
• Removing timestamps reduces query flexibility

5. You want to design a Bigtable schema for IoT sensor data that arrives frequently from many devices. Which design choice best supports fast queries for recent data per device and balanced load?

hard

A. Row key as randomUUID with sensor data in multiple tables

B. Row key as timestamp#deviceID with all columns in one family

C. Row key as deviceID only, with timestamps as columns

D. Row key as deviceID#timestamp with column families for sensor types

Solution

1. Step 1: Consider query pattern

   Queries focus on recent data per device, so deviceID first in row key helps range scans.

2. Step 2: Consider load balancing and data grouping

   Using column families for sensor types groups related data efficiently; timestamp after deviceID orders data by time.

3. Final Answer:

   Row key as deviceID#timestamp with column families for sensor types -> Option D

4. Quick Check:

   DeviceID#timestamp + column families = fast, balanced queries [OK]

Hint: Use deviceID first in row key, group columns by type [OK]

Common Mistakes:

• Putting timestamp first slows device queries
• Using random UUID breaks data locality
• Storing timestamps as columns complicates queries