This lab walks you through Cloud Spanner.
You will be creating a Spanner Instance and Database.
Region: us-central1
Duration: 60 minutes
Cloud Spanner is used to handle large amounts of data. It provides petabytes of capacity. Main use cases include financials and inventory applications.
Cloud Spanner can be considered a replacement for traditional SQL. For e.g. In a traditional database environment, when database query response times get close or even exceed the threshold limit due to an increase in the number of users or queries, you can bring response times down to acceptable levels through manual intervention.
Cloud Spanner can scale horizontally easily with minimal intervention. You can scale horizontally by just increasing the number of nodes (just change one digit).
Scaling horizontally means thousands of small machines will do the work together for you.
Scaling vertically means one big machine will do all the work for you.
Simply, Horizontal scaling implies scaling by adding more machines into your resource pool whereas Vertical scaling implies scaling by adding more power and strength to an existing machine.
For e.g multiple cloud-based POS solutions to retailers, restaurateurs, and eCommerce merchants around the globe.
Spanner is quite expensive than Cloud SQL.
For Cloud SQL you can select machine type, type of hard disk and size, region, and zone. You are restricted to have everything on one server.
Spanner is not for general SQL needs, Spanner is mainly used for massive-scale applications.
Lab Tasks:
Login into GCP Console.
Creating a Cloud Spanner Instance.
Creating a Spanner Database.
Create a Table.
Inserting data into Table using SQL Query.
Reading data through the Table using SQL Query.