You are on page 1of 56

GCP Storage and Database Overview

S-GCPSP-B M3 Storage and Database Introduction

“”””

Vídeo subtitles

hello I'm Brian rice technical

curriculum lead for Google cloud you

have recently had the chance to learn

more about the compute side of Google

cloud platform so now let's explore GCPs

storage and database capabilities cloud

platforms like GCP offer many different

storage options from object storage to

database services these options help our

customers save costs reduce the time it

takes to launch and make the most of

their data sets by being able to analyze

a wide variety of data all applications


create and use data Google provides all

the tools that organizations need to

build and move their applications to the

cloud this includes storing videos

images and other objects even to

operational application data all

applications have a database behind them

and GCP provides manage services that

are scalable reliable and are easy to

operate for relational databases which

are commonly used today we offer a cloud

sequel for my sequel in Postgres

as well as cloud spanner we also have

non relational or no sequel databases

like cloud datastore cloud fire storm


and cloud BigTable Google has been a

leader in data storage for years from

published papers on topics such as

BigTable and spanner to our operational

excellence at storing massive amounts of

data for our ads and consumer services

for databases google has two customer

priorities the first priority is helping

customers migrate existing databases to

the cloud and moving them to the right

service this will usually be customers

moving my sequel or Postgres workloads

to cloud sequel the second priority is

helping customers innovate build or

rebuild for the cloud take advantage of

mobile and plan for future growth for


cloud storage we see three common use

cases among our customers the first is

content storage and delivery this is

when an organization

has content such as images or videos and

serves that content to users wherever

they are people want their content fast

so running on the amazing global network

that Google provides makes for a great

experience for end users the second use

case is storage for data analytics and

general compute organizations want to

process or expose their data to

analytics tools like the analytics stack

of products that Google Cloud offers and


do things like genomic sequencing or IOT

data analysis the third use case is

backup an archival storage customers can

save storage costs by migrating in

frequently accessed content to cheaper

cloud storage options also if anything

happens to their data on-premises it's

critical to have a copy in the cloud for

recovery purposes data has gravity it's

critical that our customers store their

data in GCP storage and databases from

there

customers can do amazing things and take

advantage of the analytics machine

learning and AI tools available on the

platform moving forward we'll continue


to innovate on existing and new services

such as making it easier to migrate data

to GCV and giving customers more

fine-grained control over their data and

as part of our innovation strategy we're

excited to have recently released

transfer appliance a rackable server

that customers use to capture and then

transfer large amounts of data to GCP as

low-tech as it sounds sometimes the best

way to move data is to ship it on

physical medium next why don't we look

into the storage and databases product

modules to learn more about the core

products that make up this category and


the value they provide thanks for

watching and enjoy the course

“”””

Introduction to
Data Transfers
Let's Get Started
In this module...
You will be able to define data transfers, including how they work and fit within
the GCP portfolio. You will also examine some common use cases and the
value propositions of Data Transfers.

You'll get answers to...


1. What are data transfers?
 How do data transfers work?
 How do data transfers fit within the GCP portfolio?
2. What are the business and technical value propositions for Data Transfers?

1. What is Google Data Transfers?


Introduction
Let's begin by defining Data Tranfers, how it works, and how it fits within GCP. 
Data Tranfers defined
Google offers a suite of solutions that enable customers to move data to GCP
fast, regardless of that data’s location or type, network size and utilization, or its
planned use.
Data Transfer Options
Depending on the customer needs, we have options to help customers move
data. 
Select each card for each option to understand the difference. 

Online transfer

Customers can use their network to move data to Cloud Storage.

Cloud Storage
Transfer Service
Customers can transfer their data from one cloud to another.

Transfer Appliance

Customers can select between 100-480 TB rackable appliances to


securely ship data to GCS.

BigQuery Data
Transfer Service
Schedule and automate data transfers from your SaaS applications to
BigQuery.
How Data Transfer works
There are several options customers can use to transfer their data to GCP. 
 Online transfers: Gsutil is the Command Line interface that many of our
customers use to get their data into Cloud Storage. We also offer easy
drag and drop of folders in Chrome. 
 Storage Transfer Service: This transfer option is cloud-to-cloud.
Common use cases are migrating off AWS S3 or often backing up S3
data. Also, this is a great way to transfer large amounts of data between
regions at Google. 
 Transfer Appliance: A rackable, high-capacity storage server that we ship
to the customer to fill up and ship it back. 100-TB and 480-TB versions
that with compression could transfer 200 Tbs or up to a petabyte. Best
used for lots of data, where a customer's network will not meet transfer
demands.  
 BigQuery Data Transfer Service: Automates loading data into BigQuery
from Google AdWords and DoubleClick.
 
There are many partners that provide options and often complement our
solutions. 

Common use cases


There are common use cases for moving data to GCP. 
Click on each use case to find out more. 

Data Center Migration

Decommission Tape Libraries and Infrastructure

Machine Learning

Content Storage and Delivery

Backup and Archiving


Where Data Transfer fits within GCP
When organizations begin their cloud journey, it often starts with a prioritized
workload and a prioritized data set. Google Cloud’s Data Transfer options can
kick-start engagements and act as an entry point to the cloud.

Knowledge check
Now that we have reviewed Data Transfers and the options available, ensure
you can identify which option is best for the customer need.
Drag the data type/requirements to the Data Transfer option. 

Schedule and automate data transfers from your SaaS applications to Google
BigQuery.Customers can use their network to move data to Google Cloud Storage.
Customers can select between 100-480 TB rackable appliances to securely ship their
data to GCS.
Customers can transfer their data from one cloud to another.

Online transfers

Cloud Storage Transfer Service

Transfer Appliance

BigQuery Transfer Service


SubmitShow Feedback

2. Why Google: Data Transfers Value


Proposition
Introduction
So far we have defined what Data Transfers is and the different options
available, how it works, and common use cases, and how it fits within GCP. Now
let's understand the value it brings to Google customers by defining the high-
level value proposition and challenges it addresses. 
High level value proposition
"Whether you are in Denver or Denmark; with 50 Gigabytes or 50 Petabytes;
access to a T1 line or 10 Gbps; Google offers solutions to meet your unique
data transfer requirements and get your data to the cloud quickly and securely."
Challenges addressed
It is important to understand the challenges a product solves so you can listen
for the key terms in customer conversations. 
Click on each challenge to learn more about the value Data Transfers provides. 

Online Transfers

Across Clouds

Offline Transfers

Data size and network bandwidth considerations


Below is a chart to help customers select the best transfer option to meet their
needs based on their data size and network bandwidth.

Knowledge check
Now that we have reviewed the value that data transfers bring to the Google
customer, ensure you can identify customer challenges with the value that Data
Transfers provide.
Match the customer challenge with the data transfers value.

Use Cloud Storage Transfer Service to back up data to a Cloud Storage bucket from
other cloud storage providers. By default, Cloud Storage Transfer Service ensures your
content is correctly transferred over. It copies a file from the data source if the file
doesn't exist in the data sink or if it differs between the version in the source and the
sink.

Capture up to a petabyte of data on one Transfer Appliance. Or use multiple appliances


to transfer more data. All without impacting your outbound network.
The gsutil command line, drag-and-drop functionality, and JSON API enable customers
to upload data via the method and language they prefer. The BigQuery Data Transfer
Service requires no deployment and can be configured via an easy-to-use user
interface.
SubmitShow Feedback

Recap
Top takeaways

Online transfers: Gsutil is the Command Line interface that many of our
customers use to get their data into GCS. We also offer easy drag and drop of
folders in Chrome.

Cloud Storage Transfer Service: This transfer option is cloud-to-cloud. Common


use cases are migrating off AWS S3 or often backing up S3 data. Also, this is a
great way to transfer large amounts of data between regions at Google.

Transfer Appliance: A rackable, high-capacity storage server that we ship to the


customer to fill up and ship it back. 100-TB and 480-TB versions that with
compression could transfer 200 Tbs or up to a petabyte. Best used for lots of
data, where a customer's network will not meet transfer demands.  

BigQuery Transfer Service: Automates loading data into BigQuery from Google
AdWords and DoubleClick.
Want more information?
Click the links below to find out more

Marketing page ↗

Google Transfer Appliance Documentation ↗

Congratulations!
Well done on completing this module. You can revisit this module at any time.
Click the button below to close this window and return to the course main
menu.
END MODULE
Introduction to
Google Cloud
Storage
Let's Get Started
In this module...
You will be able to define Cloud Storage, including how it works and fits within
the GCP portfolio. You will also examine some common use cases and
the value propositions of Cloud Storage.

You'll get answers to...


1. What is Cloud Storage?
 How does Cloud Storage work?
 How does Cloud Storage fit within the GCP portfolio?
2. What are the business and technical value propositions for Cloud Storage?

1. What is Google Cloud Storage?


Introduction
Let's begin by defining Cloud Storage, how it works, and how it fits within GCP. 

Cloud Storage defined


Cloud Storage stores and serves object (or BLOB) data. Customers can store an
unlimited number of objects, up to 5 terabytes in size each. 

It’s the same storage that Google uses for images in Google Photos, Gmail
attachments, Google Docs, and so on. 
How Cloud Storage works
Customers have a variety of storage requirements for a multitude of use cases.
The easiest way to classify offerings is by how often that data is accessed.
Cloud Storage is unique in a number of ways, it has a single API, millisecond
data access latency, and 99.999999999% durability across all storage classes.
Cloud Storage also offers object lifecycle management which, uses policies to
automatically move data to lower cost storage classes as it is accessed less
frequently throughout its life.
Take a look at the most common use cases for each type. 

Cloud Storage classes


Cloud Storage offers data storage classes of multi-regional, regional, nearline,
and coldline that align to the data storage needs of the customer.
Click on the plus sign to learn about the common characteristics and use cases for
each. 

Multi-Regional Storage


Regional Storage



Nearline Storage





Coldline Storage







Examples of Cloud Storage Working


There are several great examples of how Cloud Storage benefits our customers.

See how Snapchat uses Cloud Storage for all their photos and videos.

See how Spotify uses Cloud Storage for their data needs. See this video too.

See how Netflix uses Cloud Storage as part of a multi-cloud strategy.


Where Cloud Storage fits within GCP
Cloud Storage is just one of many storage options on GCP.  Cloud Storage fits
in the object storage segment and provides multiple storage classes. It is good
for binary or object data such as for images, media serving, and backups. 

Knowledge Check
Now that we have reviewed Cloud Storage and the classes available, let's
ensure that you can identify data requirements and the best class to use.
Drag the data type/requirements to the Cloud Storage class. 

Multi-regional

Regional

Nearline

Coldline

Data analytics and machine learning jobs that require local access for compute
resourcesStore data that is accessed less than once a year (archive data)Storing data
that is accessed less than once a monthStoring data that is frequently accessed
around the world

SubmitShow Feedback

2. Why Google: Cloud Storage Value


Proposition
Introduction
So far we have defined what Cloud Storage is, how it works, Cloud Storage
classes, examples of it working, and how it fits within GCP. Now let's
understand the value it brings to Google customers by defining the high-level
value proposition, as well as challenges it addresses. 
High level value


High level value
Cloud Storage is object storage at Google scale. It takes care of all the basic IT
operations for you. Google has decades of experience serving massive
amounts of data to billions of users. Cloud Storage has customers ingesting
and egressing petabytes of data daily, and sharing data across the globe on
Google’s private network.
Challenges addressed
It is important to understand the challenges a product solves so you can listen
for the key terms in customer conversations. 
Click on each challenge to learn more about the value Cloud Storage provides. 

 Users want content fast

Users want content fast


 Cost savings

Cost savings
 Mitigate risk

Mitigate risk
Knowledge check
Why Google?

Now that we have reviewed Cloud Storage and its value proposition, let's ensure
that you can identify why customers are choosing Google.
Click the two cards that give reasons why customers choose Google Cloud Storage.

Faster uploads

That's correct!

Transfers data to the public internet

No, we transfer data on our backbone network for as long as possible


before giving it to the customer

Direct peering

Your business network is connected directly to Google at any of our edge


locations available worldwide

Recap
Top takeaways

Cloud Storage stores and serves object (or BLOB) data. Customers can store an
unlimited number of objects, up to 5 terabytes in size each. 

Cloud Storage includes multiple storage classes to meet customers needs: 


 Multi-regional: Storing data that is frequently accessed around the world
 Regional: Data analytics and machine learning jobs that require local access for
compute resources
 Nearline: Storing data that is accessed less than once a month
 Coldline: Store data that is accessed less than once a year (archive data)
Want more information?
Marketing page
Documentation
Pricing
Customers
How-to Guides
Data lifecycle management capabilities
Congratulations!
Well done on completing this module. You can revisit this module at any time.
Click the button below to close this window and return to the course main
menu.
END MODULE

Cloud Storage  |  Google Cloud

Introduction to
Cloud SQL
Let's Get Started
In this module...
You will be able to define Cloud SQL, including how it works and fits within the
GCP portfolio. You will also examine some common use cases, as well as
the value propositions of Cloud SQL.
You'll get answers to...
1. What is Cloud SQL?
 How does Cloud SQL work?
 How does Cloud SQL fit within the GCP portfolio?
2. What are the business and technical value propositions for Cloud SQL?

Warm up
What is a database and how is it used?
A database is a collection of information that is organized so that it can easily
be accessed and managed. Customers are building software applications using
databases to answer business questions, such as buying a ticket, filing an
expense report, storing a photo, or storing medical records. Computer
applications run databases to get a fast answer to questions like:
 What’s this user’s name given their sign-in information so I can display it?
 What’s the cost of product Y so I can show it on my dynamic webpage?
 What were my top 10 best selling products this month?
 What is the next ad I should show the user currently browsing my site?

These apps must be able to write data in and read data out of databases
(read/write). When a database is used, it’s usually run by a computer
application. So when we say that “a database is useful for doing X,” it’s usually
because it’s designed to make answering a question simply, fast, and efficient
for the app.

What are the most common kinds of databases?

Relational database management systems (RDBMS, or just relational


databases), are used extensively and are the kind of database you encounter
most of the time. They’re organized based on the relational model of data. 

They are very good when:


 You have a well-structured data model.
 You need transactions and the ability to join data across tables to
retrieve complex combinations of your data.

They are sometimes called SQL databases because they make use of the SQL
programming language.
1. What is Cloud SQL?
Introduction
Let's begin by defining Cloud SQL, how it works, and how it fits within GCP. 

Define Cloud SQL and how it works


What is it?
Cloud SQL is a fully managed database service that makes it easy to set up,
maintain, manage, and administer relational MySQL and PostgreSQL databases
in the cloud. 

It is accessible from just about any application, anywhere, as long as it’s


compatible with MySQL or PostgreSQL.

How it works:
Cloud SQL automates some of the administrative tasks of operating a MySQL
or PostgreSQL database. To the app, it's just the same MySQL or PostgreSQL
database that’s used widely today. 

Connecting to your Cloud SQL database looks the same as connecting to a


MySQL or PostgreSQL database—you use standard connectors and standard
tools like MySQL workbench.
Examples of Cloud SQL working

Websites
Use case:
Almost any kind of website. Popular with blog and CMS software, such
as Wordpress

Customer example:
TheWaltDisneyCompany.com is backed by CloudSQL.

Operational applications
Use cases:
ERP, CRM, eCommerce

Customer example:
Costco UK runs Cloud SQL with SAP Hybris

SaaS platforms
Use case:
Custom applications targeting specific workflows or verticals

Customer example:
KiSSFLOW uses Cloud SQL in its service

Business intelligence
Use case:
Ad-hoc queries, report, and chart creation using tools, such as Tableau

Customer example:
WePay queries Cloud SQL to generate reports and detect fraud
Where Cloud SQL fits within GCP
Cloud SQL is just one of many database options on GCP. Cloud SQL is a
relational database along with Cloud Spanner. We will review that later in the
training. 

Knowledge Check
Use Cases: Now that we have reviewed Cloud SQL and how it works, ensure you
can identify examples of Cloud SQL working. 
Drag the example of Cloud SQL working with the use case. 

Websites

Operational Applications

SaaS platforms

Business intelligence
ERP, CRM, eCommerce
Ad-hoc queries, report, and chart creation using tools, such as TableauAlmost any kind
of website. Popular with blog and CMS software, such as WordpressCustom
applications targeting specific workflows or verticals

SubmitShow Feedback

2. Why Google: Cloud SQL Value


Proposition
Introduction
So far we have defined what Cloud SQL is and the different options available,
how it works, common use cases, and how it fits within GCP. Now let's
understand the value it brings to Google customers by defining the high-level
value proposition, as well as challenges it addresses. 
Challenges addressed
Click on each use case to learn more about the challenges Cloud SQL addresses.

Compatible

Fast

Fully managed

Flexible pricing

High-level value proposition


By handing off to Google the time-consuming tasks required to set up and run a
database—like applying patches and updates, managing backups and
configuring replications—you can save time and money and keep your focus on
building great applications. 

And because we use vanilla MySQL or PostgreSQL, it’s easy to connect from
any application anywhere.
Technical value proposition
Technical stakeholders care about the benefits of rapid provisioning, the ability
to easily increase performance to meet demand, and the ability to scale
instances based on demand. 

The technical challenges that are addressed with GCP are related to
provisioning and performance.
Below is an illustration of the tasks that Google takes care of for technical key players
so they can focus their efforts on improving their application.

Knowledge Check 
Now that we have reviewed the value that Cloud SQL brings to the Google
customer, ensure you can identify its technical value proposition.
Drag the items below to determine what Google Cloud SQL handles versus what the
user handles.

Google Cloud SQL

Customer

Database backups, patches, and installsOS patches and installationScaling and high
availabilityServer maintenance, rack & stack, and power, HVAC, netApp optimization

Recap
Top takeaways

Cloud SQL is a fully managed relational database service that makes it easy to
set up, maintain, manage, and administer relational MySQL and PostgreSQL
databases in the cloud.

It is accessible from just about any application, anywhere, as long as it’s


compatible with MySQL or PostgreSQL.

Connecting to Google Cloud SQL databases looks the same as connecting to a


MySQL or PostgreSQL database—customers use standard connectors and
standard tools like MySQL workbench.
Additional resources:
 Cloud SQL FAQ
 Feature overview
 Google App Engine and Cloud SQL (video)
 Quick Start Guide
 Getting Started Video
 Connecting to Cloud SQL (video)
 Using Cloud SQL with AppML (W3 Schools)
 Google Cloud Datastore vs. Google Cloud SQL
Congratulations!
Well done on completing this module. You can revisit this module at any time.
Click the button below to close this window and return to the course main
menu.
END MODULE

Introduction to
Google Cloud
Spanner
Let's Get Started
In this module...
You will be able to define Cloud Spanner, including how it works and fits within
the GCP portfolio. You will also examine some common use cases and the
value propositions of Cloud Spanner.

You'll get answers to...


1. What is Cloud Spanner?
 What's the difference between Cloud Spanner and other databases?
 How does Cloud Spanner fit within the GCP portfolio?
 What are common use cases for Cloud Spanner?
2. What are the business and technical value propositions for Cloud Spanner?

Warm Up 
Relational Database Management System
The main type of database you’ll encounter is the relational database
management system (RDBMS), or just relational databases. They’re organized
based on the relational model of data—this usually means data is organized in
tables that are connected by a common column. An example is shown below. 

Traditional relational databases are very good when customers have:


 A well-structured data model: for example, the data is in tables that all
have something in common (relations).
 Specialized Database Administrator staff to manage it.
Relational databases are sometimes called SQL databases because they make
use of the Structured Query Language for managing data. For an introduction
to databases, take a look at this presentation.
Relational model

1. What is Google Cloud Spanner?


Introduction
Let's begin by defining Cloud Spanner, how it works, use cases, customer
examples, and how it fits within GCP. We will also look at how it is different
from other databases. 
Define Cloud Spanner
Cloud Spanner is the only enterprise-grade, globally distributed, and strongly
consistent managed database service built for the cloud specifically to combine
the benefits of relational database structure with non-relational horizontal
scale. 

It provides relational semantics: Schemas, ACID transactions (atomic,


consistent, isolated, durable or across rows), SQL query and horizontal-scale
with a 99.999% SLA, fully managed operations, and is easily scalable.
Check out this video about Cloud Spanner.

https://youtu.be/amcf6W2Xv6M
“”””

Vídeo subtitles

- [Narrator] We demand

a lot of our databases,

and our databases demand a lot of us.

They're fragile, expensive,

and tough to maintain.

When things break, it can

be hard to put the pieces

back together at the

speed of your business,

and you often lose data in the process.

We've all come to expect

that distributed databases

can't be globally consistent and scalable.

But what if you didn't

have to make tradeoffs?

What if you could have a

fully managed database service


that's consistent, scales

horizontally across data centers,

and speaks SQL?

This is Cloud Spanner,

a mission critical

relational database service

built from the ground up

and battle tested at Google

for strong consistency

and high availability

at global scale.

At Google, we use Spanner for services

that billions of people access every day.

It's the only cloud service designed

to be a massively distributed

relational database

with transactions and SQL semantics.


And we're talking massive.

Spanner can scale up

to millions of machines

across hundreds of data centers

and trillions of database rows,

stretching across the globe

while behaving like it's all in one place,

where you want it.

We've built Cloud Spanner to

be fully managed and secure.

Automatic sharding and

synchronous replication

with low latency and schema

updates without downtime

means your data is highly

available and reliable.

Instead of endless provisioning


and worrying about maintenance,

you can focus on growing your business.

No matter your needs,

you don't have to hit a wall

with your database service.

Get started with Cloud

Spanner and build what's next.

“””””

How Cloud Spanner works


Cloud Spanner is a database service that’s fully managed for our customers.
They no longer need to add servers or storage, replace hardware, apply
software and security updates, or answer pagers when the system goes down
or gets hacked.

Cloud Spanner includes traditional relational database properties—


Schemas, ACID transactions, and SQL. 

Data is automatically and instantly copied across regions (called synchronous


replication). Queries always return consistent and ordered answers regardless
of the region. We use replication within and across regions to achieve
availability—if one region goes offline, the customer's data can still be served
from another region.

Cloud Spanner provides strong consistency and massive scalability, which


means for our customers, this is no longer a trade-off. Plus, it provides
enterprise-grade security.
Customer use case examples
Customers across industries can use Cloud Spanner to deliver value to their
customers:
Customer examples

"It was essential for us to have order sequence in our app logic, and with Cloud
Spanner, it’s built in. When we started looking at GCP,  we quickly identified
Cloud Spanner as the solution, as it provided relational semantics and incredible
scalability within a managed service. We hadn’t found a Cloud Spanner-like
product in other clouds. We ran a successful POC and plan to move several
massive services to Cloud Spanner. We look forward to Multi-Region
configurations, as they give us the ability to expand globally and reduce
latencies for customers on the other side of the world." 
– Manoj Goyal, Chief Product Officer, Marketo

"At our size, problems such as scalability and reliability don't have a simple
answer—Cloud Spanner is a transformational technology choice for us. It will
give us a regionally distributed database storage layer for our customers data
that can scale as we continue to grow. Our whole technology team is excited to
bring this into production in the coming months."
– Ben McCormack, Vice President of Operations, Evernote

"We want to move from our current on-prem per-customer deployment model to
the cloud to improve performance and reliability, which is extremely important
to us and our customers. With Cloud Spanner, we can process ten times more
transactions per second (using a current benchmark of 55k transactions per
second), allowing us to better serve customers, with a dramatically reduced
total cost of ownership."
– Danielle Royston, CEO, Redknee/Optiva

"Based on our experience and performance testing, Cloud Spanner is the most
compelling option we’ve seen to power a high-scale relational query workload. It
has the performance and scalability of a NoSQL database, but can execute SQL
so it’s a viable alternative to sharded MySQL. It’s an impressive technology and
could dramatically simplify how we manage our databases."
– Peter Bakkum, Platform Lead, Quizlet
Where Cloud Spanner fits 
In the storage and database areas, customers have several GCP
options/products that are aligned with their specific needs. Cloud Spanner is
aligned to the relational database requirements. 
Cloud Spanner is good for relational database management service
management at scale that requires high availability and HTAP. Ideal customers
need to manage user metadata, and are often in the Ad/Fin/MarTech
industries. 

Cloud SQL is good for web frameworks such as CMS or eCommerce. 

What's the difference between Cloud Spanner and


other databases?
Most databases today require making trade-offs between scale and
consistency. With Cloud Spanner, customers get the best of relational database
structure and non-relational database scale and performance with strong
external consistency across rows, regions, and continents.

What this means is that Cloud Spanner can scale to very large database sizes
while still giving IT and developers the familiarity they are used to with other
relational databases such as MySQL, PostgreSQL, or proprietary databases.

Cloud Spanner is not a drop-in replacement, but it does solve some very tricky
problems customers face as their needs grow. It also enables them to avoid re-
platforming for growth.

Cloud Spanner also dramatically reduces the operational overhead needed to


keep the database online and serving traffic. We see customers moving to
Cloud Spanner from sharded MySQL deployments and expensive proprietary
solutions.
Knowledge Check
Now that we have reviewed Cloud Spanner and common use cases, ensure you
can identify the difference between Cloud Spanner and other databases.

What value does Cloud Spanner provide?


Turn over the 2 correct cards.

Customers get the best of relational and non-relational


database structure
Yes, Cloud Spanner provides the best of relational and
non-relational database structure!

Requires trade-offs between scale and consistency

No, that is other databases; Cloud Spanner takes away the trade-offs!

Reduces operational overhead

Cloud Spanner reduces operational overload!

2. Why Google: Cloud Spanner Value


Proposition
Introduction
So far we have defined what Cloud Spanner is, how it works, use cases,
customer examples, and how it fits within GCP. We will also look at how it is
different from other databases. 

Now let's understand the value it brings to Google customers by defining the
high-level value proposition and the business and technical value proposition
for target prospects.
High-level value proposition

Cloud Spanner is the world’s first highly scalable, strongly consistent RDBMS for
mission-critical online transaction processing (OLTP) applications that is fully
managed for you.

Cloud Spanner meets customer requirements for global consistency, high availability,
and global scale—qualities that in combination make it unique as a database service.
In fact, every day Google uses Spanner to handle millions of queries per second for
billions of users for many Google services.

Challenges addressed
It is important to understand the business challenges a product solves so you
can listen for the key terms in customer conversations.

Transactional Consistency
Companies that have outgrown a single-instance RDBMS and moved to a
NoSQL solution but need transactional consistency, or are looking to move to a
scalable solution 

Scale
Companies currently sharding databases because they need more read or write
throughput than can be placed on a single node

Global Data
Companies and/or developers building applications that rely on global data and
require strong consistency for accuracy

Database Consolidation
Companies that store their business data in multiple database products with
variable maintenance overheads and capabilities and need to consolidate their
data
Value propositions
In Cloud Spanner opportunities, business and technical buyers have their own
primary concerns. 
Click on the accordion to learn the value Cloud Spanner provides for the business and
technical buyers.

Business value proposition



Technical value proposition

Knowledge Check
 Business and technical value propositions: Now that we have reviewed Cloud
Spanner and its value proposition, let's check your knowledge of the key values
for technical and business buyers.
Drag and drop the identified values to the appropriate buyer type.

Reliability and 99.999% uptime SLA


Atomic, consistent, isolated, durable (ACID) transactions
Standard SQL (ANSI 2011)
Enterprise-grade security and access control
Update your schema with no downtime
Database as a Service (DBaaS)

Business value proposition

Technical value proposition

SubmitShow Feedback

Recap
Top takeaways

Cloud Spanner is the only enterprise-grade, globally distributed, and strongly


consistent managed database service built for the cloud specifically to combine
the benefits of relational database structure with non-relational horizontal scale.

Cloud Spanner is good for relational database management service


management at scale that requires high availability and HTAP. Ideal customers
need to manage user metadata and are often in the Ad/Fin/MarTech industries. 
Cloud Spanner is the world’s first highly scalable, strongly consistent RDBMS for
mission-critical online transaction processing (OLTP) applications that is fully
managed for our customers.
Want more info?
 Marketing
 Documentation
 Pricing explained
Additional resources:
Google Cloud Platform blogs (list)
Customer facing one page
Live demo
Google Cloud Next ‘17 video and I/O ‘17 video
Webinars
Congratulations!
Well done on completing this module. You can revisit this module at any time.
Click the button below to close this window and return to the course main
menu.
END MODULE


Warm Up 


1. What is Google Cloud Bigtable?


2. Why Google: Cloud Bigtable Value Proposition


Recap


Introduction to
Google Cloud
Bigtable
Let's Get Started
In this module...
You will be able to define Google Cloud Bigtable, including examples of it
working and fits within the GCP portfolio. You will also examine the value
propositions of Google Cloud Bigtable.

You'll get answers to...


1. What is Cloud Bigtable?

 How does Cloud Bigtable work?


 How does Cloud Bigtable fit within the GCP portfolio?
2. What are the value business and technical propositions for Cloud Bigtable?

Warm Up 
Background
Previously we discussed relational databases. 
There are also non-relational databases such as NoSQL. NoSQL databases are
designed to scale horizontally, which means that if customers need more
processing or storage, they just add more machines.

Below is a comparison between relational databases (RDBMS) and NoSQL


databases. 

Relational databases (RDBMS)


 Uses a relational model to describe entities, with structured query language
(SQL) as the interface language
 Not designed to cope with the huge amounts of data and agility challenges that
modern applications face, except for Cloud Spanner

NoSQL databases
 Wide variety of different database technologies and use cases
 Developed in response to:
o Increased volume of data stored
o Increased variety of data stored 
o Increased velocity of data written and read

1. What is Google Cloud Bigtable?


Introduction
Let's begin by defining Cloud Bigtable, examples of it working, and how it fits
within GCP.

Cloud Bigtable defined


What is Bigtable
Cloud Bigtable is a high-performance NoSQL database service for large
analytical and operational workloads. It is designed for very large amounts of
data and is great for IoT, user analytics, financial data analysis, time-series data,
and graph data. 

Bigtable offers low latency and high throughput at any scale or application type.
You can use Bigtable as the storage engine for large-scale, low-latency
applications as well as throughput-intensive data processing and analytics.

Bigtable provisions and scales to hundreds of petabytes automatically, and can


smoothly handle millions of operations per second.

With Cloud BigTable, customers no longer have to make trade-offs between


speed, scale, cost, and compatibility in a database - they get them all.
Examples of Bigtable Working
Now that you understand what Bigtable is and how it works, let's take a look at
some examples of it working or use cases. 

Data-driven customer profiles

Personalization

Dashboards

Machine data/IoT

Fraud detection, risk analysis

Where Bigtable fits within GCP


On the storage and database areas, customers have several GCP
options/products that are aligned with their specific needs. Cloud Bigtable is
aligned the non-relational database requirements and is good for heavy read
and write, events, and analytical data. 
Conversely, Cloud Datastore is good for getting started, App Engine, and serve
use cases. 

Knowledge Check
Why use Bigtable?

Now that you have learned about Bigtable and what it does, let's apply your
knowledge.

What are the reasons why customers choose Bigtable


Turn over the 3 correct cards.  


It’s a high-volume, low latency database.

Bigtable is compatible with HBase and a replacement for Cassandra or


DynamoDB.

It offers low latency and high throughput at any scale or application type.

You can use Bigtable as the storage engine for large-scale, low-latency
applications as well as throughput-intensive data processing and
analytics.

It provisions and scales to hundreds of petabytes automatically, and can


smoothly handle millions of operations per second.

Right you are!

It’s good for data applications requiring multi-row transactions and


complex joins across tables.

Bigtable is good for data and databases with lots of read-write actions-
often analytical data. 

2. Why Google: Cloud Bigtable Value


Proposition
Introduction
So far we have defined what Cloud Bigtable is and examples of it working. Now
let's understand the value it brings to Google customers by defining the high-
level value proposition, as well as the business and technical value proposition
for target prospects.
High level value
Customer value

Cloud Bigtable offers enterprises a fast, fully managed, near infinitely scalable
NoSQL database service ideal for web, mobile, and IoT applications.

Unlike comparable market offerings, Bigtable is the only fully managed


database where users don’t need to sacrifice speed, scale, or cost when their
applications grow.

Bigtable has been battle-tested at Google for 12+ years as the database driving
many major applications including Google Analytics, Gmail, and YouTube. It’s
now available as a cloud service to bring unmatched scale and speed to our
customers business applications.

Bigtable is offered through a native RPC API and an HBase-compatible API, so


it’s fully integrated with the most widely adopted Big Data tools like Hadoop,
Spark, and the other Cloud Platform products.

Cloud Bigtable features an intuitive user interface that enables the provisioning
and monitoring of Bigtable clusters in real time, eliminating the need to manage
VMs.

With Bigtable, customers can store large amounts of data with consistent
throughput, regardless of growth rate—with higher availability and durability
than comparable market offerings.

Challenges addressed

Bigtable is designed to handle massive workloads at consistent low


latency and high throughput, so it's a great choice for both operational and
analytical applications, including IoT, user analytics, and financial data analysis.
Who is a Bigtable customer?

A large opportunity for Bigtable is one that:

 Has hundreds of TB or more of data that needs to be stored


 Runs 20 or more virtual machines of Cassandra, HBase, or MapR-DB
 Spends $100,000 or more yearly on DynamoDB
Business value proposition
In Cloud Bigtable opportunities, business buyers are interested in accelerating
time to market for their data-intensive applications, enabling seamless, elastic
scaling with zero downtime, reducing operational overhead and improving
business operations.
 Accelerates time-to-market for data-intensive applications
 Enables seamless, elastic scaling with zero downtime
 Reduces operational overhead and improves business operations
Accelerates time-to-market for data-intensive applications

Bigtable allows developers to quickly build applications using an industry-


standard API and with no need to focus on infrastructure.

Business challenges addressed


It is important to understand the business challenges a product solves so you
can listen for the key terms in customer conversations. 

Time to market for data-intensive applications

Scaling without
downtime

Operational
overhead

Business
operations
Technical value proposition
In Cloud Bigtable opportunities, technical buyers are interested in scaling
quickly and easily, future proofing, cost configurability, and if it is fully managed.
 Scaling is easy and fast
 Future-proofing
 Enables cost configurability
 Fully managed
Scaling is easy and fast
Growing data no longer requires a manual configuration, tuning, and
reallocation of resources, because Bigtable enables provisioning and scaling in
seconds via a simple UI. 

Technical challenges
It is important to understand the technical challenges a product solves so you
can listen for the key terms in customer conversations.

TCO

Performance

Scalability

Management

Proven

Security

Reliability

Ease of use
Knowledge Check Business versus technical value
propositions
Now that we have reviewed the value that Bigtable brings to the Google
customer, ensure you can identify its technical and business value proposition.
Drag the items below to determine the business and technical value propositions of
Google Bigtable.

Accelerates time-to-market for data-intensive applications


Makes applications ‘future proof'
Enables seamless, elastic scaling with zero downtime
Enables cost configurability

Business value proposition

Technical value proposition

SubmitShow Feedback

Recap
Top takeaways

Cloud Bigtable is a high-performance NoSQL database service for large


analytical and operational workloads. It is great for IoT, user analytics, financial
data analysis, time-series data, and graph data. It is designed for very large
amounts of data. It is great for IoT, user analytics, financial data analysis, time-
series data, and graph data. 

Cloud Bigtable is aligned the non-relational database requirements and is good


for heavy read and write, events, and analytical data.

Cloud Bigtable accelerates time-to-market for data-intensive applications and


enables seamless, elastic scaling with zero downtime.

Cloud Bigtables also makes applications "future proof" and enables cost
configurability.
Want more info?
Marketing site    

Documentation  

Wikipedia article

Additional resources:
 Case study: Financial services firm processes 25 billion stock market events
per hour with Google Cloud Bigtable
 Bigtable: A Distributed Structured Storage System (video)
 Other Blog posts
Congratulations!
Well done on completing this module. You can revisit this module at any time.
Click the button below to close this window and return to the course main
menu.
END MODULE
Introduction to
Cloud Datastore
Let's Get Started
In this module...
You will be able to define Cloud Datastore, including how it works and fits within
the GCP portfolio. You will also examine some common use cases and the
value propositions of Cloud Datastore.

You'll get answers to...


1. What is Cloud Datastore?
 How does Cloud Datastore work?
 How does Cloud Datastore fit within the GCP portfolio?
2.  What are the business and technical value propositions for Cloud Datastore?

1. What is Cloud Datastore?


Introduction
Let's begin by defining Cloud Datastore, how it works, and how it fits within
GCP. 

Define Cloud Datastore


Cloud Datastore is a scalable, fully managed serverless NoSQL document
database for mobile and web applications.

Cloud Datastore is:


 A fully managed NoSQL document database that scales from zero to global
scale without configuration or downtime
 Ideal for rapid and flexible web and mobile development
 A proven production system, serving customers for 10 years
How Cloud Datastore works
Cloud Datastore is a database service that’s fully managed for the customer. No
more determining the number of nodes needed, adding servers or storage,
replacing hardware, applying software and security updates, or answering
pagers when the system goes down or gets hacked. Customers can scale from
zero to millions of queries per second without any operator action needed.
Cloud Datastore is a schemaless document-oriented database, with ACID
transactions, which allows customers to worry less about making changes to
their underlying data structure as their application evolves.

Complex queries are enabled with secondary (called built-ins in Cloud


Datastore) and composite indexes. Cloud Datastore is encrypted at rest and in
transit as part of Google's enterprise-grade security.
Common use cases
Below are examples of customer use cases for Cloud Datastore. 
Click on each use case to learn more. 

User profiles

Product catalogs

Mobile games

Customer example
Check out the case study that details why New York Times moved to Cloud
Datastore for handling spikey workloads.

Where Cloud Datastore fits within GCP


In the storage and database areas, customers have several GCP
options/products that are aligned with their specific needs. Cloud Datastore is
good for customers with non-relational data that want a serverless database
and don't want to worry about nodes or cluster management.

Cloud Bigtable is good for heavy read and write, events, and analytical data.
Knowledge check
Why Cloud Datastore?

Now that you have learned about Cloud Datastore and what it does, let's apply
your knowledge.

Which of these statements are a reasons why customers choose Cloud


Datastore.
Click to turn over the 2 correct cards. 

Good for customers with non-relational data.

Way to go!

Good for customers with heavy read and write, events, and analytical
data.

No, you're thinking of Bigtable.

Good for customers who want to reduce their operations burden with an
enterprise-grade database.

Correct!

2. Why Google: Cloud Datastore Value


Proposition
Introduction
So far we have defined what Cloud Datastore is, how it works, common use
cases, and how it fits within GCP. Now let's understand the value it brings to
Google customers by defining the high-level value proposition, challenges it
addresses, and the business and technical value propositions. 
High-level value proposition
Cloud Datastore provides a fully managed document-oriented database that
scales from zero usage to extremely large. With Cloud Datastore, you can use
multi-document ACID transactions and complex queries, while still using a
highly available and durable database. Cloud Datastore enables developers to
move fast with it's schemaless configuration.
Challenges addressed

Costs

Resources

Business value propositions


In Cloud Datastore opportunities, business buyers are most concerned about
scalability, operations, and reliability. 
Click on each card to read the business value proposition. 

Scalability & Operations


Cloud Datastore enables you to hand off the
responsibility of running a highly scalable
document-oriented database to Google. From 10
users to 100's of millions of users, you will no
longer need to spend time optimizing, configuring
the database, updating it, or monitoring system
health.

Reliability
High availability and durability via replications is just there — you don't
need to think about it or manage it.
No scheduled downtime for upgrades, resizing, or configuration changes.
Technical value propositions
For technical key players, ensure they understand that Cloud Datastore
addresses their concerns with scalability, provisioning, and ACID. 
Click on each card to read to the technical value proposition.

Scalability & Provisioning


Cloud Datastore handles the scaling
transparently: you don't need to think about
servers, nodes, CPU, disk, or RAM.

ACID
Unlike many NoSQL databases, Cloud Datastore offers multi-document
ACID transactions and strongly consistent reads.
Knowledge Check 
Business versus Technical value proposition: Now that you understand the
value that Datastore brings to Google customers, let's apply your knowledge.
Drag the items below to determine the business and technical value propositions of
Google Datastore.

ReliabilityScalability and ProvisioningACIDScalability and Operations

Business value propositions

Technical value propositions

SubmitShow Feedback

Recap
Top takeaways

Cloud Datastore is a scalable, fully managed serverless NoSQL document


database for mobile and web applications.
Cloud Datastore is a schemaless document-oriented database, with ACID
transactions, which allows customers to worry less about making changes to
their underlying data structure as their application evolves.

Cloud Datastore is good for customers with non-relational data that want a
serverless database and don't want to worry about nodes or cluster
management.
Want more information?
Intro: Google Cloud Next '17 video
Indepth: Google Cloud Next '17 video
Pricing explained
Congratulations!
Well done on completing this module. You can revisit this module at any time.
Click the button below to close this window and return to the course main
menu.
END MODULE

Introduction to
Cloud Firestore
Let's Get Started
In this module...
You will be able to define Cloud Firestore, including how it works and fits within
the GCP portfolio. You will also examine some common use cases and the
value propositions of Cloud Firestore.

You'll get answers to...


1. What is Cloud Firestore?
 How does Cloud Firestore work?
 How does Cloud Firestore fit within the GCP portfolio?
2. What are the business and technical value propositions for Cloud Firestore?

1. What is Cloud Firestore?


Introduction
Let's begin by defining Cloud Firestore, how it works, and how it fits within GCP. 

Define Cloud Firestore


Cloud Firestore is a flexible, scalable NoSQL cloud database to store and sync
data for client- and server-side development.

Cloud Firestore is:


 A fully managed NoSQL document database that scales from zero to global
scale without configuration or downtime
 Ideal for rapid and flexible web and mobile development
 Designed for direct access from mobile devices

How Cloud Firestore works


Cloud Firestore is a database service that’s fully managed for customers. They
will no longer need to determine the number of nodes needed, add servers or
storage, replace hardware, apply software and security updates, or answer
pagers when the system goes down or gets hacked. Cloud Firestore scales
from zero to millions of queries per second without any operator action needed.

Cloud Firestore is a schemaless document-oriented database, with ACID


transactions. Data is automatically and instantly copied across regions (called
synchronous replication). As a result, queries always return consistent and
ordered answers regardless of the region. 

Cloud Firestore achieves availability and durability by using replication within


and across regions—if one region goes offline, customer data can still be served
from another region. Secondary (called single field indexes in Cloud Firestore)
and composite indexes enable complex queries. This is encrypted at rest and in
transit as part of our enterprise-grade security.
Common use cases
Below are examples of customer use cases for Cloud Firestore. 
Click on each use case to learn more. 


User profiles

Product catalogs

Serverless mobile apps

Where Cloud Firestore fits within GCP


Cloud Firestore is good for customers that are developing mobile and web
applications and want to reduce their operations burden with an enterprise-
grade database, while not being hassled with backend servers.
Knowledge Check
Why Cloud Firestore?

Now that you have learned about Cloud Firestore and what it does, let's apply
your knowledge.

Which of these statements are reasons why customers choose Cloud Firestore.
Turn over the 2 correct cards.  

Good for customers with heavy read and write, events, and analytical
data.

No, you're thinking of Bigtable.

Good for customers who are developing mobile and web applications.

Way to go!


Good for customers who want to reduce their operations burden with an
enterprise-grade database.

Correct!

2. Why Google: Cloud Firestore Value


Proposition
Introduction
So far we have defined what Cloud Firestore is, how it works, common use
cases, and how it fits within GCP. Now let's understand the value it brings to
Google customers by defining the high-level value proposition, challenges it
addresses, and the business and technical value propositions. 
High-level value proposition
Cloud Firestore provides a flexible, scalable NoSQL cloud database to store and
sync data for client- and server-side development. With Cloud Firestore, you can
use multi-document ACID transactions and complex queries, while still using a
highly available and durable database. Cloud Firestore enables developers to
move fast with it's schemaless structure.
Challenges addressed

Costs

Resources

Business value propositions


In Cloud Firestore opportunities, business buyers are most concerned about
scalability, operations, and reliability. 
Click on each card to read the business value proposition. 

Scalability & Operations


Cloud Firestore enables customers to hand off
the responsibility of running a highly scalable
document-oriented database to Google.
From 10 users to millions of users, customers will
no longer need to spend time optimizing,
configuring the database, updating it, or
monitoring system health

Reliability
High availability and durability via replications is just there — customers
don't need to think about it or manage it.
No scheduled downtime for upgrades, resizing or configuration changes.
Technical value propositions
For technical key players, ensure they understand that Cloud Firestore
addresses their concerns. 
Click on each card to read to the technical value proposition.

Scalability & Provisioning


Cloud Firestore handles the scaling transparently; customers don't need
to think about servers, nodes, CPU, disk, or RAM.

ACID
Unlike many NoSQL databases, Cloud Firestore offers multi-document
ACID transactions and strongly consistent reads.

Offline
Cloud Firestore provides Mobile and Web SDKs with integrated offline
mode capabilities so you can develop apps that work seamlessly as they
move in and out of network availability.


Real-time
Automatically receive updated results for queries via our real-time push
system — no more needing to poll check for changing results.
Knowledge Check 
Business versus Technical value proposition: Now that you understand the
value that Cloud Firestore brings to Google customers, apply your knowledge.
Drag the items below to determine the business and technical value propositions of
Google Firestore.

ReliabilityReal-timeOfflineScalability and operations

Business value propositions

Technical value propositions

SubmitShow Feedback

Recap
Top takeaways

Cloud Firestore is a flexible, scalable NoSQL cloud database to store and sync
data for client- and server-side development.

Cloud Firestore is a schemaless document-oriented database, with ACID


transactions. Data is automatically and instantly copied across regions (called
synchronous replication). As a result, queries always return consistent and
ordered answers regardless of the region. 

Cloud Firestore is good for customers that are developing mobile and web
applications and want to reduce their operations burden with an enterprise-
grade database, while not being hassled with backend servers.
Want more information?
Introducing Cloud Firestore
Google Developer Days (India '17): Introducing Cloud Firestore
Pricing explained
Congratulations!
Well done on completing this module. You can revisit this module at any time.
Click the button below to close this window and return to the course main
menu.
END MODULE

You might also like