Build a Website on Google Cloud:
Quest: Build a Website on Google Cloud
GitHub Link: https://github.com/rebeljeet/Google-c...
Overview
You must complete a series of tasks within the allocated time period. Instead of following step-by-step instructions, you'll be given a scenario and a set of tasks - you figure out how to complete it on your own! An automated scoring system (shown on this page) will provide feedback on whether you have completed your tasks correctly.
To score 100% you must complete all tasks within the time period!
When you take a Challenge Lab, you will not be taught Google Cloud concepts. To build the solution to the challenge presented, use skills learned from the labs in the Quest this challenge lab is part of. You will be expected to extend your learned skills; you will be expected to change default values, but new concepts will not be introduced.
Please make sure you review the labs in the Hosting a Website on Google Cloud Quest before starting this lab!
Topics tested
Building and refactoring a monolithic web app into microservices
Deploying microservices in GKE
Exposing the Services deployed on GKE
Challenge lab scenario
You have just started a new role at FancyStore, Inc.
Your task is to take the company's existing monolithic e-commerce website and break it into a series of logically separated microservices. The existing monolith code is sitting in a GitHub repo, and you will be expected to containerize this app and then refactor it.
You are expected to have the skills and knowledge for these tasks, so don't expect step-by-step guides.
You have been asked to take the lead on this, after the last team suffered from monolith-related burnout and left for greener pastures (literally, they are running a lavender farm now). You will be tasked with pulling down the source code, building a container from it (one of the farmers left you a Dockerfile), and then pushing it out to GKE.
You should first build, deploy, and test the Monolith, just to make sure that the source code is sound. After that, you should break out the constituent services into their own microservice deployments.
Some FancyStore, Inc. standards you should follow:
Create your cluster in us-central-1.
Naming is normally team-resource, e.g. an instance could be named fancystore-orderservice1.
Allocate cost effective resource sizes. Projects are monitored and excessive resource use will result in the containing project's termination.
Use the n1-standard-1 machine type unless directed otherwise.
My LinkedIn: / jeet-patel-b7a90316a