Skip to content

Instantly share code, notes, and snippets.

View j-mprabhakaran's full-sized avatar

Prabhakaran Jayaraman Masani j-mprabhakaran

  • Chennai, Tamil Nadu, India
View GitHub Profile
Dataflow lifecycle
migration concerns from migrating from on-premises over into google cloud
code snippet to troubleshoot and diagnose
Part 2 - Hands-on with tools
Role of Cloud Architect
plans, designs and builds the infrastructure for an org to host their workload on GCP; able to plan to scale;
scalability and automation
@j-mprabhakaran
j-mprabhakaran / gist:2993ea834bb54b2e03bcb64d0034f5a5
Created January 20, 2019 10:24
GCP Cloud Architect - Part 3
GCP Cloud Architect - Part 3
Case Studies
Refreshed Nov 9th 2018; JencoMart completely dropped
Overview - 3 case studies; 40-50% on the exam; Question on one side, Case study on other side
Layout of Case study - 1.Company Overview 2.Solution concept - current goal 3.Existing Technical Env 4.Requirements(Tech/Business) 5.Executive statement
Mountkirk Games
Dress4Win
TerramEarth
Mountkirk Games
@j-mprabhakaran
j-mprabhakaran / GCP-Architect-QuickNotes
Created March 30, 2019 05:39
GCP-Architect-QuickNotes
The access pattern fits Nearline storage class requirements and Nearline is a more cost-effective storage approach than Multi-Regional.
The object lifecycle management policy to delete data is correct versus changing the storage class to Coldline.
Google Cloud Storage supports Multi-Regional buckets that synchronize data across regions automatically.
Google Cloud SQL instances are deployed within a single region.
Google Cloud Bigtable data is stored within a single region.
Google Cloud Datastore is stored within a single region.
Using a shared VPC allows each team to individually manage their own application resources, while enabling each application to communicate
between each other securely over RFC1918 address space.