Projects · Mini Hostpapa
Books That Help You Decide
The reading shelf behind HostKid — books that teach skills, tradeoffs, and the decisions real hosting companies had to make.
Books That Help You Decide
Alright — you have the intro. You have The Engineering Handbook Volumes. That's the map of what we're building.
This page is different.
This is the reading shelf — books that actually helped me think like someone building a hosting company, not just someone who can SSH into a box and feel productive for five minutes.
No single book is titled How to Build HostKid in Your Basement. These are the ones that teach skills, tradeoffs, and decisions — the stuff you need when you're choosing CloudStack over Proxmox, designing a provisioning engine, or explaining to Sales why "just one more VM" is never just one more VM.
I'm not asking you to read all of them. That would be a flex, not a plan. Skim this page, pick what matches the volume you're on, come back when you're stuck.
How to use this shelf
| When you're… | Reach for… |
|---|---|
| Choosing a platform or defending a decision | Decision & architecture section |
| Learning Linux, networking, storage basics | Foundation skills section |
| Building Terraform / Ansible / CI pipelines | Automation & IaC section |
| Running the company day-to-day | Ops, SRE & production section |
| Talking to customers, Sales, or interview panels | Solutions & business thinking section |
Buy used. Borrow from a library. Read one chapter on a bad day. The goal is better decisions, not a dusty shelf for LinkedIn photos.
Start here — mindset first
These four set the tone before you touch CloudStack, Terraform, or a billing system.
The Phoenix Project
Authors: Gene Kim, Kevin Behr, George Spafford
Get it: Amazon — The Phoenix Project
The IT ops story that reads like a novel. Chaos, firefighting, bottlenecks — then flow. If you've lived the "click clone in Proxmox and pray" life from the intro, this book will feel uncomfortably familiar… in a good way.
Helps with: why automation and traceability matter · ops vs business pressure · Volume 0, 21, 27
The Unicorn Project
Author: Gene Kim
Get it: Amazon — The Unicorn Project
Same universe as Phoenix, but from the developer side. Portal, API, platform teams — the friction when "the app people" and "the infra people" don't speak the same language.
Helps with: customer portal thinking · platform vs product · Volumes 8, 10, 20
Thinking in Systems
Author: Donella Meadows
Get it: Amazon — Thinking in Systems
Not a tech book — a decision book. Feedback loops. Unintended consequences. Why picking a hypervisor without thinking about the product layer bites you two years later. Read this before you argue about stack choices on Reddit.
Helps with: platform selection · architecture tradeoffs · Volume 3 decision record
The Goal
Author: Eliyahu Goldratt
Get it: Amazon — The Goal
A factory novel about bottlenecks. Replace "factory" with "datacenter" and "hosting support queue" and it still works. Capacity isn't "we have free RAM" — it's where work piles up.
Helps with: capacity planning · ops efficiency · Volume 27
Decision & architecture — when you're choosing the stack
You evaluated Proxmox, VMware, CloudStack. These books help you explain that decision like an engineer, not a fanboy.
Software Architecture: The Hard Parts
Authors: Neal Ford, Mark Richards, Pramod Sadalage, Zhamak Dehghani
Get it: Amazon — Software Architecture: The Hard Parts
No silver bullets — only tradeoffs. Distributed systems, data ownership, when to split services. Perfect companion when you document why HostKid runs CloudStack on KVM.
Helps with: decision records · system decomposition · Volumes 3, 19, 25
Cloud Computing: Concepts, Technology & Architecture
Authors: Thomas Erl, Ricardo Puttini, Zaigham Mahmood
Get it: Amazon — Cloud Computing (Erl)
Dry in places, but the vocabulary is gold. IaaS vs PaaS. Multi-tenancy. Cloud service models. When someone asks "isn't this just VMs?" — this book helps you answer properly.
Helps with: hosting business model · cloud terminology · Volumes 0, 3, 4
Architecting for Scale
Author: Lee Atchison
Get it: Amazon — Architecting for Scale
How products survive growth — failure modes, scaling patterns, what breaks when you go from ten customers to ten thousand. Hosting is a scale business wearing a tech hat.
Helps with: product growth · reliability planning · Volumes 15, 19, 27
Apache CloudStack Cloud Computing
Authors: Navin Sabharwal, Ravi Shankar
Get it: Amazon — Apache CloudStack Cloud Computing
The closest thing to a book-shaped CloudStack companion. Not perfect — docs will always beat it for version specifics — but solid for zones, pods, clusters, and the IaaS mental model.
Helps with: CloudStack fundamentals · Volume 4
Always cross-check with Apache CloudStack documentation. Books age; upstream docs don't lie about your version.
VMware vSphere Design (comparison context)
Author: Scott Lowe
Get it: Amazon — VMware vSphere Design
You didn't pick VMware for HostKid — but enterprise hosting conversations will reference it. This helps you speak that language in interviews and customer meetings.
Helps with: enterprise comparison · Volume 3 evaluation · Volume 25
Foundation skills — Linux, network, storage
The unglamorous volumes. The ones that save you at 2 a.m.
UNIX and Linux System Administration Handbook
Authors: Evi Nemeth, Garth Snyder, Trent Hein, Ben Whaley, Dan Mackin
Get it: Amazon — UNIX and Linux System Administration Handbook
The thick one on the shelf that earns its space. Users, services, storage, networking — everything in Volume 2 lives here in deeper form.
Helps with: Linux admin · SSH, systemd, firewalls · Volume 2
Computer Networking: A Top-Down Approach
Authors: James Kurose, Keith Ross
Get it: Amazon — Computer Networking (Top-Down)
DNS, HTTP, TCP/IP, TLS — taught from applications down. Half of hosting support tickets are networking misunderstandings in disguise. This fixes that.
Helps with: internet fundamentals · DNS · TLS · Volumes 1, 5, 12
DNS and BIND (5th Edition)
Author: Cricket Liu
Get it: Amazon — DNS and BIND
If you sell domains and records, you need DNS depth. PowerDNS in Volume 12 sits on the same foundations this book teaches.
Helps with: DNS platform · email routing · Volumes 12, 13
Learning Ceph
Author: Karan Singh
Get it: Amazon — Learning Ceph
Distributed storage for a cloud platform. Ceph shows up in serious IaaS deployments — understand it before you treat storage like "just mount a disk."
Helps with: Ceph · replication · Volume 6
FreeBSD Mastery: ZFS
Author: Michael W. Lucas
Get it: Amazon — FreeBSD Mastery: ZFS
Lucas writes ops like a human, not a manual. ZFS snapshots, pools, and the "why would I trust this with customer data?" questions — answered clearly.
Helps with: ZFS · snapshots · Volume 6
Automation & IaC — ProxGen DNA at company scale
Where declarative ops meets customer-facing products.
Terraform: Up & Running
Author: Yevgeniy Brikman
Get it: Amazon — Terraform: Up & Running
The book behind the mindset that built ProxGen. State, modules, plan/apply/destroy — if you're wiring automation into Volume 19, start here.
Helps with: Terraform · provisioning · Volumes 7, 19, 21
Infrastructure as Code
Author: Kief Morris
Get it: Amazon — Infrastructure as Code
Beyond one tool — patterns for environments, drift, testing, pipelines. Terraform is a hammer; this teaches you when not to swing it blindly.
Helps with: GitOps · environment strategy · Volumes 7, 21
Ansible: Up & Running
Author: Lorin Hochstein
Get it: Amazon — Ansible: Up & Running
CloudStack creates the VM. Ansible makes it yours — users, packages, hardening, app bootstrap. Post-provision config lives here.
Helps with: configuration management · post-boot setup · Volumes 7, 19
Continuous Delivery
Authors: Jez Humble, David Farley
Get it: Amazon — Continuous Delivery
The north star for Volume 21: repeatable, low-risk change. Pipelines that don't depend on "the one person who knows the deploy script."
Helps with: CI/CD · release safety · Volume 21
Platform, API & identity — the control plane
Internal Kubernetes, customer portal, REST APIs, SSO.
Kubernetes: Up & Running
Authors: Kelsey Hightower, Brendan Burns, Joe Beda
Get it: Amazon — Kubernetes: Up & Running
For internal platform workloads — monitoring, API, portal — not "sell k8s to customers" day one. Clear, practical, no cult membership required.
Helps with: k3s / k8s basics · Volume 8
OAuth 2 in Action
Authors: Justin Richer, Antonio Sanso
Get it: Manning — OAuth 2 in Action
OIDC, OAuth, tokens — explained so you can implement SSO without cargo-culting a Keycloak tutorial and hoping.
Helps with: identity · SSO · Volume 9
API Design Patterns
Author: JJ Geewax
Get it: Manning — API Design Patterns
How your provisioning API should feel to integrators and future you. Versioning, errors, resource naming — the boring stuff that separates a product from a script.
Helps with: REST design · OpenAPI thinking · Volume 20
Ops, SRE & production — running the company
Metrics, incidents, security, capacity — year two survival.
Site Reliability Engineering
Authors: Betsy Beyer, Chris Jones, Jennifer Petoff, Niall Richard Murphy (Google)
Get it: Amazon — Site Reliability Engineering
SLI, SLO, error budgets, on-call culture. Volume 27 vocabulary in one place. You don't need to copy Google — but you should steal the language.
Helps with: SLO/SLI · incident mindset · Volumes 17, 27
The Site Reliability Workbook
Authors: Niall Richard Murphy et al.
Get it: Amazon — The Site Reliability Workbook
SRE ideas with exercises and implementations. Less theory, more "okay but what do I actually do Monday morning?"
Helps with: practical SRE · alerting · Volumes 17, 18, 27
Observability Engineering
Authors: Charity Majors, George Miranda, Liz Fong-Jones
Get it: Amazon — Observability Engineering
Modern metrics, logs, traces — and why dashboards full of green lies don't mean you're fine. Pairs with Prometheus/Grafana/Loki in Volume 17.
Helps with: monitoring · debugging production · Volumes 17, 18
Building Secure and Reliable Systems
Authors: Heather Adkins et al. (Google)
Get it: Amazon — Building Secure and Reliable Systems
Security and reliability as one discipline — not security bolted on after the portal ships. Multi-tenant hosting needs this mindset early.
Helps with: security + reliability · RBAC · Volume 22
Release It!
Author: Michael Nygard
Get it: Amazon — Release It!
Stability patterns, cascading failures, bulkheads, timeouts. Migration cutovers and production fires — this is the "what breaks in the real world" book.
Helps with: failure modes · migrations · Volumes 24, 27
Solutions & business thinking — the interview volumes
When you need to explain the platform to humans who don't read your handbook.
The Manager's Path
Author: Camille Fournier
Get it: Amazon — The Manager's Path
Even if you never want to manage, this teaches how to communicate with Engineering, Sales, Ops, and customers — Volume 25 in book form.
Helps with: cross-team communication · Volume 25
Team Topologies
Authors: Matthew Skelton, Manuel Pais
Get it: Amazon — Team Topologies
Platform team vs stream-aligned team vs enabling team. Helps you structure who owns CloudStack vs who owns the portal as HostKid grows.
Helps with: org design · platform teams · Volumes 8, 25, 27
Free resources worth your time
Not everything worth reading has an ISBN.
| Resource | Link | Why bother |
|---|---|---|
| The Architecture of Open Source Applications | aosabook.org | Real systems, real tradeoffs — read like Volume 26 case studies. |
| Apache CloudStack docs | docs.cloudstack.apache.org | Primary source for Volume 4 — always current. |
| CNCF landscape | cncf.io/landscape | Volume 28 future evolution — see where the industry is heading. |
Suggested reading paths
Pick one path. Finish a book before you buy three more. Future you will thank present you.
Path A — "I'm choosing the platform" (Volumes 0–4)
- Thinking in Systems
- Cloud Computing (Erl)
- Software Architecture: The Hard Parts
- Apache CloudStack Cloud Computing + official docs
Path B — "I'm building the factory" (Volumes 2–7, 19)
- UNIX and Linux System Administration Handbook
- Computer Networking (Top-Down)
- Terraform: Up & Running
- Infrastructure as Code
- Ansible: Up & Running
Path C — "I'm running the company" (Volumes 17–27)
- Site Reliability Engineering
- Observability Engineering
- Release It!
- Team Topologies
Back to the handbook
Books give you depth. The Engineering Handbook Volumes give you our path — documented decisions, labs, scars included.
Use both. Read a chapter, write a doc page, break something in the lab, update the handbook. That's how this project stays honest.
You don't need permission to skip a book. You need clarity on what problem you're solving today. Find that row in the table above, grab the book, and get back to building.
Happy reading. Volume 0 is still waiting when you're ready.