Digital Product Fundamentals
Before any product type, component, or system can be discussed meaningfully, the underlying mechanics of how digital products actually work have to be established. This Part is the conceptual ground floor: what a digital product is, how the internet moves information, how clients and servers divide responsibility, and the architectural choices — static or dynamic, monolith or microservices, cloud or edge — that shape everything built on top of them. Every later Part in this handbook assumes the vocabulary and mental models established here.
Start Part I — 1.1What Is a Digital Product
Before designing or building anything, it's worth being precise about what category of thing is actually being made.
1.2How the Internet Works
A working mental model of packets, addresses, and routing — enough to reason clearly about everything built on top of it.
1.3Client–Server Architecture
The foundational pattern underneath almost every digital product: one side asks, the other side answers.
1.4Static vs. Dynamic Systems
The single decision that most affects a product's cost, speed, and complexity — often made by accident.
1.5Monoliths, Microservices & Event-Driven Systems
Three ways to organize a backend's internal structure — each solving a different scale of problem.
1.6Cloud & Edge Computing
Where code actually runs — and why that location increasingly matters as much as the code itself.
1.7DNS, Hosting & Domains
The plumbing between a typed name and an actual running server — invisible when it works, catastrophic when it doesn't.
1.8HTTP, HTTPS & the Request Lifecycle
The actual conversation format every browser and server uses — and the encryption layer that keeps it private.