Introduction to

Google Compute
Engine
Let's Get Started
In this module...
You will be able to define Compute Engine and discuss how it works and how it
fits within the GCP portfolio, including use cases. In addition, you will learn
about the value propositions of Google Compute Engine.
You'll get answers to...
1. What is Compute Engine?

 How does Compute Engine work?

 How does Compute Engine fit within the GCP portfolio?
2. What are the value propositions for Compute Engine?

Warm Up 
Cloud computing is changing the world...
Cloud computing has enabled a revolution in app startups (think Uber and
Snapchat) by drastically speeding up innovation. Previously, to launch a global
service with billions of users, you’d have to make large upfront payments and
have contracts with many different vendors to host servers. You’d also have to
hire a large staff to manage the systems 24/7.

Today, with just a credit card, you can sign up with Google Cloud Platform and
rent all the infrastructure you need with no up-front investment, drastically
reducing time to market.
Fast facts...

More than 70% of IT budgets are spent on planning, building, and maintaining

infrastructure.

Less than 30% is spent on innovating to gain a competitive advantage.

Using Infrastructure as a Service (IaaS) is changing this, and making

companies more competitive by decreasing costs, building products that
differentiate the company, and improving product quality and time to market.

1. What is Google Compute Engine?

Introduction
Let's begin by defining Compute Engine, how it works, and how it fits within
GCP. Google Compute Engine delivers virtual machines running in Google's
innovative data centers and worldwide fiber network.

Compute Engine defined

Google Compute Engine is a type of infrastructure as a service (IaaS). Compute
Engine delivers scalable, high-performance virtual machines running in
Google's innovative data centers and worldwide fiber network. Compute Engine
provides practically unlimited computing power using virtual machines (VMs) in
the cloud.

Customers can run any computing workload on Compute Engine such as, web-
server hosting, application hosting, and/or application backends.

Examples include mobile gaming servers, automated bidding for online

advertising space, and batch-data processing, such as Hadoop and logs
processing. Other examples are media rendering, transcoding, financial-market
simulation, and genomics, such as DNA sequencing.
How Compute Engine works
Understand the fundamentals of Compute Engine in less than five minutes! This
video will explain the key services and how they work together to run your
applications on Google's infrastructure.  Automation and APIs are next,
wrapping up with pointers to further details.
Note: Our billing model has changed since production of this video. Google
Compute Engine now bills for a minimum of 1 minute of usage, so if you run an
instance for 30 seconds of uptime, you are billed for 1 minute. After 1 minute,
your instance is billed on a per-second basis.

“”Video Subtitles :
https://www.youtube.com/watch?v=43gvHZyPRVk

Hi.

Please join me for a quick

tour of Google Compute Engine.

Our vision is to help

you run your applications

on the same

infrastructure we use

for hosting Google's

applications.

And Compute Engine

is three things.
It's virtual machines.

It's networking.

And it's disks.

So you start with a project.

And it's an administrative

grouping of Google's APIs.

And we have a lot

of APIs, including

other services for

compute and storage.

But right now, we're going

to focus on Compute Engine.

And here, we can

think of the project

as your virtual private cluster

to use for whatever you need.

Inside the project, we

have virtual machines,

we have networks,

and we have disks.

So the network-- and the

network is Google's network.

It's the same network we use

to serve all of our products,

and we work very hard to get

traffic from the internet

onto our dedicated

infrastructure

and get it to your

virtual machines
as quickly as possible.

And your part of this network

is private to your project.

All of your virtual machines

can see each other on the same

network, but nobody else

can see your project,

and you can't see anyone else's.

We work hard to

make it easy to use,

including a DNS server

that maps the names

of your virtual machines to

their internal IP addresses,

making it easy to configure

and connect to other machines.

The Compute Engine Load Balancer

is Google's network level

distributed load balancer,

bringing packets directly

to your virtual machines.

So you've got a pool

of virtual machines,

and Google's infrastructure

balances the load

to all of those machines.

We published a

blog post recently

with details of scaling the Load

Balancer to one million queries

per second, without any

advance warning or pre-warming.

And it only hits virtual

machines that are healthy.

And you get to define

for your application

exactly what healthy means.

So we've got networks.

We've got load balance

traffic on those networks.

And next up, we have

virtual machines.

And virtual machines

are literally
the core of Compute Engine.

When creating a

virtual machine, you

choose what balance of CPU to

RAM is right for your needs.

And these virtual

machines are all

running on Google's

infrastructure in the same data

centers we use for our products.

We work very hard to keep the

underlying machines up to date.

They get software updates.

Hardware gets replaced when it

needs to-- that sort of thing.

These virtual

machines are billed

by the minute with

a 10-minute minimum.

So you can use them in a

wide variety of situations

that just wouldn't be possible

if the billing intervals were

longer.

All of these instances boot

off of Persistent Disk,

which is a logical block

storage device that's

spread out in the data centers.

And it's been designed for high

performance and very consistent

I/O latency.

If you already have a

database you're happy with,

this is a great place to host it

and any other latency-sensitive

workloads you have.

Your virtual machines

get that high performance

and consistent I/O latency

because the infrastructure

is distributing the underlying

blocks across hundreds

or thousands of machines,

optimizing the reads

and writes to give

excellent performance.

And did I mention the

consistent I/O latency?

We strive to make it work at

the same speed all the time.

Workloads should perform

the same from day to day,

from machine to machine.

And I don't know about

you, but I really

like sleeping through the night.

So the key to that

is automation.

We've all got this virtual

machines and hardware,

so let's take advantage

of that fact--

the fact that it's virtual-- by

automating everything we can.

So we've got tools

to help, and we've

partnered with several

excellent groups

to offer services for

scaling and managing

your infrastructure.

We've also created plug-ins for

a wide variety of open source

management tools.

All of this access, all the

access to Compute Engine,

is via our HTTP and JSON API.

Everything I just mentioned.

Also our command line tools

and our developer console,

built on the same API.

This means your code

has the same access

to all the features of

Google Compute Engine.

And now you know the

fundamentals of Compute Engine.

We have a lot more details

in the documentation.

Thanks for watching.

And we're really looking forward

to seeing what you build.

Happy computing

“””””

Customer example
Take a few minutes and read about how Shazam, one of the most popular
mobile apps in the world, saves time and resources through the use of scaling
with Compute Engine. 

Where Compute Engine fits within GCP

On the compute continuum, customers have four GCP options/products that
are aligned with where the code needs to run. Compute Engine is the
infrastructure-centric solution. 

Note that all solutions are supported by Google networking. 

Click the cards to find out more. Each solution will be covered in detail in this training.

Compute Engine
IaaS

Virtual machines with industry-leading price/performance

Ideal for customers that:
Need complete control over the virtual-machine infrastructure

Need to make changes to the kernel, such as providing their own network or
graphics drivers to squeeze out the last drop of performance

Need to run a software package that can’t easily be containerized or have

existing VM images to move to the cloud

Kubernetes Engine 
Hybrid

Cluster manager and orchestration engine built on Google’s container

experience
Ideal for customers that:
Have been challenged when deploying or maintaining a fleet of VMs and it
has been determined that containers are the solution

Have containerized the workloads and need a system on which to run and
manage them

Never want to touch a server or infrastructure

Don’t have dependencies on kernel changes or on a specific (non-Linux)

operating system

App Engine 
PaaS

A flexible, zero ops platform for building highly available apps

Ideal for customers that:

Want to focus on writing code and never touch a server, cluster, or
infrastructure

Build quickly and highly value time to market

 Do not want to worry about a pager going off or 5xx errors

Need apps to have high availability without a complex architecture

Cloud Functions 
Serverless Logic

A lightweight fully managed serverless execution environment for

building and connecting cloud services
Ideal for customers that:
Need to connect and extend cloud services

Want to automate with event-driven functions that respond to cloud events

Want to use open and familiar JavaScript

Never manage a server or runtime environment

Knowledge Check
Compute Engine basics:

Now that you have learned about Compute Engine and what it does, which of
the following statements about Compute Engine are true?
Turn over the 2 correct cards.

Compute Engine is a type of infrastructure as a service (IaaS).

Right you are!

Cloud Engine is a computing platform provided as a service, called a

“platform  as a service” (PaaS).
 Actually, that’s Google App Engine.

Compute Engine provides practically unlimited computing power using

virtual machines (VMs) in the cloud.

You got it!

Knowledge check
How Compute Engine works/fits for customers:

Apply your knowledge — think about the types of customers Compute Engine is
ideal for.

Which of these customer needs are solved by Compute Engine and which ones
are not?
Drag and drop the corresponding customer need into either the 'Compute Engine' OR
'Not Compute Engine' boxes. 

Need complete control over the virtual-machine infrastructure

Need to connect and extend cloud services

Need to run a software package that can’t easily be containerized or have existing VM
images to move to the cloud

Never want to touch a server or infrastructure

Compute Engine :

Need complete control over the virtual-machine infrastructure

Need to run a software package that can’t easily be containerized or have existing VM
images to move to the cloud

Not Compute Engine :

Never want to touch a server or infrastructure

Need to connect and extend cloud services

SubmitShow Feedback
 2. Why Google: Compute Engine
Value Proposition
Introduction
So far you have learned what Compute Engine is and how it works, and looked
at customer examples. Now you can look at the value Compute Engine brings to
customers by reading the high-level value proposition, as well as the business
and technical value proposition for target prospects. 
High-level value proposition
Read the value proposition to share with prospects.

Compute Engine makes it easy to create and configure high-performance VMs

that will quickly and easily scale to any size workload while using Google’s
worldwide, high-speed network. Customers can choose zones and regions that
are closest to customers to reduce latency. They can also replicate apps in data
centers across the globe to ensure high availability. 

Customers pay only for what they use and earn automatic discounts as they
use more. The result—up to 50% more computing power for the money over
other vendors, without contracts or lock-in. Customers can also integrate with
the other products in the GCP suite, especially big-data products like BigQuery.
Challenges addressed
It is important to understand the business challenges a product solves so you
can listen for the key terms in customer conversations.

Reduce costs
The pricing model can give customers 50% or more computing power for their
money via sustained-use discounts and custom VMs.
Compute Engine's batch features, particularly Preemptible VMs, provide another
big cost-saving opportunity.
 Competitive differentiation
Google’s global private network is superior in performance to other clouds that
route traffic over the internet.
Compute Engine benefits from integration with Google’s other world-
class, NoOps cloud services.

Improve quality and time to market

Google data centers give customers scale and security that are world-class and
would be very expensive to achieve on-premises.
Business value propositions
In Compute Engine opportunities, business buyers are most concerned about
ensuring they have industry-leading performance at a low cost.
Click on each use case below to learn the value Compute Engine provides.

Industry-leading performance

Low cost

Technical value propositions

For technical key players, ensure they understand that Compute Engine
addresses the following technical use cases.
Click on each use case below to learn the value Compute Engine provides.

Fast and efficient networking

Flexibility for every workload

Knowledge Check
Check your knowledge of the key values for technical and business buyers. 

Do these values apply to Business or Technical?

Drag and drop the identified values to the appropriate buyer type.

Low costFast and efficient networkingFlexibility for every workload

Business

Technical

SubmitShow Feedback

Recap

Top takeaways
Compute Engine provides practically unlimited computing power using virtual
machines (VMs) in the cloud. It offers the same computing power that Google
uses for its infrastructure with virtual machines in the cloud.

Compute Engine helps clients improve quality and accelerate time to market
with Google-grade data centers that give them world-class scale and security
and would be expensive to achieve on-premises.

Compute Engine makes it easy to create and configure high-performance VMs

that quickly and easily scale to any size workload.

Compute Engine is ideal for customers that need complete control over the
virtual-machine infrastructure.
Want more information? 
Marketing

Documentation

Partner Resources

Virtual Network: Marketing

Virtual Network: Documentation

Additional resources:
  Pricing example: Part 1 and Part 2
 Information on Compute Engine pricing
 Virtual Private Cloud marketing
 Virtual Private Cloud documentation
 Google Compute Engine ranked #1 in price-performance by Cloud Spectator
 Quick Start Guides
 Choosing the right compute option in GCP

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 App
Engine
Let's Get Started
In this module...
You will be able to define App Engine and discuss how it works and fits within
the GCP portfolio, including use cases. In addition, you will learn about the value
propositions of App Engine.
You'll get answers to...
1. What is App Engine?

 How does App Engine work?

 How does App Engine fit within the GCP portfolio?
2. What are the value propositions for App Engine?

Warm Up 
Market trends...
Organizations are looking to become zero ops; that is, they will have almost no
staff dedicated to the operations of IT infrastructure, and this idea is spreading
throughout the IT industry. 

No one knows the exact size of the platform as a service (PaaS) market, but it’s
growing in the billions of dollars. PaaS application-development services are
also growing to be a >$1 billion business.

Google has a sizable chunk of the public cloud market currently, and is well
positioned to lead the field because of our developer friendliness, global
computing capabilities, and expertise. 

1. What is Google App Engine?

Introduction
Let's begin with an example of common challenges, then define App Engine,
how it works, and how it fits within GCP.
Let's begin with the challenges...
Click the arrows to learn about Tom...


Meet Tom... 
Tom is the CTO of XYZ, Inc. and he needs to update and scale their new
web/mobile app fast! Demand is skyrocketing. The DevOps team is swamped
and there is no way they can add another critical project to the list. They are
managing fleets of servers to serve end-user requests and can’t afford to have
their systems fall over. They need high levels of scale while having some control
of the code they need to run.
App Engine defined
App Engine is a computing platform provided as a service, called a “platform as
a service” (PaaS).
Ultimately, App Engine saves organizations time and cost in software
application development by eliminating the need to buy, build, and
operate computing hardware and other infrastructure.

Organizations of varying sizes can focus their engineering teams on creating

high-value applications, instead of no-value operations work.

Let's look at an analogy

While we can think of IaaS as providing the pieces that make up a car, App
Engine is the fully built car that just runs. It has a default set of tires, seats, and
paint color—these are the language runtimes, performance settings, and where
the app is homed. And you can customize all these.

The engine here is App Engine’s cluster management, and it's the only aspect
that is not configurable: it’s the lower-level service that guarantees high
availability, and thus cannot be changed. So, in the same sense that you want to
get in the car and just drive, App Engine allows customers to jump right in and
“just code.”

How App Engine works

For customers building their next great application, who need a cloud platform
that is easy to use, won't become an ongoing maintenance headache, and of
course, will scale just in case the app becomes a smashing success: Enter
Google App Engine. This video will walk you through how App Engine can be
used at each level of application needs, and most importantly, keep servers and
client batteries from melting.
Customer example
Read about how Backflip Studios uses App Engine to handle unpredictable load
and focus on development. 

Where App Engine fits within GCP

On the compute continuum, customers have four GCP options/products that
are aligned with where the code needs to run. 

App Engine is a platform-centric solution.

Click on the cards to read the definition for each product and the types of customers
it is ideal for.
 

Compute Engine
IaaS

Virtual machines with industry-leading price/performance

Ideal for customers that:

Need complete control over the virtual-machine infrastructure

Need to make changes to the kernel, such as providing their own network or
graphics drivers to squeeze out the last drop of performance

Need to run a software package that can’t easily be containerized or have

existing VM images to move to the cloud

Kubernetes Engine 
Hybrid

Cluster manager and orchestration engine built on Google’s container

experience
Ideal for customers that:

Have been challenged when deploying or maintaining a fleet of VMs and it

has been determined that containers are the solution

Have containerized the workloads and need a system on which to run and
manage them

Never want to touch a server or infrastructure

Don’t have dependencies on kernel changes or on a specific (non-Linux)

operating system

App Engine 
 PaaS

A flexible, zero ops platform for building highly available apps

Ideal for customers that:

Want to focus on writing code and never touch a server, cluster, or

infrastructure

Build quickly and highly value time to market

Do not want to worry about a pager going off or 5xx errors

Need an app to have high availability without a complex architecture

Cloud Functions 
Serverless Logic

A lightweight fully managed serverless execution environment for

building and connecting cloud services
Ideal for customers that:

Need to connect and extend cloud services

Want to automate with event-driven functions that respond to cloud events

Use open and familiar JavaScript

Never manage a server or runtime environment

How Compute products fit
Now that you understand a few of compute products, watch a quick overview of
the high-level architecture of App Engine and Compute Engine and the
beginnings of the continuum of computing. This video will dive into the
architecture of Google scale and touch on the possibilities of using App Engine
and Compute Engine together.
0:00 / 0:00

What is included
With App Engine, customers get services and application programming
interfaces (APIs) that address key needs of developers including:
 Multiple options to store application data including:
o Caching - App Engine Memcache
 o Cloud Storage - store any objects up to 5 TB in size
o Cloud Datastore - persistent, low-latency memory for serving data to
applications
o Cloud SQL - relational database that can be run on persistent disk >1
terabyte in size
o Cloud Bigtable - NoSQL database for heavy read/writes and analysis
 Task queues
 User authentication
 Automatic scaling to meet any demand
 Load balancing
 Versioning for your app
 Logging
 Monitoring
 Robust security tools like Cloud Security Scanner
 Global network
 Support packages
...all with high availability and guaranteed redundancy.
Knowledge Check 
What does it mean when organizations are looking to become zero-ops?
Turn over 1 card see if you can find the right answer.

Organizations that want to become zero-ops want to have almost no

staff dedicated to the operations of IT infrastructure.

That's right! 
You’re the zero-ops hero!

When a customer is looking to become zero-ops, they’re looking for an

on-premises solution to build their app on.

Nope! This doesn't mean they are zero-ops.

First, hire a staff dedicated to maintaining and operating the IT systems.

 This is not the answer you’re looking for...

2. Why Google: App Engine Value

Proposition
Introduction
So far we have defined what App Engine is, discussed how it works, and looked
at a customer example. 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 proposition
Let's begin with the high-level value proposition. 

App Engine is built on Google’s years of experience running some of the highest
performance, global web-based apps and backend systems. Google runs 7
cloud products with more than a billion users. App Engine gives this capability
to everyone. Google is starting to lead the competition with:
 Differentiators that developers notice
 Low cost
 Breadth of products and breadth of network
 Ease of use and performance
 Practically infinite scalability

The Google Cloud Platform suite of products enhances the value of App Engine
by vastly extending its capabilities.
Challenges addressed
Building an app with App Engine relieves customers from an incredible amount
of difficult, no-value work they would have to do to:

 Build their own infrastructure

 Grow it as their computing needs increase
 Make sure it’s available night and day

This can be up to 70% of the work required to get your app up and running.
Instead, Google provides customers with a world-class information technology
platform-reliability service. 
Business value proposition
For business key players, ensure they understand that App Engine addresses
the following high-level key points.
Click the headings below to find out more

General business





Developer productivity






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

The key terms to listen for are the cost of development, downtime, and time to

market. Homing in on these triggers will help you further the sales conversation.

Technical value proposition

For a technical stakeholder, they care about the benefits of using App Engine,
including its ability to:
 Provide the code and configuration tools for your app production pipeline
 Provide superb consistency and availability at all points in the development and
production process
 Provision all the necessary underlying infrastructure
  Automatically increase capacity within the limits you set. If you need more,
increase your limit. No more time-consuming capacity planning
 Eliminate patches for zero-day exploits; Google takes care of it
Technical challenges
It is important to understand the technical challenges a product solves so you
can listen for the key terms in customer conversations.

The key terms to listen for are accelerating development time and reducing

time spent managing and maintaining infrastructure, capacity planning, and
patching.

Knowledge Check
Which of these developers is expressing a productivity benefit App Engine
provides?
Select all the cards that apply.

Developer 1: 
“Thanks to App Engine, it’s easier to manage code in development and
move it to production.”

That’s right! You’re going places.

Developer 2: 
“Using App Engine, I have complete control over the virtual-machine
infrastructure.”

You’re thinking of Compute Engine’s benefits.

Developer 3: 
 “With App Engine, I can easily build apps that draw on the power of the
entire Google Cloud Platform product suite.”

Correct! You must be some sort of Google guru.

Recap
Top takeaways

App Engine helps customers because they don't have to build their own
infrastructure.

App Engine saves organizations time and costs in software application

development by eliminating the need to buy, build, and operate computing
hardware and other infrastructure.

If businesses need to accelerate time to market, App Engine helps accomplish

that.

App Engine provides services that help customers meet key developer needs
with user authentication, versioning, and robust security tools like Cloud
Security Scanner.
Want more information? 
Marketing

Documentation

Additional resources:
Introduction to App Engine on Youtube
Choosing a Compute Option
Building a mobile app on Google Cloud Platform
When to use App Engine flexible environment

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 App
Engine
Let's Get Started
In this module...
You will be able to define App Engine and discuss how it works and fits within
the GCP portfolio, including use cases. In addition, you will learn about the value
propositions of App Engine.
You'll get answers to...
1. What is App Engine?

 How does App Engine work?

 How does App Engine fit within the GCP portfolio?
2. What are the value propositions for App Engine?

Warm Up 
Market trends...
Organizations are looking to become zero ops; that is, they will have almost no
staff dedicated to the operations of IT infrastructure, and this idea is spreading
throughout the IT industry. 

No one knows the exact size of the platform as a service (PaaS) market, but it’s
growing in the billions of dollars. PaaS application-development services are
also growing to be a >$1 billion business.

Google has a sizable chunk of the public cloud market currently, and is well
positioned to lead the field because of our developer friendliness, global
computing capabilities, and expertise. 
 1. What is Google App Engine?
Introduction
Let's begin with an example of common challenges, then define App Engine,
how it works, and how it fits within GCP.
Let's begin with the challenges...
Click the arrows to learn about Tom...


New way....
He needs a new way…. He cannot have his teams wasting time on these no-
value activities. They need to start developing and fast to meet the timeline and
customer demand…. 

Read on to find out what we could do to help Tom.

App Engine defined
App Engine is a computing platform provided as a service, called a “platform as
a service” (PaaS).

Ultimately, App Engine saves organizations time and cost in software

application development by eliminating the need to buy, build, and
operate computing hardware and other infrastructure.

Organizations of varying sizes can focus their engineering teams on creating

high-value applications, instead of no-value operations work.

Let's look at an analogy

While we can think of IaaS as providing the pieces that make up a car, App
Engine is the fully built car that just runs. It has a default set of tires, seats, and
paint color—these are the language runtimes, performance settings, and where
the app is homed. And you can customize all these.

The engine here is App Engine’s cluster management, and it's the only aspect
that is not configurable: it’s the lower-level service that guarantees high
availability, and thus cannot be changed. So, in the same sense that you want to
get in the car and just drive, App Engine allows customers to jump right in and
“just code.”

How App Engine works

For customers building their next great application, who need a cloud platform
that is easy to use, won't become an ongoing maintenance headache, and of
course, will scale just in case the app becomes a smashing success: Enter
Google App Engine. This video will walk you through how App Engine can be
used at each level of application needs, and most importantly, keep servers and
client batteries from melting.

“””””
Video subtitles : https://www.youtube.com/watch?v=ytT2-kL9v2o

so you have a great idea for an app

that's going to run across mobile

tablets laptops and PCs and after you've

done all the hard work of designing the

UI now it's time to get to the really

hard problems that is how do you get all

of these devices communicating between

one another it's time for to take

advantage of the cloud acting as a

central resource each client can use the

cloud to send and receive messages

keeping all the other clients in sync

with each other but not every cloud is

created equal

you'll want something that's easy to use

won't become an ongoing maintenance

headache and of course scale just in

case your app becomes a smashing success

enter Google App Engine which makes it

easy to build scalable cloud solutions

for web apps and mobile backends app

engine reduces the pain of building

these solutions by providing a suite of

powerful usable services and it also

reduces deployment pains by

automatically running and managing your

applications for you this ensures that

your app always has the right amount of

server capacity to handle your traffic

not too much not too little but back to

the point you're building the next great

app how can Google App Engine help with

that let's say user a wants to send a

message to user B but user B isn't

currently online we're gonna need some

place to store the message the App

Engine data store is the easiest choice

for this it's part of App Engine so it's

ready to use with no configuration or

setup needed you hand your data to App

Engine and it takes care of replicating

it to multiple data centers across the

world so it's always available to your

global customers no scheduled

maintenance or configuration headaches

required but best of all the data store

will continue to scale whatever size

your app needs as you write more data

you get more capacity all without having

to lift a finger

and of course storing messages is only

half the problem when user becomes back

online
you'll need to retrieve any messages

waiting for and to do this you'll need

some server logic to fetch the right

messages for the specific user and

return them to the appropriate client

and thankfully you can author that

server-side logic on one of our many

supported languages like Java Python

goat and PHP now as the number of your

users grow you'll notice that your app

often ends up fetching the same data

over and over and over and over again

frankly some data is just more popular

than other data fetching this data does

take a bit of time and computation and

repeated fetches of the same information

is hugely wasteful to avoid melting your

servers with wasteful fetching App

Engine provides a feature to improve

retrieval speed called men

- memcache allows you to store commonly

accessed data in fast in-memory

distributed cache so your app isn't

sitting around waiting for a bunch of

data store writes or for some business

logic to execute also did I mention less

melting that's a really important part

of course besides the datastore and

memcache there is a plethora of api's at

your disposal but that's another video

anyhow back to your app using datastore

and memcache you can store and retrieve

data quickly the runtime logic allows

you to specify custom request handlers

so your client gets exactly the

responses they need however you don't

always want your clients to wait around

for server-side logic to finish

sometimes you want the server to do some

work and you want your clients to come

back later for the result for example

processing an upload video or applying

an awesome filter to a picture of a soon

to be eaten entree these high compute

operations take a bit of time to finish

and leaving the client connection open

during this time can show up your users

batteries which doesn't make for a great

user experience plus there's probably

work your app wants to do when no one

else is around like gathering statistics

of how many of your users are

interacting with one of your new

features to help with this app engine

provides the tasks API which allows you

to schedule work to be run later or in

the background which is important to

keep your users battery from melting

while waiting for the server to finish

work but that's another video at this

point you have a basic app set up and

running as your app grows you'll

probably want to add support for binary

files like a user profile photo or some

awesome homemade music now while the

data store is built for structured data

it might not be the right place for

binary files as such it's time to look

deeper at your storage options Google

Cloud Storage is up to this particular

task allowing you to store an unlimited

number of files or objects up to

terabytes in size that are available

globally each with the access controls

that you specify and so far we've talked

about how App Engine scales on the back

end but it's also worth pointing out how

App Engine provides another invisible

layer which helps your app scale as well

you see App Engine provides a dedicated

layer of front ends which makes sure

client data get off the internet and

onto Google's network as quickly as

possible while also making sure that

your code and the App Engine runtime

don't have to wait around for slow or

poorly connected clients now don't

forget your clients can talk directly to

many of the backend services without

needing to go through your server-side

code

for example your user can upload an

image and data directly to cloud storage

or grab structured data right from the

cloud store API and even talk directly

to the tasks API to see what pending

work is available for processing before

you go running off to build your app

there's a there's a bit of planning that

needs to happen though namely as your

service or back-end changes over time

keeping your Android web and iOS clients

in sync with those changes becomes a

really gnarly task to help with this

Cloud endpoints makes your life just a

little bit easier you simply define your

server API and the cloud endpoints will

generate the client libraries for you

which not only takes care of data

serialization but handles the connection

and minimizes transport bloat across the

wire with all these features and

services at your command Google App

Engine allows you to build the next

great app and scale it big with the

least amount of trouble for you C

building the next amazing app is as easy

as that now go build something great

“”””
Customer example
Read about how Backflip Studios uses App Engine to handle unpredictable load
and focus on development. 

Where App Engine fits within GCP

On the compute continuum, customers have four GCP options/products that
are aligned with where the code needs to run. 

App Engine is a platform-centric solution.

Click on the cards to read the definition for each product and the types of customers
it is ideal for.

Compute Engine
IaaS

Virtual machines with industry-leading price/performance

Ideal for customers that:

Need complete control over the virtual-machine infrastructure

Need to make changes to the kernel, such as providing their own network or
graphics drivers to squeeze out the last drop of performance

Need to run a software package that can’t easily be containerized or have

existing VM images to move to the cloud


 Kubernetes Engine 
Hybrid

Cluster manager and orchestration engine built on Google’s container

experience
Ideal for customers that:

Have been challenged when deploying or maintaining a fleet of VMs and it

has been determined that containers are the solution

Have containerized the workloads and need a system on which to run and
manage them

Never want to touch a server or infrastructure

Don’t have dependencies on kernel changes or on a specific (non-Linux)

operating system

App Engine 
PaaS

A flexible, zero ops platform for building highly available apps

Ideal for customers that:

Want to focus on writing code and never touch a server, cluster, or

infrastructure

Build quickly and highly value time to market

Do not want to worry about a pager going off or 5xx errors

Need an app to have high availability without a complex architecture

Cloud Functions 
Serverless Logic
 A lightweight fully managed serverless execution environment for
building and connecting cloud services
Ideal for customers that:

Need to connect and extend cloud services

Want to automate with event-driven functions that respond to cloud events

Use open and familiar JavaScript

Never manage a server or runtime environment

How Compute products fit
Now that you understand a few of compute products, watch a quick overview of
the high-level architecture of App Engine and Compute Engine and the
beginnings of the continuum of computing. This video will dive into the
architecture of Google scale and touch on the possibilities of using App Engine
and Compute Engine together.
0:00 / 0:00

What is included
With App Engine, customers get services and application programming
interfaces (APIs) that address key needs of developers including:
 Multiple options to store application data including:
o Caching - App Engine Memcache
o Cloud Storage - store any objects up to 5 TB in size
o Cloud Datastore - persistent, low-latency memory for serving data to
applications
o Cloud SQL - relational database that can be run on persistent disk >1
terabyte in size
o Cloud Bigtable - NoSQL database for heavy read/writes and analysis
 Task queues
 User authentication
 Automatic scaling to meet any demand
 Load balancing
 Versioning for your app
 Logging
 Monitoring
 Robust security tools like Cloud Security Scanner
 Global network
 Support packages
...all with high availability and guaranteed redundancy.
Knowledge Check 
What does it mean when organizations are looking to become zero-ops?
Turn over 1 card see if you can find the right answer.
 

Organizations that want to become zero-ops want to have almost no

staff dedicated to the operations of IT infrastructure.

That's right! 
You’re the zero-ops hero!

When a customer is looking to become zero-ops, they’re looking for an

on-premises solution to build their app on.

Nope! This doesn't mean they are zero-ops.

First, hire a staff dedicated to maintaining and operating the IT systems.

This is not the answer you’re looking for...

2. Why Google: App Engine Value

Proposition
Introduction
So far we have defined what App Engine is, discussed how it works, and looked
at a customer example. 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 proposition
Let's begin with the high-level value proposition. 

App Engine is built on Google’s years of experience running some of the highest
performance, global web-based apps and backend systems. Google runs 7
cloud products with more than a billion users. App Engine gives this capability
to everyone. Google is starting to lead the competition with:
 Differentiators that developers notice
 Low cost
 Breadth of products and breadth of network
 Ease of use and performance
 Practically infinite scalability

The Google Cloud Platform suite of products enhances the value of App Engine
by vastly extending its capabilities.
Challenges addressed
Building an app with App Engine relieves customers from an incredible amount
of difficult, no-value work they would have to do to:

 Build their own infrastructure

 Grow it as their computing needs increase
 Make sure it’s available night and day

This can be up to 70% of the work required to get your app up and running.
Instead, Google provides customers with a world-class information technology
platform-reliability service. 

Business value proposition

For business key players, ensure they understand that App Engine addresses
the following high-level key points.
Click the headings below to find out more

General business





Developer productivity
 Apps cost less to develop with App Engine and new apps get to market
faster because Developers:

 Are more productive because they can get laser-focused on producing

top-notch apps with the best tools
 Have an easier time of managing code in development and moving it to
production
 Can easily build apps that draw on the power of the entire Google Cloud
Platform product suite
 Don’t have to spend time coordinating with IT operations or DevOps,
since the need for their help is greatly reduced or eliminated

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

The key terms to listen for are the cost of development, downtime, and time to

market. Homing in on these triggers will help you further the sales conversation.

Technical value proposition

For a technical stakeholder, they care about the benefits of using App Engine,
including its ability to:
 Provide the code and configuration tools for your app production pipeline
 Provide superb consistency and availability at all points in the development and
production process
 Provision all the necessary underlying infrastructure
 Automatically increase capacity within the limits you set. If you need more,
increase your limit. No more time-consuming capacity planning
 Eliminate patches for zero-day exploits; Google takes care of it
Technical challenges
It is important to understand the technical challenges a product solves so you
can listen for the key terms in customer conversations.

The key terms to listen for are accelerating development time and reducing

time spent managing and maintaining infrastructure, capacity planning, and
patching.

Knowledge Check
Which of these developers is expressing a productivity benefit App Engine
provides?
Select all the cards that apply.

Developer 1: 
“Thanks to App Engine, it’s easier to manage code in development and
move it to production.”

That’s right! You’re going places.

Developer 2: 
“Using App Engine, I have complete control over the virtual-machine
infrastructure.”

You’re thinking of Compute Engine’s benefits.

Developer 3: 
“With App Engine, I can easily build apps that draw on the power of the
entire Google Cloud Platform product suite.”

Correct! You must be some sort of Google guru.

Recap
Top takeaways

App Engine helps customers because they don't have to build their own
infrastructure.
App Engine saves organizations time and costs in software application
development by eliminating the need to buy, build, and operate computing
hardware and other infrastructure.

If businesses need to accelerate time to market, App Engine helps accomplish

that.

App Engine provides services that help customers meet key developer needs
with user authentication, versioning, and robust security tools like Cloud
Security Scanner.
Want more information? 
Marketing

Documentation

Additional resources:
Introduction to App Engine on Youtube
Choosing a Compute Option
Building a mobile app on Google Cloud Platform
When to use App Engine flexible environment
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
Kubernetes
Engine
 Let's Get Started
In this module...
You will be able to define Kubernetes Engine and discuss how it works and fits
within the GCP portfolio, including use cases. In addition, you will learn about
the value propositions of Google Kubernetes Engine.
You'll get answers to...
1. What is Kubernetes Engine?
 How does Kubernetes Engine work?
 How does Kubernetes Engine fit within the GCP portfolio?
2. What are the value propositions for Kubernetes Engine?

1. What is Google Kubernetes Engine?

Introduction
Let's begin by defining Google Kubernetes Engine, how it works, and how it fits
within GCP. 

Google Kubernetes Engine defined

Google Kubernetes Engine is a managed environment for deploying
containerized apps. It brings our latest innovations in developer productivity,
resource efficiency, automated operations, and open source flexibility to
accelerate time to market. GKE is a powerful cluster manager and orchestration
system for running Docker containers in Google cloud. 

Kubernetes Engine manages containers automatically, based on specifications

(such as CPU and memory). It's built on the open-source Kubernetes system,
making it easy for customers to orchestrate container clusters or groups of
containers. Because it is built on the open source Kubernetes system, it
provides customers the flexibility to take advantage of on-premises, hybrid, or
public cloud infrastructure.

How Google Kubernetes works

Google Kubernetes Engine is a managed environment for deploying
containerized applications.
Click on the arrows to learn more about how Google Kubernetes works.


 


Kubernetes Engine
Kubernetes Engine is a managed service environment for deploying
containerized applications. It brings our latest innovations in developer
productivity, resource efficiency, automated operations, and open source
flexibility to accelerate our customer's time to market.
Customer example
So now that we have the basics, let's look at a customer story that shows how
Kubernetes can help.
Click on the arrows to learn more about how Kubernetes has helped RealMassive.


Results
With Google Cloud Platform, RealMassive is transforming the commercial real
estate market:

 Presents real estate information faster and more accurately than the
competition
 Launches new markets in a single day
 Saves 50% on cloud hosting costs

Where Kubernetes Engine fits within GCP

On the compute continuum, customers have four GCP options/products that
are aligned with where the code needs to run. Kubernetes Engine is in the
middle (cluster). Note that all solutions are supported by Google Networking.
Click the cards to find out more. Each solution will be covered in detail in this training.


 Compute Engine
IaaS

Virtual machines with industry-leading price/performance

Ideal for customers that:
o Need complete control over the virtual-machine infrastructure
o Need to make changes to the kernel, such as providing their own
network or graphics drivers to squeeze out the last drop of
performance
o Need to run a software package that can’t easily be containerized or
have existing VM images to move to the cloud

Kubernetes Engine 
Hybrid

Cluster manager and orchestration engine built on Google’s container

experience
Ideal for customers that:
o Have been challenged when deploying or maintaining a fleet of VMs,
and it has been determined that containers are the solution
o Have containerized the workloads and need a system on which to
run and manage them
o Never want to touch a server or infrastructure
o Don’t have dependencies on kernel changes or on a specific (non-
Linux) operating system

App Engine 
PaaS

A flexible, zero ops platform for building highly available apps

Ideal for customers that:
o Focus on writing code and never touch a server, cluster, or
infrastructure
o Building quickly and time to market are highly valued
o Not worry about a pager going off or 5xx errors
 o Need app to have high availability without a complex architecture

Cloud Functions 
Serverless Logic

A lightweight fully managed serverless execution environment for

building and connecting cloud services
Ideal for customers that:
o Need to connect and extend cloud services
o Want to automate with event-driven functions that respond to cloud
events
o Use open and familiar JavaScript
o Never manage a server or runtime environment
Knowledge Check
Key terminology: Let's see what you have learned about Google Kubernetes
Engine and what it does.
Select the correct term for each definition.  

Provides the operating system that is needed to run an application. 

Container

A tool that puts the application into a container.

Docker

An open source container orchestration tool for managing a cluster of containers as a

single system.

Kubernetes

A managed service environment for deploying containerized applications.

Kubernetes Engine

SubmitShow Feedback

Knowledge check
Which of the following describes where Kubernetes Engine fits within GCP?
Turn over the 1 correct card.
 

Virtual machines with industry-leading price/performance

No, sorry that is Compute Engine. 

Cluster manager and orchestration engine built on Google’s container

experience

That's right! 

A flexible, zero ops platform for building highly available apps

Sorry, that is App Engine.

A lightweight fully managed serverless execution environment for

building and connecting cloud services

Sorry, that is Cloud Functions.

2. Why Google: Google Kubernetes

Engine Value Proposition
Introduction
So far you have learned what Kubernetes Engine is and how it works, and
looked at customer examples. Now you can look at the value Kubernetes
Engine brings to customers by reading the high-level value proposition, and as
the business and technical value proposition for target prospects.
High-level value proposition
Customers can build apps that run on Kubernetes Engine that:
 Are highly secure and reliable and backed by Google’s service level agreement.
 Will scale up to handle massive computing loads quickly and efficiently.

Google’s entire infrastructure runs on containers, and we launch more than 2

billion per week. It’s fundamental to everything we do. With over 50 Google
developers contributing code on a daily basis to the Kubernetes open source
project, Google has an intimate knowledge of how to run at peak performance.

Challenges addressed
It is important to understand the high-level challenges a product solves so you
can listen for the key terms in customer conversations. 
Click on each challenge and learn how Google Kubernetes Engine addresses it. 

Speed

Scalability

Complexity

Time

Business value proposition

Before beginning down the Google Kubernetes Engine path, customers need to
understand the value of containers and Kubernetes over traditional methods. 
Click on each tab to learn the value Google Kubernetes Engine provides. 

 Performance and power

 Discounts and pricing
 Scaling w/o downtime
 Google expertise
Google expertise and experience
Google has been pioneering container orchestration solutions for 15 years.
Customers gain the benefit of our years of experience.

Technical value propositions

Technical stakeholders care about the benefits to the client using Google
Kubernetes Engine.

Click the arrow to understand the overall technical value and specifics when talking to
technical teams and developers.

 Overall technical value

 Maximize resource utilization

 Seamlessly migrate code from development to production
 Simplify management of code from developers to cloud to hybrid
on-premises/cloud to multiple cloud providers
 Easily scale up and down clusters based on business needs
 Improve applications reliability through integrated health checking
 Nodes can be regional instead of in a single zone, which protects
customers if a single zone fails

 For Developers
 The code runs the same on a laptop, server, or in the cloud
 Copy and reuse public images of popular open source tools
 Easily adjust the resources allocated to your containers, or the
size of your container cluster, as your application's requirements
change
 Google Container Registry makes it easy to store and access your
private Docker images
 Google Container Builder runs container image builds in a fast,
consistent, and reliable environment on Google Cloud Platform
 Enable Google Stackdriver Logging which lets you manage and
analyze log data from AWS as well as Cloud Platform in one place
 Fast startup when called
 Reduced work setting up OSs

Knowledge check 
Value propositions: Take a minute to associate the key value points to each
type of stakeholder: business or technical. 
Drag and drop the value points that best align to the stakeholder.

Business Stakeholder

Google expertiseDiscounts and pricing

Technical Stakeholder

Simplify management of codeSeamlessly migrate code from development to

production
Improve applications reliability through integrated health checking

SubmitShow Feedback

Recap
Top takeaways

A software container provides the operating system needed to run an

application.

Kubernetes Engine is a managed environment for deploying containerized apps.

The benefit of Kubernetes Engine that appeals to customers is the ability to

scale without downtime.

Customers can build apps that run on Kubernetes Engine that are highly secure
and reliable and backed by Google’s service level agreement.

Google Kubernetes Engine is a hybrid solution. 

Want more information? 
Marketing

Documentation

Product Manager Overview (Video)

Pricing

Additional resources (Optional): 

Containerizing example using Minecraft
What is Docker?
What is Kubernetes?
Technical Overview of Kubernetes
Your GCP compute options, explained
Kubernetes code lab exercise
Change Log
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 Functions
Let's Get Started
In this module...
You will be able to define Cloud Functions and how it works and fits within the
GCP portfolio, including use cases. In addition, you will learn about the value
propositions of Cloud Functions.

You'll get answers to...

1. What is Cloud Functions? 

 How does Cloud Functions work?

 How does Cloud Functions fit within the GCP portfolio?
2. What are the value propositions for Cloud Functions?

1. What is Cloud Functions?

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

Cloud functions defined

Cloud Functions is a serverless execution environment for building and
connecting cloud services. With Cloud Functions, customers write simple,
single-purpose functions that are attached to events emitted from their cloud
infrastructure and services. 

The Cloud Function is triggered when an event being watched is fired. The code
executes in a fully managed environment. There is no need to provision any
infrastructure or worry about managing any servers.

Cloud Functions are written in Javascript and execute in a Node.js environment

on Google Cloud Platform. Customers can take their Cloud Function and run it
in any standard Node.js runtime which makes both portability and local testing
a breeze.
How Cloud Functions works
 Connect and Extend Cloud Services

Connect and Extend Cloud Services

 Events and Triggers

Events and Triggers

 Serverless

Serverless
Customer examples
Now that you understand what Cloud Functions is and how it works, let's take a
look at some examples of it working.

Customer quote: Meetup

Common Use cases

Where Cloud Functions Fits within GCP

On the compute continuum, customers have four GCP options/products that
are aligned with where the code needs to run. Cloud Functions is the serverless
logic solution.
Microservices Over Monoliths: 
Developer agility comes from building systems composed of small,
independent units of functionality focused on doing one thing well. Cloud
Functions lets customers build and deploy services at the level of a single
function, not at the level of entire applications, containers, or VMs.
Click the cards to read the definition for each product and the types of customers it is
ideal for.

Compute Engine

IaaS
Compute Engine

Virtual machines with industry-leading price/performance

Ideal for customers that:

o Need complete control over the virtual-machine infrastructure

o Need to make changes to the kernel, such as providing their own
network or graphics drivers to squeeze out the last drop of
performance
o Need to run a software package that can’t easily be containerized
or have existing VM images to move to the cloud

Kubernetes Engine

Hybrid
Kubernetes Engine

Cluster manager and orchestration engine built on Google’s container

experience

Ideal for customers that:

 o Have been challenged when deploying or maintaining a fleet of
VMs and it has been determined that containers are the solution
o Have containerized the workloads and need a system on which to
run and manage them
o Never want to touch a server or infrastructure
o Don’t have dependencies on kernel changes or on a specific (non-
Linux) operating system

App Engine

PaaS
App Engine

A flexible, zero ops platform for building highly available apps

Ideal for customers that:

o Want to focus on writing code and never touch a server, cluster, or

infrastructure
o Build quickly and highly value time to market
o Do not want worry about a pager going off or 5xx errors
o Need apps to have high availability without a complex architecture

Cloud Functions

Serverless Logic
Cloud Functions

A lightweight fully managed serverless execution environment for

building and connecting cloud services

Ideal for customers that:

o Need to connect and extend cloud services

 o Want to automate with event-driven functions that respond to
cloud events
o Want to use open and familiar JavaScript
o Never manage a server or runtime environment
Knowledge Check
Now that you have learned about Cloud Functions and what it does, let's check
what you know. 

What is Cloud Functions

Select the correct definition of Cloud Functions.

Google Cloud Functions is a serverless execution environment for building and

connecting cloud services.

Google Cloud Functions is a cluster manager and orchestration engine built on

Google’s container experience.

Google Cloud Functions is a flexible, zero ops platform for building highly available
apps.

Google Cloud Functions is virtual machines with industry-leading price/performance.

Knowledge check
How Cloud Functions works: Match the description of a Cloud Functions
functionality to the term. 
Drag and drop the description to the functionality.

Cloud Functions can be configured to respond to events such as changes in the

environment, including changes to data in a database, files added to a storage system,
or a new virtual machine instance being created. Cloud Functions removes the work of
managing servers, configuring software, updating frameworks, and patching operating
systems; it is fully managed by Google. Cloud Functions provides a connective layer of
logic that lets customers write code to connect and extend cloud services. 

Connect and Extend Cloud Services

Events and Triggers

Serverless

SubmitShow Feedback

2. Why Google: Cloud Functions

Value Proposition
Introduction
So far you have learned what Google Cloud Functions is, how it works, looked at
customer examples, and reviewed where it fits within GCP. Now let's define the
high-level value and customer challenges it addresses. 
High-level value 

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

Improve developer productivity

Integration complexity

Costs of integration

Recap
Top takeaways

With Cloud Functions, customers can write simple, single-purpose functions

that are attached to events emitted from their cloud infrastructure and services.

Cloud Functions connects and extends by providing a layer of logic that

customers can write code for in order to access other services.

Cloud Functions offers serverless economics and accelerates developer

productivity. 

Cloud Functions helps customers build and deploy services at the level of a
single function, not at the level of entire applications, containers, or VMs.
What have you learned?
We defined Cloud Functions including:
 How it works
 How it fits within the GCP portfolio
 Common use cases
We reviewed the business value propositions of Cloud Functions.

Additional resources:
Cloud Functions Website
Cloud Functions Documentation
Cloud Functions Overview

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

GCP Cloud Functions

What have you learned?
We defined Cloud Functions including:
 How it works
 How it fits within the GCP portfolio
 Common use cases
We reviewed the business value propositions of Cloud Functions.

Additional resources:
Cloud Functions Website
Cloud Functions Documentation
Cloud Functions Overview

Not quite!

Run the entire network in the cloud so that customers don't have to spend time
on network installations, maintenance, and upgrades: Google Virtual Private
Cloud

Distributes resources to single and multiple regions around the globe and
scales up and down with Intelligent Autoscaling: GCP Cloud Load Balancing
 Leverages Google's globally distributed edge caches to accelerate content
delivery for websites and applications served by Google Compute Engine: GCP
Cloud CDN

Provides options to connect to Google with higher availability or lower latency

(or both) than standard internet connections: GCP Cloud Interconnect

Programmable so that customers can easily publish and manage millions of

DNS zones and records using a simple user interface, command-line interface
(CLI) or application programming interface (API): GCP Cloud DNS

Introduction to
Firebase
Let's Get Started
In this module...
You will be able to define Firebase and how it works and fits within the GCP
portfolio, including customer examples. In addition, you will understand the
value propositions of Firebase.

You'll get answers to...

1. What is Firebase? 

 How does Firebase work?

 How does Firebase fit within the GCP portfolio?
2. What are the value propositions for Firebase?
 1. What is Firebase?
Introduction
Let's begin by defining Firebase, how it works, and how it fits within GCP. 
Firebase defined
Firebase is Google’s mobile app development platform that provides tools and
cloud services to help solve many common challenges across the lifecycle of
application development, enabling developers to focus on creating unique value
for their customers.
In particular, it helps mobile application development teams:

 Develop faster and easier with cloud backend services

 Understand their application stability and performance with remote monitoring
 Grow their user base and engagement with analytics and A/B testing, which is a
controlled experiment with two variants, A and B. 
 Firebase provides SDKs across platforms, on iOS, Android, Web (JavaScript),
Unity and C++

How Firebase works

Mobile app teams can integrate their mobile apps with one of the available
SDKs (software development kits) and manage the integrated Firebase services
via the Firebase console, which includes tools from Google for developing apps,
engaging with users, and earning more through mobile ads.

Customer example
Snapchat uses Firebase Crashlytics to monitor their app errors and crashes.

There are more case studies available here. 

Where Firebase fits in GCP

Firebase is GCP's mobile extension. Several of Firebase’s products are built on
top of GCP products, providing mobile-optimized SDKs and capabilities.

For example, Firebase provides client-side caching and offline network handling
for Cloud Storage. In another example, images stored on Cloud Storage for
Firebase can also be accessible and managed via the GCP console.


 Cloud Functions for Firebase
Run your mobile backend code without managing servers using Cloud
Functions for Firebase.

Cloud Firestore for Firebase

Store and sync app data at global scale with Cloud Firestore for Firebase.

Cloud Storage for Firebase

Store and serve content with ease with Cloud Storage for Firebase.
Knowledge Check
Now that you have reviewed the Firebase basics, what are the answers to these
questions? 
Think about your answer and click on the question to learn the answer. 

What type of platform is Firebase?

What is the common challenge it helps developers with? 

How does Firebase help development teams? 

2. Why Google: Firebase Value

Proposition
Introduction
So far you have learned what Firebase is and how it works, and looked at
customer examples and where it fits within GCP. Now it is important to
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
Let's start with the high-level value of Firebase.
"Firebase provides a comprehensive mobile app development platform, built on
Google’s world-class cloud infrastructure, and integrates with many Google
offerings, including Google Cloud Platform, Google Analytics, and Google Play."

Challenges addressed
It is important to understand the business challenges a product solves so you
can listen for the key terms in customer conversations.
Click to learn how Firebase addresses each customer challenge.

More rapid application development

Firebase provides core backend services to enable rapid application
development and extension, freeing app teams from managing their own
infrastructure. e.g., Firestore, Authentication, and Analytics.

Monitor app stability and performance

Firebase provides application monitoring tools, including Crashlytics
(error and crash reporting) and Performance Monitoring (latency and
network monitoring) that help application teams build great experiences
for their users.

Grow user engagement and business success

Firebase provides tools to help application teams better understand and
fine-tune their application experience, including Analytics, A/B Testing,
and Predictions. With these insights, application teams can also be more
informed about their GCP deployment strategies (e.g., managing regions
based on most valuable customers, not just traffic volume).
Business value proposition
In Firebase opportunities, business buyers are most concerned about saving
time and cost and ensuring they have the scalability, availability, and security for
their applications.

Save time and cost

Save time and cost by using Firebase services to help solve many of the
common challenges across the application development lifecycle. As a result,
customers can channel more resources into building differentiated value for
their customers.

Scalability, availability, and security

Firebase is built on Google’s world-class cloud infrastructure that can scale to
grow with their app and business. From prototype to production to planet-scale.

To see individual product value propositions,

see https://firebase.google.com/products/.
Technical value proposition
For technical key players, ensure they understand that Firebase addresses ease
of use and familiar mobile platforms. 
SDKs are available across mobile platforms including Android, iOS, JavaScript,
and Unity, C++, providing a single consistent experience across Firebase
offerings. 

Knowledge Check
Value propositions: Check your knowledge of the key values for technical and
business buyers. 
Drag and drop the identified values to the appropriate buyer type.

Ease of useScalability, availability, and securitySave time and costSDKs across mobile
platforms

Business

Technical

SubmitShow Feedback

Recap
Top takeaways
Firebase helps mobile application development teams develop faster and easier
with cloud backend services.

Mobile app teams can integrate their mobile apps with one of the available
SDKs (software development kits)and manage the integrated Firebase services
via a console which includes tools from Google for developing apps, engaging
with users, and earning more through mobile ads.

SDKs are available across mobile platforms including Android, iOS, JavaScript,
Unity, and C++, providing a single consistent experience across Firebase
offerings.
Additional resources:
 Firebase website

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
Networking
 Let's Get Started
In this module...
You will be able to define Google networking and how it works and fits within
the GCP portfolio, including a customer example. In addition, you will be able to
define the value propositions of Google networking.

You'll get answers to...

1. What is Google Networking? 
 How does it work?
 How does it fit within the GCP portfolio?
2. What are the value propositions for Google Networking?

Warm Up
Networking background
Computers communicate with each other on a network. The computers in a
single location, such as an office, are connected on a local area
network (LAN). Multiple locations can have their LANs connected to a wide area
network (WAN). Most networks today are connected to the internet, enabling
millions of personal computers, servers, and other smartphones and devices to
communicate, and provide and consume information technology (IT) services.

1. What is Google Networking?

Introduction
Let's begin by defining Google Networking, how it works, and how it fits within
GCP.
Google Networking defined
For the past 15 years, Google has been building out the fastest, most powerful,
highest quality cloud infrastructure on the planet.
Google’s high-quality private network connects our regional locations to more
than 100 global network points of presence close to users. Google Cloud
Platform also uses state-of-the-art software-defined networking and distributed
systems technologies to host and deliver a customer’s services around the
world. When every millisecond of latency counts, Google ensures that content is
delivered with the highest throughput.
What are the primary products included in Google
networking? 
Click on each product to learn more about what it does.

How Google Networking works

Here is an example network diagram for an application which bridges a
customer's data center, a colocation facility, and Google Cloud Platform. 

Click on the + icons to learn about the different components.

Customer Example WIX.com

Where Google Networking fits within GCP
All Google customers — GCP and otherwise — benefit from our superb
networking.

””””

Video subtitles : https://youtu.be/HGdKHqMTAko

“”””’

Knowledge Check
GCP Cloud Networking products: Google has been building out the fastest,
most powerful, highest quality cloud infrastructure on the planet. Consider the
functions of each of the primary products. 
Drag the product function description to the product name/icon. 

GCP Virtual Private Cloud

GCP Cloud Load Balancer

GCP Cloud CDN

GCP Cloud Interconnect

GCP Cloud DNS

Translates requests from domain names to IP addresses with the infrastructure to

manage millions of zones and records. Serves content to end users with high
availability and performance, typically by storing files close to the user. Provides
consistent performance for users by replacing a powerful server with a cluster of
servers that adds resources and capacity as needed to scale. A comprehensive set of
networking capabilities and infrastructure managed by Google, with isolation and fine-
grained networking policies.
Connect existing infrastructure to Google network edge with enterprise-grade
connections. Partner network service providers are available.

SubmitShow Feedback

2. Why Google: Networking Value

Proposition
Introduction
So far we have defined what Google network [networking] is and how it works,
and looked at a customer example. 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 and challenges addressed
So far we have defined what Google Networking is, how it works, and common
use cases. Now let's understand the value it brings to Google customers by
defining the high-level value proposition and the product value propositions
within Google networking. 
Click on the section headings to learn the high-level value proposition and the
customer challenges that are addressed. 

High level value

 



Challenges addressed







Value Propositions
Click on the circles to read the value of each networking product. 

Knowledge Check
Cloud Networking value propositions: As we have said, the Cloud Networking
products/solutions are the foundation for GCP. Take a moment and match a
primary Cloud Networking product to the value statements. 
Select the product that matches each value statement. 

Run the entire network in the cloud so that customers don't have to spend time on
network installations, maintenance, and upgrades. 

Select...

Distributes resources to single and multiple regions around the globe and scales up
and down with Intelligent Autoscaling. 

Select...
Leverages Google's globally distributed edge caches to accelerate content delivery for
websites and applications served by Compute Engine. 

Select...

Provides options to connect to Google with higher availability or lower latency (or both)
than standard internet connections.

Select...

Programmable so that customers can easily publish and manage millions of DNS
zones and records using a simple user interface, command-line interface (CLI) or
application programming interface (API).

Select...

SubmitShow Feedback

Recap
Top takeaways

A "network" is an isolated global resource holding network configuration.

Cloud CDN included in Google Cloud Networking serves content to end users
with high availability and high performance.

Virtual Private Cloud allows customers to connect GCP resources in a separate

cloud and isolate them from each other for security and compliance.

Cloud DNS publishes and manages millions of DNS zones and records using a
simple user interface, command-line interface (CLI), or application
programming interface (API).
Want more info?
Documentation

Cloud Virtual Network

Cloud Load Balancing

Cloud CDN
Cloud Interconnect

Cloud DNS 

Additional resources:
 Virtual Private Cloud (VPC)
 Cloud Load Balancing
 Cloud CDN
 Cloud Interconnect
 Cloud DNS
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