Google Cloud Services Flashcards

1
Q

What is serverless?

A

Serverless architecture are fully-managed services that automatically scale, are highly available,
durable and secure by default. Abstracts away the underlying infrastructure and are billed based on
the execution of your business task. Pay-for-Value (you don’t pay for idle servers ).
Serverless can Scale-to-Zero meaning when not in use they cost nothing.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Serverless Services

A

Cloud Functions Function as a Service
Choose a runtime, upload single function code.
Intended to be short-lived.

Knative Serverless K8 containers
Deploy and manage serverless, cloud-
native applications for Kubernetes.

BigQuery Serverless Data-Warehouse
Understand your data using a fully managed, highly
scalable data warehouse with built-in

Cloud Run serverless containers
Run stateless containers on a fully managed
environment or on Anthos.

App Engine Platform as a Service
Build and deploy apps built using traditional web-
frameworks. All the underlying infrastructure is taken
care of for you.

Eventarc Serverless Event Bus
Build event-driven solutions by asynchronously
delivering events from Google services, SaaS, and your
own apps. Used for application integration

Workflows Serverless State Machine
Orchestrate and automate Google Cloud and HTTP-
based API services with serverless workflows.

Cloud Storage Serverless Storage
Store objects with global edge caching.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Storage Services

A

Cloud Storage object Storage
Store objects with global edge caching.

Cloud Storage for Firebase
Add Google-scale object storage
and serving to your apps.

Filestore file-system storage
Create fully managed, high-
performance NFS file servers on Google Cloud

Persistent Disk block-Storage
Add block storage to VM instances.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

More Storage Services

A

Block (Persistent Disk)
Data is split into evenly split blocks
Directly accessed by the Operation System
Supports only a single write volume
When you need a virtual hard drive attached to a VM

File (Filestore)
File is stored with data and metadata
Multiple connections via a network share
Supports multiple reads, writing locks the file.
When you need a file-share where multiple users or
VMs need to access the same drive

Object (Cloud Storage)
Object is stored with data, metadata and Unique ID
Scales with limited no file limit or storage limit
Supports multiple reads and writes (no locks)
When you just want to upload files, and not have to worry
about underlying infrastructure. Not intended for high IOPs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly