Integrated by Design: Why the Best Systems Are the Ones You Don't Notice

The operating system book that Linux administrators didn't know they needed. With practical examples you can follow along.22 chapters. One thesis: integrated systems solve problems that assembled ones keep creating.You administer Linux servers. They work. You are, with sufficient conviction, even proud of them. But you have also noticed that the firewall offers four tools for the same job (none quite deprecated enough to ignore), the init system has quietly annexed half the operating system, and the package manager pulls in half the internet to install a perfectly ordinary text editor.One might reasonably wonder whether it has to be this complicated.It does not. FreeBSD ships one kernel, one userland, one package manager, one firewall — built by one team, in one repository, released together. This book shows you what that difference looks like in practice, across eight domains where the pattern repeats so reliably that by Chapter Eight, you will see it coming. That is rather the point.What you getPart I — The problem: why modern server infrastructure feels more complex than it ought to bePart II — The evidence: containers, upgrades, storage, firewalls, packages, init systems, networking, and documentation — compared head-to-head, with characteristic British restraintPart III — The pattern: why the integrated model produces these results (and what the demoscene has to do with operating system design)Part IV — Hands-on: install FreeBSD, build a web stack with jails, deploy services through Unix sockets, upgrade without downtime, and monitor with tools that ship in the base system. Every command works on FreeBSD 15. Every example includes its output. Nothing is left to imagination or optimism.How this book is differentThe comparisons are fair. Linux is a remarkable achievement, and the people who build it deserve respect. They get it here. What they have built, however, is an assembled system, and this book argues that integrated systems solve certain problems more cleanly. That is a statement about architecture, not about competence.Written by a systems engineer with twenty-seven years across Linux, FreeBSD, and the demoscene. The servers in the examples are named after Star Trek characters, because life is too short for server1 and example.com has suffered enough.For Linux administrators who have wondered whether it has to be this complicated.For FreeBSD users who have always known it doesn't. Read more