CodeWithClarity

  Google Compute Engine (GCE) — IaaS 1. What is Compute Engine? Compute Engine is Google Cloud's IaaS (Infrastructure as a Service) solution. It allows you to create and run Virtual Machines (VMs) on Google's infrastructure. Think of it as: Physical server → Google owns it Virtual machine → You rent/use it You don't need to buy physical servers upfront. 2. What is a Virtual Machine? A VM is like a virtual computer/server running inside Google's data center. You can configure it similar to a physical server: CPU → How much processing power you need Memory (RAM) → How much memory you need Storage → Disk space and type Operating System → Linux, Windows Server, etc. Example You could create: VM ├── 4 vCPUs ├── 16 GB RAM ├── 100 GB Disk └── Linux OS This VM behaves like a complete computer/server. 3. How can you create a VM? You have three main options: Google Cloud Console Web-based graphical interface. Google Cloud CLI Command-line i...

  Google Cloud Load Balancing — Easy Notes 1. Why do we need Load Balancing? Suppose your application starts with 4 VMs , but during high traffic it scales up to 40 VMs . The question is: How do users know which VM to connect to? 👉 Cloud Load Balancing handles this. Load Balancer = Traffic Distributor It distributes incoming user traffic across multiple VMs/backend instances. Users / | \ ↓ ↓ ↓ Load Balancer / / | \ ↓ ↓ ↓ ↓ VM1 VM2 VM3 ... VM40 2. Benefits Distributes traffic across multiple instances. Prevents one VM from becoming overloaded. Improves performance and availability . Automatically responds to: Changes in traffic Number of users Backend health Network conditions Supports cross-region load balancing . Can automatically perform multi-region failover if a backend becomes unhealthy. It's fully managed → you don't need to create or manage load-bala...

 Google Cloud VPC – Important Compatibility Features 1. Routing Tables VPCs have built-in routing tables , similar to physical networks. You don't need to create or manage a router . Routes can forward traffic: Between VM instances in the same network Between different subnetworks Between different Google Cloud zones This communication can happen without external IP addresses . 👉 Key idea: VPC routing is managed by Google Cloud automatically. 2. VPC Firewall Google Cloud VPC provides a global, distributed firewall . It controls both: Ingress → incoming traffic Egress → outgoing traffic You don't need to provision a separate physical firewall. Network Tags Firewall rules can target Compute Engine VMs using network tags . Example: Suppose you have several web servers: VM1 → WEB VM2 → WEB VM3 → WEB You can create a firewall rule: Source → Allowed Port → 80, 443 Target → WEB tag This means all VMs tagged WEB can receive HTTP/HTTPS t...