Cloud Spanner for global distribution in GCP - Mini Project: Build & Apply

Cloud Spanner for global distribution

📖 Scenario: You are building a globally distributed application that requires a highly available and scalable database. Google Cloud Spanner is a perfect choice because it offers strong consistency and global distribution.In this project, you will create a Cloud Spanner instance, configure a database with a table, and set up multi-region replication to ensure your data is available worldwide.

🎯 Goal: Create a Cloud Spanner instance with a multi-region configuration, define a database schema with a table, and configure the instance for global distribution.

📋 What You'll Learn

Create a Cloud Spanner instance named global-instance with a multi-region configuration nam6 (North America multi-region).

Create a database named customer-db inside the instance.

Define a table named Customers with columns CustomerId (STRING(36), primary key), Name (STRING(100)), and Country (STRING(50)).

Configure the instance to use 3 nodes for capacity.

💡 Why This Matters

🌍 Real World

Global applications like e-commerce, financial services, and gaming require databases that are fast, consistent, and available worldwide. Cloud Spanner provides this capability with multi-region replication.

💼 Career

Cloud architects and database administrators use Cloud Spanner to design scalable, globally distributed databases that support mission-critical applications with strong consistency and high availability.

1

Create Cloud Spanner instance

Create a Cloud Spanner instance named global-instance with the configuration nam6 and 3 nodes.

GCP

# Your code here to create the Cloud Spanner instance named global-instance

Hint

Use the gcloud spanner instances create command with the correct instance name, configuration, and node count.

2

Create Cloud Spanner database

Create a database named customer-db inside the Cloud Spanner instance global-instance.

GCP

gcloud spanner instances create global-instance --config=nam6 --description="Global multi-region instance" --nodes=3
# Your code here to create the database customer-db inside global-instance

Hint

Use the gcloud spanner databases create command with the correct database name and instance.

3

Define Customers table schema

Define a table named Customers with columns CustomerId (STRING(36), primary key), Name (STRING(100)), and Country (STRING(50)) using a DDL statement. Use the gcloud spanner databases ddl update command to apply this schema to the customer-db database in the global-instance instance.

GCP

gcloud spanner instances create global-instance --config=nam6 --description="Global multi-region instance" --nodes=3
gcloud spanner databases create customer-db --instance=global-instance
# Your code here to define the Customers table schema using DDL

Hint

Use the gcloud spanner databases ddl update command with a DDL string to create the table.

4

Verify instance configuration for global distribution

Verify that the Cloud Spanner instance global-instance is configured with the multi-region configuration nam6 and has 3 nodes allocated.

GCP

gcloud spanner instances create global-instance --config=nam6 --description="Global multi-region instance" --nodes=3
gcloud spanner databases create customer-db --instance=global-instance
gcloud spanner databases ddl update customer-db --instance=global-instance --ddl="CREATE TABLE Customers (CustomerId STRING(36) NOT NULL, Name STRING(100), Country STRING(50)) PRIMARY KEY (CustomerId)"
# Your code here to verify the instance configuration

Hint

Use the gcloud spanner instances describe command to check the instance details.

Practice

1. What is the main benefit of using Cloud Spanner's global distribution feature?

easy

A. It keeps applications fast and reliable by storing data across multiple regions.

B. It reduces the cost of storage by using local disks only.

C. It automatically deletes old data to save space.

D. It limits access to data to a single region for security.

Solution

1. Step 1: Understand global distribution purpose

   Cloud Spanner stores data in multiple regions to improve speed and reliability.

2. Step 2: Compare options

   Only It keeps applications fast and reliable by storing data across multiple regions. correctly describes the benefit of global data storage for performance and reliability.

3. Final Answer:

   It keeps applications fast and reliable by storing data across multiple regions. -> Option A

4. Quick Check:

   Global data storage = fast and reliable apps [OK]

Hint: Global means data spread worldwide for speed and reliability [OK]

Common Mistakes:

• Thinking global distribution saves storage cost
• Believing data is deleted automatically
• Assuming data is limited to one region

2. Which of the following is the correct way to specify a multi-region configuration in Cloud Spanner?

easy

A. multi_region_config = "europe-west1"

B. multi_region_config = "us-central1"

C. multi_region_config = "asia-east1"

D. multi_region_config = "nam3"

Solution

1. Step 1: Identify multi-region config names

   Cloud Spanner uses specific multi-region config names like "nam3" for North America multi-region.

2. Step 2: Check options

   Only A is a valid multi-region config. Options B, C, and D are single-region names.

3. Final Answer:

   multi_region_config = "nam3" -> Option D

4. Quick Check:

   Multi-region config uses names like nam3 [OK]

Hint: Multi-region configs have short codes like nam3, not single region names [OK]

Common Mistakes:

• Using single region names instead of multi-region codes
• Confusing region names with zone names
• Misspelling multi-region config strings

3. Given this Cloud Spanner instance configuration:
instance_config = "nam3"
nodes = 3
What is the expected behavior of this setup?

medium

A. Data is globally distributed across North America with 3 nodes handling requests.

B. Data is stored in a single region with 3 nodes for processing.

C. Data is stored only in Europe with 3 nodes.

D. Data is stored in Asia with 3 nodes but no replication.

Solution

1. Step 1: Interpret instance_config "nam3"

   "nam3" is a multi-region config for North America, so data is distributed across multiple regions there.

2. Step 2: Understand nodes setting

   3 nodes means the instance has 3 processing units to handle workload.

3. Final Answer:

   Data is globally distributed across North America with 3 nodes handling requests. -> Option A

4. Quick Check:

   nam3 = North America multi-region + 3 nodes [OK]

Hint: Multi-region config + nodes = distributed data with processing power [OK]

Common Mistakes:

• Assuming single region storage with multi-region config
• Ignoring the meaning of nodes
• Confusing region names with multi-region configs

4. You configured a Cloud Spanner instance with instance_config = "nam3" but your app experiences high latency in Europe. What is the likely cause?

medium

A. The instance_config "nam3" is invalid and causes errors.

B. You need to increase the number of nodes to reduce latency.

C. The multi-region config "nam3" only covers North America, not Europe.

D. Cloud Spanner does not support multi-region configurations.

Solution

1. Step 1: Understand "nam3" coverage

   "nam3" is a multi-region config limited to North America regions only.

2. Step 2: Analyze latency cause

   High latency in Europe happens because data is not stored close to European users.

3. Final Answer:

   The multi-region config "nam3" only covers North America, not Europe. -> Option C

4. Quick Check:

   nam3 excludes Europe, causing latency there [OK]

Hint: Check if multi-region config covers your app's user locations [OK]

Common Mistakes:

• Assuming multi-region covers all continents
• Thinking node count fixes geographic latency
• Believing "nam3" is invalid

5. You want to deploy a Cloud Spanner instance that serves users in Asia, Europe, and North America with low latency. Which configuration should you choose?

hard

A. Use a single-region config in Asia with 5 nodes.

B. Use the multi-region config "nam-eur-asia1" with enough nodes.

C. Use multiple single-region instances in each continent.

D. Use the multi-region config "nam3" with 3 nodes.

Solution

1. Step 1: Identify multi-region config covering Asia, Europe, North America

   "nam-eur-asia1" is a multi-region config spanning these continents.

2. Step 2: Understand node allocation

   Choosing enough nodes ensures capacity and low latency across regions.

3. Step 3: Compare other options

   Single-region configs or multiple instances increase complexity or limit coverage.

4. Final Answer:

   Use the multi-region config "nam-eur-asia1" with enough nodes. -> Option B

5. Quick Check:

   nam-eur-asia1 covers all needed continents [OK]

Hint: Pick multi-region config covering all user continents [OK]

Common Mistakes:

• Choosing single-region config for global users
• Using nam3 which excludes Europe and Asia
• Deploying multiple instances instead of one multi-region