Gcpforawscourseonpearsonrev11541985173886 PDF

GCP
for AWS Course

Click to edit Master title style
GCP for AWS Professionals

- Get to Know GCP with comparisons
to AWS Services and experience
- Revised 11/09/2018
GCP For AWS Course Overview
CLASS IS 4.5 HOURS
Segment 1: Why Google Cloud Platform, Network Infrastructure,

Accounts and Billing (90 minutes)
Break: 10 Minutes
Segment 2: Virtual Networking, Compute Options, Data Storage
Services (90 minutes)
Break 10 Minutes
Segment 3: Database Options, Emerging Technologies, Load Balancing
and Scaling, Monitoring and Certifications (90 minutes)
GCP For AWS Professionals
What you'll learn-and how you can apply it
• GCP Platform Overview

• Why Use GCP
• Comparing GCP to AWS Services
• Cloud Console and CLI Demos
• GCP Services/Solutions Discussions
• Designing a GCP Cloud Service
• GCP Positioning
• GCP Cloud Certifications
Expectations
• This course was designed for IT Professionals who have a

foundation in AWS Services and Solutions.
• 6 Months of AWS. No detailed discussions on AWS
services
• We will cover GCP Solutions and directly compare to
AWS.
• You be pointed to additional resources to leverage
• This course should be considered a stepping stone to
learn more about GCP
Course covers main Cloud features.
• Networking
• Compute
• Storage
• Data Services
Lets Find out More about the Audience

Survey Question
Who currently is or is planning on using GCP services in

their enterprise environments?
• Yes, we are using GCP Services

• No plans to at this time
• Will be in 3 Months
• Will be in 6 Months or more
Survey Question
What Services are you using in your production environment?
• Cloud Storage
• Cloud SQL
• App Engine
• Compute Engine
• BigQuery
• Bigtable
• Cloud ML
• Stackdriver
• Other GCP Services
Survey Question
What Services are you using in your Dev/Test environments?
• Cloud Storage
• Cloud SQL
• App Engine
• Compute Engine
• BigQuery
• Bigtable
• Cloud ML
• Tensorflow
• Other GCP Services
Survey Question
What Cloud Providers are you currently using for your
cloud IaaS/PaaS services in your enterprise?
• AWS
• GCP
• Bluemix
• Azure
• Rackspace
• Cloud Foundry
• Other Cloud Services
Survey Question
What vendor Cloud Computing Certifications do you hold?
• AWS
• GCP
• Azure
• IBM
• Cloud Foundry
• VMware/EMC/Dell
• Cisco
• Others Not Listed
Survey Question
In my current role my job role and duties are similar to
what role?
• Cloud Engineer
• Cloud Developer
• Cloud Architect
• Data Engineering/Big Data Architect
• GSuite Administrator
• Enterprise Architect
• Application Admin
• Other role not listed
Survey Question
What is the industry/vertical your working in?
• Consulting/VAR/Vendor or Integrators
• Financials (Banking/Insurance/Investments)
• Manufacturing
• Government
• Telcom/Internet/Social Media
• Healthcare and Pharma
• Retail/Online Commerce
• Education
• Others not listed
Survey Question
What Google Cloud Certifications are of interest to you?

(Select All)
• Cloud Architect
• Data Engineer
• Associate Cloud Engineer
• GSuite Certifications
Lets Get Started

Why GCP
• Google Cloud Platform enables developers to build, test and

deploy applications on Google’s highly-scalable, secure, and
reliable infrastructure.
• Choose from computing, storage, big data/machine learning,

and application services for your web, mobile, analytics, and
backend solutions.
Why GCP
• Google has the most powerful infrastructure and owns most

of it.
• Datacenters
• Fiber Backbones https://peering.google.com/#/
• Submarine lines
• Points of Presence
Why GCP
• Sub Minute Billing

• Sustained Used Discounts
• Automatically reward users who run virtual machines for
over 25% of any calendar month Compute Engine Custom
machines types
• Pay only for the resources you need for your application
WHY GCP
• Google provides interoperability at multiple layers of the

stack.
• Kubernetes Engine give customers the ability to mix and
match microservices running across different clouds
• Leverage multiple providers .
• Open API’s
Why GCP?
Your choice managed or

unmanaged services.
1. Flexibility
2. Cost effective
3. High performance
• Rock Solid Infrastructure
• Top Tier Data Analytics
• Serverless leadership
• Innovative Pricing https://cloud.google.com/
• Security @ Scale
• Superior Machine Learning
and Automated Intelligence
Services
• Google Cloud Platform enables
developers to build, test and deploy
applications on Google’s highly-
scalable, secure, and reliable
infrastructure.
• Choose from computing, storage, big
data/machine learning, and
application services for your web,
mobile, analytics, and backend
solutions.
• Regions are independent geographic areas that consist
of zones.
• Locations within regions tend to have round-trip
network latencies of under 5ms on the 95th percentile.
• Zones are a deployment area for Cloud Platform
resources within a region.
• Zones should be considered a single failure domain
within a region.
AWS GCP
Regions Global Infrastructure Regions and Zones
Abstracted data Availability Zone Zone
center
Edge caching CloudFront Cloud CDN(App
Engine, Cloud
Storage)
WHY GCP
GCP Has a growing number of zones and regions.
https://cloud.google.com/compute/docs/regions-zones/
WHY GCP
GCP Has an ever expanding infrastructure.
For more information on Google’s Edge Network, see:

https://peering.google.com/#/.
Regions and Zones
Regions and Zones
• Zones have high-bandwidth, low-

latency network connections to other
zones in the same region.
• Note that there could be bandwidth

costs between regions and zones.
• Google recommends deploying

applications across multiple zones and
multiple regions. MZ + MR
AWS Global Infrastructure
Lets Look at AWS…..
https://aws.amazon.com/about-aws/global-infrastructure/
Lets Compare Terms and numbers
AWS GCP
Backbones - - Different View
Datacenters region and region and zone
availability zone (AZ)
Edge Locations CloudFront (75+) Cloud CDN and Cloud
Interconnect (110+)
AWS Global Infrastructure
Concept AWS GCP Notes
Lets Compare Terms and numbers
Cluster of DC Region (18) Region (17) GovCloud in
Services progress with
GCP….
Abstracted DC Availability Zone Zone(44) * Does not include
(53) locales that are
not online
Edge Caching POP (Cloudfront) POP(CDN, Other Cloud Platform's POPs

connect to data centers
Services) through Google-owned
fiber.
Total Services 200 + 50+

POPS and Cloud
• POPS form the edge of this network and are unique amongst cloud
vendors.
• You connect to the Google edge location closest to you, then Google
routes your packets over its backbone to datacenters.
• Big cost savings could be approached.
• GCP uses POPs to provide Cloud CDN and to deliver built-in edge
caching for services such as Google App Engine and Google Cloud
Storage.
• AWS uses POPs to provide a content delivery network (CDN) service,
Amazon CloudFront.
Compare Global Infrastructure
AWS has 18 Regions & 53 Lets Compare
Availability Zones
• N. Virginia (6) • Asia Pacific Central (2)

• Ohio (3) • Beijing (2) China
• N. California (3) • Frankfurt (3)
• Oregon (3) • Ireland (3)
• Mumbai (2) • London (2)
• Seoul (2) • São Paulo (3)
• Singapore (2) • AWS GovCloud (US-West)
• Sydney (3)
• Tokyo (3)
https://aws.amazon.com/about-aws/global-infrastructure/
Compare Global Infrastructure
GCP has 17 regions & 52 zones Lets Compare
•Council Bluffs, Iowa, USA (us-central1) •Finland - New
•St. Ghislain, Belgium (europe-west1) •Frankfurt, Germany
•Changhua County, Taiwan (asia-east1) (europe-west3)
•Sydney, Australia (australia-southeast1) •Jurong West, Singapore
•The Dalles, Oregon, USA (us-west1) (asia-southeast1)
•Ashburn, Virginia, USA (us-east4) •Tokyo, Japan (asia-
•Moncks Corner, SC, USA (us-east1) northeast1)
•São Paulo, Brazil (southamerica-east1) •Mumbai, India (asia-south1)
•London, UK (europe-west2) •Montréal (northamerica-
•Frankfurt, Germany (europe-west3) northeast1)
•Jurong West, Singapore (asia-southeast1) •Netherlands (europe-west4)
https://cloud.google.com/about/locations/
Hierarchy in Google Cloud Platform

GCP accounts can be associated to a G Suite domain or Gmail
user account.
• This is useful since it can follow a lifecycle with Gmail. If
you delete the user, all billing accounts, projects and
resources are deleted. (Follow the user)
• With GSuite this works different. Billing accounts,
projects, and resources follow the company life cycle.
(Follow the company organization)
GCP accounts can be associated to a G Suite domain or Gmail
user account.
• IN AWS ---- you can also allow users outside your
organization to access resources.
• In GCP --- All you do is add a Google user or group to your
organization, folder, or project and they get access to
everything under it.
• Concept of G Suite super admins ---- add themselves and
others as Organization Admins
Projects and Hierarchy
GCP Has the following
Hierarchy.
• Organizations
• Folders
• Projects
• Resources
• Folders (Cloud IAM)
• The Cloud IAM Folders feature
lets you assign policies to
resources at a level of granularity
you choose.
• The resources in a folder can
share IAM policies
• Google Cloud IAM is comparable

to AWS Directory Service.
• An Organization resource is available for G Suite and Cloud Identity

customers.
• Link your org domain to GCP.
• Think of an Organization as a hierarchy.
• Set access control and configuration settings at the organization or
project level
• Billing accounts, projects, and resources are not deleted when an
employee leaves the company. Follows corporate lifecycle.
AWS and GCP Accounts
Organizational Units (OUs)
• AWS Requires an account and GCP also requires you to signup for
a Google account.
• In AWS you create an Organization OU account and then you can
create subaccounts for organizations. (Billing)
• In Google you create your account and then provision resources
from projects.
• Projects have three main

identifiers
• Project Name
• Project ID
• Project number
https://cloud.google.com/resource-manager/docs/creating-managing-
projects
Use a project to:

• Track resource and quota usage.
• Enable billing.
• Manage permissions and
credentials.
• Enable services and APIs
Concept AWS GCP
Billing Accounts One Many per account
Billing Structure Sub Accounts Projects
Admin Roles IAM User, Groups and Google user or Groups
Roles
Account Admins Root Gmail or Gsuite
- In GCP all you have to do to allow an outside user is to add their Gmail or Gsuite user
account to a project
- Add a Gsuite domain as a user and create what is really an admin domain.
- The organization is linked to your G Suite domain.
- All billing accounts, projects, and resources created by domain members belong to the
organization instead of users who create them.
Pricing Calculators
Both AWS and GCP have

pricing calculators.
• Straight forward.
• AWS pricing calculator is
more useful for pricing
overall.
GCP Services Overview – Virtual Networking

2.

• Network Latency is a big
deal. It could MS or
Seconds in difference.
• Use Latency Check from

Cloudharmony
• GCPING
• Cloudping.info
2.

• Network Investments by GCP
are impressive
• Google Network speed up to

10Tbps of the cable’s total
60Tbps bandwidth. JPN –
USA
• Over Googles private network

and not the internet!!!
2.

Google launched the first of any
cloud providers network tier
service.
• Standard Tier - It delivers

outbound traffic from GCP to
the internet over transit (ISP)
networks
• Premium Tier - served over

Googles low latency and
reliable network. (N+2)
2.

• Lets Compare Networking Solutions
Solutions GCP AWS
VPC VPC VPC
DNS Cloud DNS Route 53
CDN Cloud CDN CloudFront
Interconnect Cloud Interconnect Direct Connect
Load Balancing Cloud Load Balancing Elastic Load Balancing
Tiering Network Service Tier N/A
2.

• A Virtual Private Cloud
(VPC) is a GLOBAL
private isolated virtual
network partition that
provides managed
networking functionality
for your Google Cloud
Platform (GCP)
resources
2.

GCP Virtual Private Cloud
• Global Communications Space

• Compute or GCP Services
• Shared VPC
• Hybrid Support
• Private Peering
• Two Types (Auto & Custom)
2.

GCP Virtual Private Cloud
• Global Communications Space

• Thru the Google backbone directly.. (This is a big differentiator
from AWS)
2.

Cloud Scale Services and Comparing to AWS VM Networking
• GCP offers global networks

• GCP offers regional subnetting
• GCP offers a default internet gateway which does not require
peering.
• GCP VMS in Compute Engine are more global.
• AWS VMS in EC2 are more isolated.
2.

Cloud Interconnect
• GCP has a interconnect (AWS Directconnect) called Cloud

Interconnect to extend your data center network into your
Google Cloud projects.
• IPSec VPN
• Direct access to RFC1918 IPs in your VPC (SLA)
• Partner Interconnect
2.

Cloud Peering
• GCP supports peering. Peering is the direct

interconnection between Google's network and
another network to support the exchange of traffic.
• Access to Google public IPs only – without SLA
• Direct Peering
• Carrier Peering
• Meet Requirements
https://peering.google.com/#/options/peering
2.
Compute Options
Lets Compare Compute Services
AWS GCP
IaaS Compute EC2 Compute Engine
PaaS App Delivery App Engine Elastic Beanstalk
SaaS Functions Lambda Cloud Functions
Containers Container Service Kubenetes Engine
AWS GCP
Configurations Instance Types Machine Types
SSH Keys Include your keys Instance and project wide
Public Images Yes Yes
Marketplace AWS Marketplace Cloud Marketplace
Import/Export VM import/export Import RAW Images import more

RAW/OVA/VMDK/VVHD manual
Image Storage EBS/S3 Project/export to GCS
Max Config 128 vCPUs & 3,904 GB RAM. 160 vCPUs & 3,844 GB RAM
AWS GCP
Predefined Images Not as flexible (AMI) Yes, on demand
customization of
RAM/CPU/GPU
Block Storage Elastic Block Store Persistent -
HDD/SSD Standard/SSD
Local SSD EC2 Ephemeral Local SSD
Virtualization Xen KVM
Compute Engine– These VMS are focused on your enterprise IaaS
services.
Cloud Functions -is geared towards a serverless approach and
focused on microservices
App Engine - is focused on PaaS and can be delivered in two different
solutions (Standard or Flexible)
Kubentetes Engine - Awesome solution for developers wanting a
simple and lightweight container.
Note! A Compute Engine instances can run Linux and Windows

Server
Virtual Machines - Compute Engine
IaaS – Infrastructure as a Service (AWS its called EC2)
• Can be predefined (templates or custom)

• Cloud Launcher(Market Place)
• vCPU and Memory
• Networking
• OS (Linux or Window)
• Inferred instances- for billing purposes, the same type of
machine used in the same zone will be combined into a
single charge (Increase your discounts)
• Google does discounts their resources steeply
Billed for minimum of 1 minute and thereafter every second.
• Lower price for a PREMPTIVE instances..
• Longer term use also discounted.
• Custom-type is discounted on a percent of total use
Storage on VMS
Standard, SSD (Can Scale PDs) or local SSD

Can resize disks and migrate with no downtime
https://cloud.google.com/compute/docs/disks/performance
Networking in VMS
Networking Features
• Default and Custom Networks
• Inbound/Outbound Firewalls
• Regional load balancing and Network Load
balancing
• Global and multiregional Subnetworks
Global, regional, and zonal resources
• Global resources include preconfigured

disk images, disk snapshots and networks.
• Regional resources include static external
IP addresses.
• Zonal resources include VM instances,
their types, and disks.
VMS
Supported Protocols
• TCP
• UDP
• ICMP
Note – Supports Ipv4 only
Every VM Instances belongs to a network.
2.

Auto restart refers to what behavior the VM should take after a
hardware failure or a system event.
• If marked auto restart, the system will try to launch a

replacement VM.
• Auto restart does not restart the VM if it was terminated due to
a user event, such as shutting down and terminating the VM.
NOTE: If the VM availability policy is set to the default, live

migrate, during regular system maintenance your VM will be
migrated to different hardware so there is no downtime
2.

Creating VMS Instance Groups
• A managed instance group uses an instance template to create or

update the instances that are part of the group.
• Create an instance template once & can reuse it for multiple groups
and configuration.
• An instance template is a global resource that is not bound to a zone
or a region.
• You can still specify some zonal resources in an instance template,
which restricts the template to the zone,
• By default, instances in the group will be placed in the Default and
randomly assign IPs from the Regional Range
2.

A managed instance group use for
• Autoscaling
• Load balancing
• Updates
Two Types of Managed Instance Groups.

• Zonal Managed Instance Group
• Regional Managed Instance Group (Recommended)
https://cloud.google.com/compute/docs/instance-groups/
Creating VMS Instance Groups
• Unmanaged instance groups are groups of dissimilar instances that

you can arbitrarily add/remove from the group.
• Unmanaged instance groups DO NOT offer autoscaling, rolling
update support, or the use of instance templates.
• Google recommends creating managed instance groups whenever
possible.
• Use unmanaged instance groups only if you need to apply load
balancing to your pre-existing configurations or to groups of
dissimilar instances.
2.

Images in Compute Engine
• Public base
Google, 3rd party vendors, and community; Premium images
• Private and custom images

Create new image from VM - pre-configured & installed SW
Import from on-prem, workstation, or another cloud
Management features: image sharing, image family,
deprecation
• Virtualbox or AWS
2.

Disk Options in Compute Engine
• Compute Engine VM comes with a single root persistent disk
Image is loaded onto root disk during boot process
• Bootable - you can attach to a VM and boot from it
• Snapshots - incremental backups
• Durable -- can survive VM terminate
• Some SW is installed and OS is configured by GCE
• Each persistent disk can be up to 64 TB in size
• Each instance can attach only a limited amount of total
persistent disk space and a limited number of individual
persistent disks.
2.

Disk Options in Compute Engine
• Each Compute Engine instance has a single root persistent disk that
contains the operating system.
• Add one or more additional storage options to your instance.
• Scope of access – Local, Zonal or Global
• Max Sustained IOPS. Review
• A single file system gives the best performance on Persistent disk
• Local SSDs = High IOPS and low latency.
• Review options here
https://cloud.google.com/compute/docs/disks/
2.

Moving VMS
Two ways to do this usually to support availability
1. Manual
2. Automatic
• Don't use on a VM with a local SSD. The local SSD data

cannot be backed up and will just be discarded.
• Persistent disks have to be attached to only the VM you are
going to move. (Multiple not supported)
• Sufficient quota must exist for all the resources copied
during duplication, or the process will fail.
2.

Snapshots VMS
• Snapshot is not available for local SSD

• Creates an incremental backup to GCS
• Snapshots can be restored to a new persistent disk
• Don't use for database migration across zones
• Cant be shared among projects
• https://cloud.google.com/compute/docs/disks/create-snapshots
GCP Cloud Engineer Overview
Virtual Machines Billing

Per-second billing, sustained use discounts
1 minute minimum and 1 sec increments
Preemptible instances
Live at most 24 hours
Can be pre-empted with a 30 second notification via API
Discounted significantly
Custom machine types
https://cloud.google.com/custom-machine-types/
Customize amount of memory and CPU
Built in Recommendation Engine
https://cloud.google.com/compute/docs/instances/preemptible
Notifies you of under utilized instances
Recommendation Engine
Compute Engine provides machine type recommendations to help
you optimize the resource utilization of your virtual machine
instances.
• These recommendations are generated automatically based on

system metrics gathered by the Google Stackdriver Monitoring
service over the previous 8 days.
• This feature is also known as Rightsizing Recommendations.

Recommendation Engine
Billing and Pricing VMS.. Lets Compare
AWS GCP
Per Second Yes Yes
Discounts (Instances) Spot (Regular/Block) Preemptable (24 hrs)
Discounts Reserved Committed Use
Savings Prepay and discount Up to 80% and no
Prepaid contract
GCP Cloud Engineer Overview
2.
APP ENGINE
2.

App Engine
Cloud Client Libraries
• Go, Java, Python, Node.js, PHP, Ruby, C#
Installation Process
• Download: https://cloud.google.com/sdk/downloads
• Extract file
• Setup paths/reporting: ./google-cloud-sdk/install.sh (or .bat)
• Initialize the SDK: gcloud init
• Authorization
gcloud auth activate-service-account --key-file [KEY_FILE]
2.

App Engine PaaS
• Fully Managed, just worry about your code.

• Hosted on Googles infrastructure and networks
• Supports source code that is written in a version of any of the
supported programming languages:
Python, Java, Node.js, Go, Ruby, PHP, or .NET
• Standard or Flexible Environments
• SDK Kits (Develop locally)
• https://cloud.google.com/appengine/
2.

App Engine PaaS
• App Engine is regional, which means the infrastructure that

runs your apps is located in a specific region and is managed
by Google to be redundantly available across all zones in that
region.
• You cannot change an app's region after you set it.
• Free and Paid resources available.
• Supports Spring Framework
• Supports MemCache
• Support and SLA
2.

App Engine PaaS Standard Environment
•Python 2.7, Python 3.7 (beta)
•Java 8, Java 7
•Node.js 8 (beta)
•PHP 5.5, PHP 7.2 (beta)
•Go 1.6, 1.8, 1.9, and Go 1.11 (beta)
App Engine PaaS Flexible Environment

• Supported Languages are Not Specific
• Python, Java, Node.js, Go, Ruby, PHP, or .NET
2.
Kubenetes Engine
2.

Kubernetes Engine
Containers are
• Virtualization at OS Layer
• Separates operating system from app code and
dependencies
• Isolates individual processes
• Docker and Kubernetes
2.

Container Engine (Kubernetes Engine)
• Kubernetes Engine is a managed environment for deploying

containerized applications
• Fast Efficient Docker format container deployment and portability
• Kubernetes Engine only supports the use of Docker containers for
workloads
• Kubernetes Engine and Kubernetes, these containers run workloads
• Before you deploy a workload on a KE cluster, package the workload
into a container.
https://cloud.google.com/kubernetes-
engine/docs/concepts/kubernetes-engine-overview
2.

CD Pipeline
2.

CD Pipeline
Google Cloud
2.

Why use?
Workload portability
•Run in many environments, across cloud providers
•Implementation is open and modular
Rolling updates
•Upgrade application with zero downtime
Autoscaling
•Automatically adapt to changes in workload
2.

• One purpose of GKE is to enable you to manage applications, not
machines.
To accomplish this, you need to understand the GKE abstractions for
applications.
• Any data access mounted to a pod, called a Volume, is available to
all containers in the pod.
• Containers that are part of the same pod are guaranteed to be
scheduled together on the same VM and can share state via local
volumes.
Note---Persistent Volumes, using persistent disks in GCE, survive
instance and container restarts.
2.

Pools
Instance groups in the Kubernetes cluster
• All VMs in a pool are the same
• Pools can contain different VMs from one another
• Pools can be in different zones GKE is node pool-aware
• Labels on VMs in the pool make them available to GKE
• Node Pools and Multi-zone Container Clusters
• GKE will replicate all the pools along with all the clusters
Careful! It could use up quotas in the region
2.
• So What do I choose. App Engine or Kubenetes Engine?
Kubenetes Engine App Engine Std App Engine Flex

Language Any Java, Python, Go, Any
PHP, Node.js
Service Model Hybrid PaaS PaaS
Use Case Containers Web & Mobile Web and Mobile

container based.
2.
Cloud Functions
2.

Cloud Functions -Event-based microservices
• Fully managed, serverless, secure

• Triggers - Cloud Pub/Sub, HTTP, Cloud Storage
• Code Deploy functions from a Cloud Storage bucket, Github
or Bitbucket repository
• Written in Javascript and runs in Node.js
• Stackdriver integration
• Cloud Functions come in two distinct variants: foreground
(HTTP) and background
• https://cloud.google.com/functions/
Cloud Functions
•Cloud Functions is used for responding to events.
• Event-driven serverless compute platform
• Simple way to run code
• Similar to Lambda in AWS
AWS GCP
IaaS Compute EC2 Compute Engine
PaaS App Delivery App Engine Elastic Beanstalk
SaaS Functions Lambda Cloud Functions
Containers Container Service Kubenetes Engine
2.
Data Storage and Services

2.

GCP Storage
• Choose a Storage Option

https://cloud.google.com/storage-options/
• Cloud Storage
• Cloud BigTable
• Cloud SQL
• Cloud Spanner
• Cloud Datastore
• Persistent Disk
2.

GCP Object Storage To AWS Object Storage
AWS GCP
Units Bucket Bucket
ID Globally Unique Key Globally Unique Key
Deployment Regional Regional and
Multiregional
Notifications Events Pub/Sub, Cloud
Functions, OCN
Object Metadata, Yes Yes
Versioning and
Lifecycles
2.

GCP Storage
• First is to understand do you need Structured or

Unstructured
• Second, consider the availability and compliance
requirements
• Third, consider costing models
• Fourth, consider performance requirements (Latency)
• Fifth, determine migration requirements
2.

GCP Storage Choices
Structure Data Services Unstructured Data Services

Cloud SQL Cloud Storage (Blob)
Cloud BigTable Cloud Filestore (NAS)
Cloud BigQuery (Warehouse)
Cloud Datastore
Cloud Spanner
2.

GCP Storage
Cloud
Cloud Storage Datastore Cloud SQL Bigtable
NoSQL,
Storage Type Object Store document Relational SQL NoSQL, wide Column
Capacity Petabytes Terabytes up to 500GB Petabytes
Unit Size 5TB per object 1MB/Entity MySQL Limits 10MB Cell/100MB row
Transactions No Yes Yes No
Complex Queries No No Yes No
Strcutured or Web Flat Data, events,
Good For Unstructured App Engine apps Frameworks analytics
Images, media,
Use Case backups User profiles User Credentials Adtech
Catalogs Customer Orders Financial
IoT
2.

Data Storage - Unstructured data
• Unstructured data is data that does not have a pre

determined sequence, data model or schema.
• Can be human generated or machine generated
• Examples are Email, documents, social media, mobile,
sensor data, satellite images, etc
• On GCP Cloud Storage is the only service built for managing
and maintaining you Unstructured Data
2.

Data Storage - Structured data
• Structured data is data that
does have a pre determined
sequence, data model or
schema. Generally a database
(RDBMS)
• Can be human generated or
machine generated
• Examples are SQL.
2.

Data Storage - Semi-Structured data
• Semi-Structured data is data that
contains semantic tags, but does
not conform to the structure
associated with typical relational
databases.
• Can be human generated or
machine generated
• Examples are XML, JSON and
NoSQL
2.

Need Help trying to pick what service?
2.

• Google Cloud Storage is unified object storage for
developers and enterprises, from live data serving to data
analytics/ML to data archiving.
• High performance, internet-scale, immutable BLOB (binary
large object) storage
• Simple Abstraction Storage buckets, immutable objects with
mutable metadata and Globally unique URI identifiers for
buckets, objects
• Common storage for Google Cloud Platform services
2.

Cloud Storage is Not a file system. Though Cloud Storage is not a
file system, it can be accessed as one using third party tools
such as Cloud Storage Fuse.
• Simple administration and does not require capacity
management
• Accessed through REST APIs
- Client libraries
- REST APIs
- gsutil (CLI)
2.

Cloud
• Supports Online or offline imports
• All storage classes accessed through the same APIs
• Simple pricing model
- Network ingress, and data transfer within a region is free
- Network egress charges apply and vary by destination
2.

Cloud Storage Terminology
• All data in Cloud Storage belongs inside a project.

• A project consists of a set of users, a set of APIs, and billing,
authentication, and monitoring settings for those APIs.
• Buckets are the basic containers that hold your data.
Everything that you store in Cloud Storage must be
contained in a bucket.
• Objects are the individual pieces of data that you store in
Cloud Storage.
2.

Objects have two components:
object data and object metadata.
• Object data is typically a file that you want to store in Cloud

Storage.
• Object metadata is a collection of name-value pairs that
describe various object qualities.
2.
Cloud Storage Notes

• Cloud Storage uses a flat namespace to store objects.
• There is only one Cloud Storage namespace, which means
every bucket must have a unique name across the entire
Cloud Storage namespace.
• Object names must be unique only within a given bucket.
2.

More Notes on Cloud Storage
• Google Cloud Storage offers four storage classes.
• Customers can associate each of their buckets with the
storage class most appropriate for their use cases.
• All of the storage classes are accessed in using the Cloud
Storage API, and all offer millisecond access times.
• All storage classes incur a cost per gigabyte of data stored
per month, and egress and data transfer charges may apply.
• In addition to those charges, Nearline storage also incurs an
access fee per gigabyte of data read, and Coldline storage
incurs a higher fee per gigabyte (reads)
2.

Google Cloud Storage has four specific classes that you should
be aware since this will affect durability and costing
significantly.
• Multi-Regional
• Regional
• Nearline
• Coldline
• https://cloud.google.com/storage/docs/storage-classes
2.

Objects
Supports object control features

• Object Versioning
• Object Lifecycle Management
• Object Change Notification
• Imports
https://cloud.google.com/storage/docs/object-versioning
2.

Object Lifecycle Management
• Object Lifecycle management policies specify actions to be
performed on objects that meet certain rules sets.
• Changes to configurations can take 24 hours to apply
• Object inspection occurs asynchronous batches
2.

Object Change Notification
• Uses Webhooks
• Object change notification watches a bucket and send
notifications to external applications when objects change
https://cloud.google.com/storage/docs/object-change-notification
2.

Import
• Imports allow you to use The Cloud Storage Transfer service
enables high-performance imports of online data into Cloud
Storage buckets
• Offline Media Import is a service where physical media is
sent to a 3rd-party provider who uploads the data
Availability and Third Party Service Providers

https://cloud.google.com/storage/docs/offline-media-import-
export
2.

Object Data Storage Lets Compare
AWS GCP
Services S3 Cloud Storage
Hot S3 Standard GCS
Chilled S3 Standard (IA) GCS Nearline
Cold (Archive) Glacier GCS Coldline
Object Size 5TB 5TB
Backups/Archival Glacier NA
2.

Block and File Data Storage Lets Compare
AWS GCP
Block Storage EBS Persistent Disk
Disk/Volume Size 1GB-16GB Provisioned 1GB -64GB
SSD 4GB-16GB
Types EBS Provisioned IOPS Zonal standard

SSD, EBS General persistent disks (HDD),
Purpose SSD, regional persistent disks,
Throughput Optimized zonal SSD persistent
HDD, Cold HDD disks, regional SSD
persistent disks
2.

Block and File Data Storage Lets Compare
AWS GCP
Throughput (Volume) 800 read, 400 write 160 (320 for
(MB/s) Provisioned IOPS)
Replication RAID-1 Built in platform
Max IOPS 10,000 (20,000 for 40,000 read, 30,000
Provisioned IOPS) write
Max IOPS of
75,000/instance
2.
Cloud SQL
2.

Cloud SQL is a fully-managed MySQL and PostgreSQL database
service.
• Fully managed instances
• Patches and updates automatically applied
• You still have to administer MySQL users
• Cloud SQL supports many clients
2.

Cloud SQL is a fully-managed
MySQL and PostgreSQL
database service.
• Pay per use model
• Rest API
• Affordable and high
performance
2.

Scaling Cloud SQL
• Adaptive Scaling
capabilities
• Vertical scaling (read and
write)
• Horizontal scaling (read)
• Seamless integration with
App Engine and Compute
Engine
2.

Robust features
• Supports IPv4 and IPv6
• Automated Backup and Recovery
• Availability Protection
• Partner Ecosystems
• Fully Managed
• Google Scale Security
• Automated backups occur on a daily basis during chosen
window.
• On-demand backups are also available via console, , or API
2.

SQL Features Supported
• Cloud SQL supports: Stored procedures, Triggers, and Views
• Cloud SQL does not support: User-defined functions,
Internal MySQL replication, statements and functions
related to files and plugins
• Go to this page for current supported and unsupported
capabilities
https://cloud.google.com/sql/docs/features
2.

Instances Supported
• Second Generation instances support MySQL 5.6 or 5.7, and
provide up to 208 GB of RAM and 10 TB data storage, with
the option to automatically increase the storage size as
needed.
• First Generation instances support MySQL 5.5 or 5.6, and
provide up to 16 GB of RAM and 500 GB data storage.
2.

Cloud SQL Proxy provides secure
access to your Cloud SQL Second
Generation instances without
having to:
1. Whitelisting
2. Configure SSL
Cloud SQL Proxy works by having a

local client, called the proxy,
running in the local environment.
2.
Cloud Spanner
2.

Cloud Spanner is the only
enterprise-grade, globally-
distributed, and strongly
consistent database service
built for the cloud specifically
to combine the benefits of
relational database structure
with non-relational horizontal
scale.
2.

Cloud Spanner Overview.
• Strong Consistency
• SQL Support
• Managed Service
• Strong global consistency
• Secure global transactions
• Horizontal scalability
• Managed by Googles SRE team
https://cloud.google.com/spanner/
• Cloud Spanner has regional and multi-region instance

configurations.
• Cloud Spanner database can contain one or more tables.
• Data in Cloud Spanner is strongly typed (Strong Schema)
2.

Cloud Spanner transaction modes:
• Locking read-write. This type of transaction is the only transaction

type that supports writing data into Cloud Spanner.
• Read-only. This transaction type provides guaranteed consistency

across several reads, but does not allow writes.
https://cloud.google.com/spanner/docs/transactions
2.
Cloud Datastore
2.

Cloud Datastore is a highly-scalable NoSQL database for your
applications. Cloud Datastore automatically handles sharding and
replication, providing you with a highly available and durable
database that scales automatically to handle your applications' load.
• Strong Consistency
• Global Scalability
• Managed Instances
• SQL Support ANSI 2011
2.
Cloud Datastore.
• Pay per use model
• Rest API
• Affordable and high performance
Schemaless
• JSON API, Java (JPA, JPO, Objectify),
Python (NDB), Ruby, Node.js
• Charges for storage and for
read/write operations
2.
Cloud Datastore Replication
• Multiple Locations
Multi-Regional
• Multi-Region redundancy, Higher Availability
Regional locations
• Lower write latency, Co-location with other resources
• Global Points of Presence - lower latency for the end user
2.

• Cloud Datastore Notes
• Google Cloud Datastore is a schemaless database, which allows
you to worry less about making changes to your underlying data
structure as your application evolves.
• Datastore provides a powerful query engine that allows you to

search for data across multiple properties and sort as needed.
2.
Cloud Bigquery
2.

• Cloud Bigtable Overview.
• Fully-managed NoSQL database
• Petabyte-scale with very low latency
• Seamless scalability for throughput
• Learns and adjusts to access patterns
• Cloud Bigtable utilizes a low-latency storage stack
• Redundant Autoscaling Storage
• Seamless Cluster Resizing
2.

• GCP Big Table
• Integrates easily with
popular Big Data tools like
Hadoop, as well as Google
Cloud Platform products like
Cloud Dataflow and Dataproc.
• Bigtable supports the open-

source, industry-standard
HBase API
2.

• Database Options – Lets Compare
AWS GCP
Relational RDS/Aurora Cloud SQL/Cloud
Spanner
NoSQL – (KV) DynamoDB Cloud Datastore
Cloud Bigtable
NoSQL SimpleDB Cloud Datastore
Analytics Redshift/Athena BigQuery
2.
DevOps
2.

DevOps and the Cloud
• DevOps is where any application starts.

• Agility to be able to try things out
quickly
• Minimize Incurring upfront costs or
facing delays while procuring hardware.
• Performance and Agility can reduce
time to market.
• GCP supports this superbly.
2.

DevOps and the Cloud
GCP AWS
Code Repository Cloud Repositories CodePipeline
Build Test Code Cloud Build CodeBuild
Automate Cloud Build CodeDeploy
Deployments
Unified CI/CD Kubenetes Code Star
Pipelines Engine/Container
Registry
2.

DevOps and GCP Cloud
• Cloud Build - Run your container image builds in a fast, consistent,

and reliable environment. Builds Docker container images for
deployment in various environments.
• Container Registry - manage Docker images, perform vulnerability
analysis, and decide who can access what with fine-grained access
control for pipelines.
• Cloud Repositories - Design, develop, and securely manage your
code. Fully featured, scalable, and private Git repository. Extend Git
workflow by connecting to other GCP tools.
2.

What is DevOps
• DevOps (development & operations) is an enterprise software

development phrase used to mean a type of agile relationship
between development and IT operations.
• The goal of DevOps is to change and improve the relationship by
advocating better communication and collaboration between these
two business units.
• Google just about wrote the book on this.
2.

Continuous Integration
Continuous integration (CI) is the

practice of merging all developer
working copies to a shared mainline
(Pipeline) several times a day.
Benefits are efficiency, reduce risk,
remove manual processes
2.

Continuous Delivery
• Continuous Delivery is the ability to

get changes of all types—including
new features, configuration changes,
bug fixes and experiments—into
production, or into the hands of
users, safely and quickly in
a sustainable way
• Benefits are lower risks release, faster
market time, high quality and lower
costs
2.

Continuous Deployments
• Continuous Deployments can be

thought of as an extension
of continuous integration, aiming at
minimizing lead time, the time elapsed
between development writing one
new line of code and this new code
being used by live users, in production
• Benefits are lower risks, reduce lead
time to market, quicker feedback and
better ROI
2.

In a Nutshell . (From Stackoverflow)
Continuous Integration basically just means that the developer's
working copies are synchronized with a shared mainline several times a
day.
Continuous Delivery is described as the logical evolution of continuous
integration: Always be able to put a product into production!
Continuous Deployment is described as the logical next step after
continuous delivery: Automatically deploy the product into production
whenever it passes QA!
• Puppet.com has a good comparison as well

2.

Developer Resources
Repositories provide full Git repositories on GCP

• App Engine and Compute Engine
• Each Project has a repository
• Includes a source editor.
2.

Developer Resources
Toolsets are
• Cloud Source Repositories
• App Engine
• Stackdriver (Debug and Trace)
• Cloud SDK
• Numerous other tools from
GCP and third parties
2.

Cloud Endpoints
• API Gateway
• NGINX based proxy
• Cloud Endpoints are used to create a web backend.
• Used for web and mobile clients
• Deploy with App Engine
• Tools and Library
2.

Cloud Endpoints Notes
• Oath 2.0 & Firebase NGINX-based proxy & distributed

architecture
• Access your App Engine Instances
- Datastore
- Cloud Storage
- Task Queues
• Reduces your development cycle
• Java and Python
2.

Cloud Endpoints Lets Compare
AWS GCP
API Gateway API Gateway Cloud Endpoints
User Interface Yes No, CLI
Specification REST OpenAPI, REST
2.
Load Balancing
2.

AWS and GCP approach load balancing very differently.
• AWS is manual service and is VPC bound

• GCP is a managed service and is global.
Lets discuss more in detail.
2.

Load Balancing services in GCP
• Types of Load Balancing

• Network Load Balancing
• HTTPS Load Balancing
• Cross-Region Load Balancing
• Content-based Load Balancing
• Cloud SSL Proxy
2.

Load Balancing Components has three main components.
• Global Networking- 100 plus POPs, 100,000 of miles of

fiber network and optimized traffic ingestion.
• Software Defined - SDN construct of it, includes the
global forwarding rules at the Google global front end
to the targeted proxy service.
• Url Maps - Traffic Distribution uses and or both Cross
Region or Content based mapping.
2.

Network Load Balancing in GCP is a Managed Service and
deployed globally.
• Network load balancing distributes incoming traffic across

multiple instances
- Supports non-HTTP(S) protocols (TCP/UDP)
- Can be used for HTTPS traffic when you want to terminate
connection on your instances (not at HTTPS load balancer)
• Supports autoscaling with managed instance groups
https://cloud.google.com/compute/docs/load-balancing/network/
2.
Network Load Balancing

• Forwarding rules consist of...
Name
Region
IP Address (regional, not global)
IP Protocol (TCP, UDP; AH, ESP, ICMP,
SCTP)
Ports
Target-pool or target-instance
2.

Network Load Balancing in GCP
• Target pools consist of...

Name
Description
Region
Instances (must all be in same region as target pool)
SessionAffinity (NONE, CLIENT_IP_PROT, CLIENT_IP)
BackupPool
FailoverRatio
Each URL is specified by a virtual IP and port in a global
forwarding rule.
2.
HTTP(S) Load Balancing
• HTTP(S) Load Balancing distributes HTTP(S) traffic among

instance groups based on proximity to user or URL or both
• Autoscalers can be attached to HTTP(S)load balancers
https://cloud.google.com/compute/docs/load-balancing/network/
2.

HTTP(S) Load Balancing
• HTTP(S) The following resources comprise a load balancer
Global Forwarding Rule
Target Proxy (w SSL certificate resource for HTTPS proxy)
URL map
Backend Service and Backends
Health Check
• The load balancer leverages additional resources
Global IP Address (ephemeral or static)
One or more Instance Groups
2.

Global Forwarding
• A global forwarding rule provides a single global IP address for an
application
• The rule routes traffic by IP address, port, and protocol to an HTTP or
HTTPS target proxy
• A global forwarding rule can only forward to a single port
• Global forwarding rules can only be used by an HTTP(S) load balancer
https://cloud.google.com/compute/docs/load-balancing/http/global-
forwarding-rules
2.

Target proxies route incoming HTTP(requests) based on URL maps and
backend service configurations
• HTTPS target proxy terminates client SSL session
• HTTPS target proxies require configured SSL certificate resources
https://cloud.google.com/compute/docs/load-balancing/http/target-
proxies
2.

Backend services
• A health check
• Session affinity settings
• One or more backends
A backend comprises
• An instance group (managed or unmanaged)
• A balancing mode (CPU utilization or Rate in request/second)
• A capacity scaler (ceiling % of CPU/Rate targets)
• A backend service may have up to 500 endpoints per zone
GCP Cloud Architect Overview
2.

• Connection draining delays the termination of an instance
until remaining connections are closed
- New connections to the instance are prevented
- Instance preserves existing sessions until they end OR a
designate timeout is reached (1 to 3600 seconds)
- Minimizes interruption for users
• Connection draining is triggered when an instance is
removed from an instance group
- Manual removal, resizing, autoscaling
https://cloud.google.com/compute/docs/load-balancing/enabling-
connection-draining
2.

Cloud SSL Proxy
• Cloud SSL proxy alt type of load balancing
- non-HTTP(S) traffic
- Performs global load balancing, routing clients to the closest
instance with capacity
• Cloud SSL proxy advantages
- Intelligent routing
- Reduced CPI load on instances
- Certificate management
- Security patching
2.

Cross Region Load Balancing
HTTP/HTTPS only
Cross-region using a single global IP address
Requests routed to the closest region
Automatically reroutes to next closest once capacity is reached
Eliminates need for DNS-based load balancing
2.

Content Based Load Balancing
HTTP/HTTPS only
Create multiple backend services to handle content types
Add path rules to backend services
- /video for video services
- /static for static content
Configure different instance types for different content types
2.

What type of load balancing?
• HTTP, HTTPS, TCP, and SSL load balancing
• Network Load Balancing
https://cloud.google.com/compute/docs/load-balancing/optimize-
app-latency
2.

Instance Groups
Manage Groups of VMs
Three Types
1. Unmanaged
2. Managed Instance Group (Zonal)
3. Managed Instance Group (Regional)
Unmanaged instance groups contain dissimilar instances and wont.

- Autoscaling
- Rolling updates
- Instance creation using instance templates
https://cloud.google.com/compute/docs/instance-groups/creating-
groups-of-managed-instances
2.

• Notes to know……
• Google Cloud SSL proxy terminates user SSL (TLS) connections at the
global load balancing layer, then balances the connections across
your instances via SSL or TCP.
• Cloud SSL proxy is intended for non-HTTP(S) traffic.
• For HTTP(S) traffic, HTTP(S) load balancing is recommended instead.
https://cloud.google.com/compute/docs/load-balancing/tcp-ssl/
2.

Lets Compare with AWS
• AWS uses instance-based load balancing . Itis deployed as processes

on the instances.
• Needs a warm up time during peak demands.
• Bound to a VPC and does not use a single global IP address.
• Route 53 to route to nearest load balancer
• Region Failure results in load balancer failure. Manual process to
resolve
2.

Lets Compare Terms
AWS GCP
Service Elastic Load Balancer Compute Engine
Network load Yes Yes
balancing
Static IP No Yes
Content No Yes
Cross Region No Yes
Scaling Pattern Linear Real Time
Locality Regional Global
2.
Autoscaling
2.

Autoscaling
• Part of the Compute Engine API
• Used to automatically scale number of instances in a managed
instance group based on workload
• Create one autoscaler per managed instance group
• Autoscalers can be used with zone-based managed instance groups
or regional managed instance groups
• Fast typically ~ 1 min windows
https://cloud.google.com/compute/docs/instance-groups/distributing-
instances-with-regional-instance-
groups#provisioning_your_autoscaler_configuration
2.

• Autoscaling
• When the Autoscaler scales down, it determines the number of
virtual machines it needs to shut down
• Before an instance is terminated validate remaining connections,
gracefully shut down any applications or application servers,
uploading logs, etc.
• Shutdown Scripts….
2.

• Autoscaling in AWS is the same essentially as GCP
• In AWS and GCP autoscaling uses a bunch of VMs behind a load

balancer with a policy and health check and then calls it an auto
scaling group
• VMs are targets
• Spin config – Warm up config in AWS (Instance Template in GCP)
• Both allow you to define instance machine type, disk image, zone,
and startup scripts.
2.

• Autoscaling in AWS is the same essentially as GCP
Big difference though in the following.
• GCP does not need step adjustments and is more streamlined

2.
Google Stackdriver
Hybrid Monitoring
AWS and GCP
2.

• Monitoring. Lets Compare
AWS GCP
Monitoring CloudWatch Stackdriver
Monitoring
Logging CloudTrail Stackdriver Logging
Notifications SNS/SQS Pub/Sub
Message Delivery Pull-based message Push/Pull
2.

• Stackdriver is a hybrid Monitoring, logging, and diagnostics
for applications on Cloud Platform and AWS.
• GCP Purchased Stackdriver and was rebranded to Google
Stackdriver.
• Stackdriver monitors the clouds service layers in a single SaaS
solutions.
• Native integration with Google Cloud data tools BigQuery,
Cloud Pub/Sub, Cloud Storage, Cloud Datalab, and out-of-
the-box integration with all your other application
components.
• Access from GCP Console
2.

Lets Compare Monitoring
• Stackdriver was built for hybrid monitoring whereas
Cloudwatch was specific for AWS.
• Stackdriver allows you to monitor GCP, AWS and multicloud
environments.
• For monitoring, Stackdriver gathers GCP,AWS, and custom metrics
using the Stackdriver Monitoring API.
• If monitoring needs expand beyond native cloud services (i.e.
3rd party applications and virtual machine metrics) the API allows
you to extend your monitoring capabilities.
2.

Benefits to know
• Monitors multi cloud

• Identify trends and prevents issues
• Lowers Monitoring headaches
• Fix problems faster
• Reduces monitoring noise!
2.

Major Features to know for Architect Exam..
• Monitoring
• Debugger
• Logging
• Trace
• Error Reporting
2.

Monitoring
• Defaults are intelligent and dynamic
• Health checks
• Metrics = Platform, system, application
>>>>Ingest Data Metrics, events and metadata
>>>>>Then provides insight thru dashboards, charts and
alerts
2.

Uptimes
• Uptime checks verify 6 Global locations.

• When you make a change to an uptime check delay could be 25
minutes
2.

Monitoring agent (AWS EC2 and GCP VMS)
• App Engine has built in support
• The Monitoring agent, stackdriver-agent, is based on the
original collectd system statistics collection daemon.
stackdriver-agent
• Only specific OS's and versions are supported so validate
here.
https://cloud.google.com/monitoring/agent/
2.

Logging
• Supports Platform, System and App logs
• 30 day retention (Cloud Storage for longer) 7 Days Basic
• Search, view and filter
• Log based metrics
• Alerts on log events
2.

Logging
• Don’t use substrings
• Setup Filters
• Advanced viewing interface
• Export logs to Cloud Storage
• BigQuery (Search and Analyze)
• Datalab (Visualize)
• Pub/Sub (App or Endpoint Streams)
2.

Reporting
• Setup Filters
2.

Reporting
• Setup Filters
2.

Tracing
• Displays data in near time

• Latency reports
• Latency sampling (URL)
• Data is collected
• App Engine
• HTTP Load Balancers and Stackdriver Trace SDKS
2.

DEBUGGING
• Inspect Applications and not
have to stop it
• App Engine Standard or
Flexible Java, Python or Go
• Snapshots
• Logpoints
Infrastructure Deployments
2.

Why have an Infrastructure as a code.
• Version Control
• Consistent configurations
• Audit Trails
• CD pipeline
• Failback
2.

Lets Consider Options
• Deploying infrastructure
AWS GCP
Infrastructure Tool CloudFormation Deployment Manager

Resources Stack Files, templates and
schemas
Syntax JSON, YAML YAML, Jinja, Python
Reuse Nested Stacks Templates
Scope Regional Global
GCP Positioning
2.

Google Cloud Platform Competes with AWS or is superior in
some respects.
• Long-term discounts provide significant costing benefits
(Instant)
• Big Data and Machine Learning products are market
leading. (Cloud ML, Cloud Datalab, BigQuery)
• Instance configurability and flexibility.
• Service Latency
• Privacy and traffic Security
• Expertise in DevOps and SRE
2.

Google Cloud Positioning
• GCP is growing quickly but is a work in progress.

• They have been “Developer” focused but not Enterprise focused.
This is approach is changing of course.
• Partnered with Cisco. They know enterprises.
• GCP is a great choice for DevOps environments
• GCP is also a great choice for more flexible pricing and contracts.
• GCP is picking up market share in some segments. AWS has had
over five years for a in enterprise compute services.
2.
GCP Certifications
Google has a limited but growing portfolio of Cloud Certifications.
• Associate Cloud Engineer

• Professional Cloud Engineer
• Professional Data Engineer
• G Suite Administrator
• G Suite
Certification Page
https://cloud.google.com/certification/
How does GCP Certifications Map to AWS Certifications?
GCP AWS
Associate Cloud Engineer AWS SysOps Associate
Cloud Architect AWS Solutions Architect -
Professional
Data Engineer AWS DevOps Engineer –
Professional
GCP Certifications
Thank you

Gcpforawscourseonpearsonrev11541985173886 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Gcpforawscourseonpearsonrev11541985173886 PDF

Uploaded by

Copyright:

Available Formats

GCP

for AWS Course

GCP for AWS Professionals

Segment 1: Why Google Cloud Platform, Network Infrastructure,

• GCP Platform Overview

• This course was designed for IT Professionals who have a

Lets Find out More about the Audience

Who currently is or is planning on using GCP services in

• Yes, we are using GCP Services

What Google Cloud Certifications are of interest to you?

Lets Get Started

• Google Cloud Platform enables developers to build, test and

• Choose from computing, storage, big data/machine learning,

• Google has the most powerful infrastructure and owns most

• Sub Minute Billing

• Google provides interoperability at multiple layers of the

Your choice managed or

For more information on Google’s Edge Network, see:

• Zones have high-bandwidth, low-

• Note that there could be bandwidth

• Google recommends deploying

Edge Caching POP (Cloudfront) POP(CDN, Other Cloud Platform's POPs

Total Services 200 + 50+

• N. Virginia (6) • Asia Pacific Central (2)

Hierarchy in Google Cloud Platform

• Google Cloud IAM is comparable

• An Organization resource is available for G Suite and Cloud Identity

• Projects have three main

Use a project to:

Both AWS and GCP have

GCP Services Overview – Virtual Networking

Click to edit Master title style

• Use Latency Check from

Click to edit Master title style

• Google Network speed up to

• Over Googles private network

Click to edit Master title style

• Standard Tier - It delivers

• Premium Tier - served over

Click to edit Master title style

Click to edit Master title style

Click to edit Master title style

• Global Communications Space

Click to edit Master title style

• Global Communications Space

Click to edit Master title style

• GCP offers global networks

Click to edit Master title style

• GCP has a interconnect (AWS Directconnect) called Cloud

Click to edit Master title style

• GCP supports peering. Peering is the direct

Click to edit Master title style

SSH Keys Include your keys Instance and project wide

Public Images Yes Yes

Marketplace AWS Marketplace Cloud Marketplace

Import/Export VM import/export Import RAW Images import more

Note! A Compute Engine instances can run Linux and Windows

IaaS – Infrastructure as a Service (AWS its called EC2)

• Can be predefined (templates or custom)

Standard, SSD (Can Scale PDs) or local SSD

• Global resources include preconfigured

Click to edit Master title style

• If marked auto restart, the system will try to launch a