Google Cloud Functions

Question 1

Cloud Functions

Answer 1

Serverless, Event-driven, stateless, and autoscaling that is quick and pay as you go for small applications

Question 2

Use for IoT Backends

Answer 2

Process and autoscale data from IoT without any human intervention

Question 3

Use for Mobile Backends

Answer 3

Can process data delivered by mobile applications and can interact with all GCP services to make use of big data, ML capabilites, and so on.

Question 4

Use for Third-Party API Integrations

Answer 4

Use functions to integrate with any third party system that provides API allowing you to extend your application with additional features delivered by other providers

Question 5

Real Time Stream Processing

Answer 5

When messages arrive in the Pub/Sub, Cloud Functions can be triggered to analyze or enrich the messages to prepare them for further data processing

Question 6

Real Time Files Processing

Answer 6

Immediately process files uploaded to your Cloud Storage Bukets using GCP AI APIs or creating thumbnails

Question 7

Autoscaling in Cloud Functions

Answer 7

Scale from zero to desired scale, and is managed without user intervention. Limits can be set to control execution cost, to prevent design flaws causing spikes in use.

Question 8

Stateless Cloud Functions

Answer 8

Functions do not store state or data. This allows them to work independantly and scale as needed. Each invocation has its own execution enviornment and does not share global variable memory or file systems. To share state across function invocations, should use Cloud Datastore or Cloud Storage.

Question 9

Event Drive Response in Cloud Functions

Answer 9

Cloud Functions are triggered in response to an event of HTTP request, therefore they are invoked only wen needed and have no cost when inactive.

Question 10

Chatbots and Virtual Assistants

Answer 10

Connect your text or voice platforms to Cloud Functions to integrate them with other GCP services such as DialogFlow to provide a natural conversation experience. Integration with third party aps can also be used to provide services.

Question 11

Video and Image Analysis

Answer 11

Use Cloud Functions to interact with the various GCP AI building blocks such as video and image AI. When a user uploads an image or video, CF can immedately trigger the related API and return the anaylsis and can perform actions depending on the results of the analysis.

Question 12

Lightweight APIs and Webhooks

Answer 12

Cloud Functions can be triggered using HTTP, exposing your application to the external world without building your API from scratch

Question 13

What runtimes are supported in Cloud Functions?

Answer 13

Node.js 6/8/10, Python 3.7, Go 1.11. Modules and libraries associated with that runtime will be automatically loaded into that enviornment.

Question 14

HTTP Functions

Answer 14

Cloud Functions can be triggered by HTTP(S) requests such as post, put, get delete, and options. It can return a response that has been constructed in the function

Question 15

Background Functions

Answer 15

Can be triggered by changes in Cloud Storage Buckets, messages in the Cloud Pub/Sub topic, or one of the supported Firebase Events

Question 16

Event Triggers

Answer 16

Things happening inside or outside the GCP enviornment, where certain occurances trigger an action. Events can come from Cloud Storage, Cloud Pub/Sub, Stackdriver, Cloud Firestore, Firebase Realtime Database, Storage and Authentication

Question 17

Triggers

Answer 17

The configured reaction to an event. The actual binding of the trigger happens at deployment time.

Question 18

Cloud SQL Connectivity

Answer 18

Cloud Functions are stateless and therefore need access to an external storage or database. Cloud SQL can be connected using a local socket interface provided in the Cloud Functions execution enviornment.

Question 19

VPC Connectivity for Cloud Functions

Answer 19

You can access services within VPC by creating serverless VPC access controller, referring to this connection when you deploy the function. Does not work with Shared VPCs and legacy networks.