• Use GCP to Build Your Apps

< Action
Safe
Title
Safe >
GCP offers a variety of compute services spanning
different usage options

Google
Compute Engine App Engine Cloud Functions
Kubernetes Engine

IaaS PaaS Serverless logic Hybrid

Virtual machines with A flexible, zero ops A lightweight fully Cluster manager and
industry-leading platform for building highly managed serverless orchestration engine built
price/performance available apps execution environment for on Google’s container
building and connecting experience
cloud services, good
option for triggering code
to run based on some
kind of event
Compute Engine is an infrastructure-centric solution

1.Type of Iaas
2.Scalable, high-performance VMs
3.Run any computing workload, such as,
web-server hosting, application hosting,
and/or application backends
4.Predefined or custom machine types
5.Windows or Linux (allows users to run
their choice of operating system.)
6.No upfront investment required
Create VMs that are right for your workloads

Machine type options to consider:

● Higher proportion of memory to
CPU
● Higher proportion of CPU to
memory
● Blend of both
Select from predefined VM
configurations:
● General-purpose
● Memory-optimized
● Compute-optimized
Customize your own configuration
General-purpose machine types offer the best price-performance ratio for a variety of
workloads.

N1 machine types offer up to 96 vCPUs, 6.5 GB of memory per vCPU, and are
available on Intel Sandy Bridge, Ivy Bridge, Haswell, Broadwell, and Skylake CPU
platforms.

N2 machine types offer up to 80 vCPUs, 8 GB of memory per vCPU, and are

available on the Intel Cascade Lake CPU platforms.

E2 machine types are cost-optimized VMs that offer up to 16 vCPUs with up to 8

GB of memory per vCPU. E2 machines have a predefined CPU platform running either
an Intel or AMD EPYC processor.
Memory-optimized machine types are ideal for memory-
intensive workloads because they offer higher memory per core
than other machine types, with up to 12 TB of memory.

Compute-optimized machine types offer the highest

performance per core on Compute Engine and are optimized for
compute-intensive workloads. Compute-optimized machine
types offer Intel Scalable Processors (Cascade Lake) and up to
3.8 GHz sustained all-core turbo.

Shared-core machine types are available in the N1 and E2

families. These machine types timeshare a physical core. This
can be a cost-effective method for running small, non-resource
intensive applications.
https://cloud.google.com/compute/docs/machine-types
Building virtual disks
Network storage can be attached to VMs as
persistent disks (PDs).
PDs are cost-effective, durable, and offer good
performance.
Local SSDs provide higher performance with
lower latency, but exist only for the lifetime of a
specific instance.
Standard PD throughput performance and IOPS
increases linearly with the size of the disk until it
reaches set per-instance limits.
SSD PD IOPS performance depends on the
number of vCPUs in the instance in addition to
disk size. "Input/Output Operations Per Second."

https://cloud.google.com/compute/docs/disks/
https://cloud.google.com/persistent-disk
Storage Type
✓Zonal standard persistent disk and zonal SSD persistent disk: Efficient,
reliable block storage.

✓Regional persistent disk and regional SSD persistent disk: Regional block
storage replicated in two zones.

✓Local SSD: High performance, local block storage.

✓Cloud Storage buckets: Affordable object storage.

✓Filestore: High performance file storage for Google Cloud users.

Compute Engine pricing

https://cloud.google.com/products/calculator/
Google Cloud Platform Pricing Calculator
• All virtual machines are charged for 1 minute at boot time, which is the minimum charge
for a VM.

• After that, per-second pricing begins, meaning that you only pay for the compute time used.

• Google also offer sustained use discounts, which automatically provide discounted prices
for long-running workloads without the need for sign-up fees or any up-front commitment.

• The GCP Pricing Calculator is a great way to see pricing estimates based on the different
configuration options that are available under instances,
• sole-tenant nodes,
• persistent disks,
• load balancing, and
• cloud TPUs.
Where App Engine fits within GCP

Google
Compute Engine App Engine Cloud Functions Kubernetes
Engine
IaaS PaaS Serverless logic Hybrid

Virtual machines with A flexible, fully managed A lightweight fully Cluster manager and
industry-leading platform for building highly managed serverless orchestration engine built
price/performance available apps execution environment for on Google’s container
building and connecting experience
cloud services
App Engine within GCP
• Google App Engine is a Platform as a Service and cloud computing platform for developing and hosting web
applications in Google-managed data centers.

• Applications are sandboxed and run across multiple servers.

• App Engine is a fully managed, serverless platform for developing and hosting web applications at scale.

• You can choose from several popular languages, libraries, and frameworks to develop your apps, then let
< Action
SafeApp Engine take care of provisioning servers and scaling your app instances based on demand
Title
•SafeApp
> Engine allows you to have high availability apps without a complex architecture.
https://cloud.google.com/appengine/docs
Several popular languages supported by Google
App Engine

< Action
Safe
Title
Safe >
App Engine is a platform-centric solution
Type of PaaS
No need to buy, build, or operate
hardware/infrastructure
No managing servers or
configuring deployments
Focus on app development instead
of operations

Use a range of languages and tools

Automatic scaling
App Engine offers two different environments

Standard environment Flexible environment

Fully-managed Docker container support
Scale to zero VMs exposed
Specific versions of supported Any language in your container
languages More options for infrastructure
Changes/configuration limited customization and configuration
for performance

https://cloud.google.com/appengine/docs/the-appengine-environments
https://medium.com/@venkat86.careers/how-to-choose-app-
engine-environment-standard-flexible-9f4c26a723b0
App Engine addresses the key needs of developers

Multiple storage options Automatic scaling Load balancing

V1.1

V1.2
V1.3

App versioning Monitoring and logging Security

Where Cloud Functions fits within GCP

Google
Compute Engine App Engine Cloud Functions Kubernetes
Engine
IaaS PaaS Serverless logic Hybrid

Virtual machines with A flexible, zero ops A lightweight fully Cluster manager and
industry-leading platform for building highly managed serverless orchestration engine built
price/performance available apps execution environment for on Google’s container
building and connecting experience
cloud services

https://cloud.google.com/functions/#overview
The components that make Cloud Functions work

Connect and Events and Serverless

extend cloud triggers
services
How Cloud Functions works

Emit events
Invokes other
services

Writes back
Cloud services Cloud Functions Other APIs

Responds to events
• The simplest way to run your code
• Cloud Functions is Google Cloud’s event-driven serverless compute
platform.
• Run your code locally or in the cloud without having to provision
servers. Go from code to deploy with continuous delivery and
monitoring tools.
• Cloud Functions scales up or down, so you pay only for compute
resources you use.
• Easily create end-to-end complex development scenarios by
connecting with existing Google Cloud or third-party services.

https://cloud.google.com/functions/#overview
✓No servers to provision, manage, or upgrade
✓Automatically scale based on the load
✓Simplify complex application development across different
languages
✓Integrated monitoring, logging, and distributed tracing
✓Built-in security at role and per function level based on the
principle of least privilege
✓Key networking capabilities for hybrid and multi-cloud scenarios
Key features
• Simplified developer experience and increased developer velocity.
• Pay only for what you use
• Avoid lock-in with open technology
• Scales automatically
• No server management
• Runs code in response to events
IaaS to PaaS comparison

Compute Engine Google Kubernetes App Engine

Engine

IaaS PaaS

Servers, networking, storage Preset run-times, managed

services
Pay for what you allocate Pay for what you use
Where GKE fits within GCP

Google
Compute Engine App Engine Cloud Functions Kubernetes
Engine
IaaS PaaS Serverless logic Hybrid

Virtual machines with A flexible, zero ops A lightweight fully Cluster manager and
industry-leading platform for building highly managed serverless orchestration engine built
price/performance available apps execution environment for on Google’s container
building and connecting experience
cloud services
IaaS virtualizes the hardware
App App App

Libs Libs Libs

VMs OS OS OS

Hypervisor

Hardware
Virtualizing the hardware costs time and resources
App App App App App

Lib Lib Lib Lib Lib

OS OS OS OS OS

Hypervisor Hypervisor

Hardware Hardware
Using PaaS provides hosted services and an
environment that can scale workloads independently

Billing Orders Inventory

Write code in self-contained
workloads and include any libraries. Part1 Part2 Part3

Libs Libs Libs

Decouple code easily.

Services
Data | Cache | Storage | DB | Network
The platform scales to meet demand

Build your apps as decoupled P1 P2 P3

microservices.

You may not be able to fine-tune the

X underlying architecture to save cost.
Services
Data | Cache | Storage | DB | Network
Leveraging containers offer the IaaS flexibility with
PaaS scalability

App App App containers

Libs Libs Libs

OS / Hardware
implements
container
interfaces
Using a common host configuration, you can deploy
hundreds of containers on a group of servers

MS2
MS1 MS3

Host1 Host2 Host3

Host4 Host5 Host6
Kubernetes makes it easy to orchestrate many
containers on many hosts

MS2
MS1 MS3

An open-source container
management platform
The relationship between containers, Docker,
and Kubernetes
GKE is a managed environment for deploying
containerized apps
Agenda (2/2)

Event Driven Programs with Cloud

Functions

Lab: Cloud Functions: Qwik Start -

Command Line

Containerizing and Orchestrating

Apps with GKE

Quiz

Summary
Quiz

Which of the following would be considered IaaS?

A. Compute Engine
B. Google Kubernetes Engine
C. App Engine
D. Cloud Functions
Quiz

Which of the following would be considered IaaS?

A. Compute Engine
B. Google Kubernetes Engine
C. App Engine
D. Cloud Functions
Quiz

Which of the following two services can take advantage of containers

to run your applications?

A. Compute Engine
B. Google Kubernetes Engine
C. App Engine
D. Cloud Functions
Quiz

Which of the following two services can take advantage of containers

to run your applications?

A. Compute Engine
B. Google Kubernetes Engine
C. App Engine
D. Cloud Functions
Quiz

Which of the following is considered to be serverless?

A. Compute Engine
B. Google Kubernetes Engine
C. App Engine
D. Cloud Functions
Quiz

Which of the following is considered to be serverless?

A. Compute Engine
B. Google Kubernetes Engine
C. App Engine
D. Cloud Functions