The GCP family

Introduction to GCP

Nabeel Imam

Content Developer at DataCamp

The storage cousins

Cloud Storage

Logo of Google Cloud Storage

  • Files and data objects
Cloud SQL

Logo of Google Cloud SQL

  • Tables and structured data
Introduction to GCP

Where do the trees go?

An org chart showing a CEO and their direct reports.

  • Trees are non-relational
  • They lack row-column relationships
Introduction to GCP

Say hello to Bigtable

  • Designed to accommodate non-relational data
  • Optimized for large workloads
    • Low latency and high throughput
    • Ideal for applications in IoT, finance, and ad tech

Logo of Google Bigtable.

Introduction to GCP

App dilemma

  • App Engine: the application hosting service by GCP
  • E.g.: an app that converts documents
    • Should it be hosted on App Engine?

An app converting PDFs to Doc files and vice versa.

Introduction to GCP

Cloud Functions

  • Built for single-purpose functions
  • Runs only when called upon
  • Charged per request
    • Cheaper than App Engine in this scenario

Logo of Google Cloud Functions.

Introduction to GCP

Going serverless

  • App Engine and Cloud Functions are serverless

    • They don't need hardware setup or management

  • Like ordering a coffee rather than making it yourself

    • No equipment needed, barista handles everything
    • Only pay for the result

A barista serves a coffee.

Introduction to GCP

Containers

  • Some applications have specific requirements
  • Developers package them into virtual "containers"
  • Like a tiny home for an application
    • Contains everything needed to run it

Containers being used as homes, each container contains all the belongings and necessities of a resident.

Introduction to GCP

So what were virtual machines?

Virtual machine (VMs)

  • Complete environment
  • Includes full operating system

Containers

  • Contains only what is needed for the application
  • Lightweight, can run up to 20 in a single machine!
Introduction to GCP

Containerized applications

Container 1: User authentication

A user enters their user name and password to gain access.

Container 2: Product listings

A user views different products listings on their website.

Container 3: Payment processing

A person uses their credit card to make a purchase online.

And so on...

Each container provides a "microservice"

Introduction to GCP

The power of microservices

  • Microservices break large services into smaller manageable units
  • Can be scaled more efficiently
  • Less prone to system-wide failure

Containers hover around a mobile device that is running an application.

Introduction to GCP

Let's practice!

Introduction to GCP

Preparing Video For Download...