Web services communication protocols are the standardized methods through which distributed applications exchange data over networks, defining how services send requests, receive responses, and handle real-time or asynchronous interactions. What This Is and Why These Components Work Together Web services need a common language to talk across the internet. Without protocols, a Java service on […]
The 7-Layer OSI Model is a conceptual framework that organizes how computer networks communicate, splitting the process into seven distinct layers, each responsible for a specific aspect of data transmission—from raw electrical signals to user applications. What This Model Is and Why It Matters The OSI (Open Systems Interconnection) model is not a protocol or […]
1. What Is Stoicism? Stoicism is a practical philosophy that teaches you how to live well, stay calm, and act wisely, especially when life is difficult. It started in ancient Greece and was later developed in Rome, but its ideas are extremely useful today. At its core, Stoicism focuses on three things: You don’t need […]
The Saga pattern is one of those ideas that sounds intimidating until you realize it’s basically a grown-up way of saying: “When a long process has many steps, and one step fails, don’t panic—undo the earlier steps carefully.” Picture a classic problem in distributed systems. You have multiple services, each with its own database. There […]
What this diagram is trying to show It shows a typical setup where Terraform provisions AWS + cluster add‑ons, while CI builds and ships containers, and Kubernetes runs them behind an ALB with DNS. First: understand the four big areas (subgraphs) 1) Developers / CI This is the software delivery pipeline: you push code, CI […]
A Kubernetes Ingress is a Kubernetes-managed way to route external HTTP/HTTPS traffic to the right Services inside a cluster using hostnames and URL paths. 1) What this combination is and why the components are used together Ingress is not a single component—it’s a pattern made of a few pieces that work together: They’re used together […]
A Helm chart is a packaged, reusable way to define, install, and upgrade an application on Kubernetes. 1) What this is and why the components are used together Kubernetes is great at running containers, but it expects you to provide many related objects—deployments, services, ingress rules, config, secrets references, autoscaling settings, and more. Managing those […]
Relationship Diagram (with 1→N associations) What “one-to-many” means here (plain English) 1) Physical Machine → VMs (1→N) A single physical server can host many VMs (depending on CPU/RAM limits). Why? Virtualization slices hardware into multiple isolated “computers”. 2) Node → Pods (1→N) A node (a worker machine) typically runs many pods. Why? Kubernetes schedules pods […]
Below is a clear mental model for how container, pod, node, VM, and physical machine relate. Think of them as layers of “where software runs”, from hardware up to your app process. The “stack” in one picture (most common in cloud Kubernetes) In short:\ Physical machine → (Hypervisor) → VM → Node → Pod → […]
Big Picture Overview Modern systems don’t run on “just code.” They run on infrastructure: networks, databases, load balancers, Kubernetes clusters, IAM roles, message queues, and more. In the cloud, these are all created through APIs—meaning your infrastructure is effectively software-controlled. But there’s a catch: Terraform exists to solve this. Terraform is a tool for Infrastructure […]
My Notes 