The first couple of chapters are aimed at the small, one-man-band, startup dev team. They cover source control, development environments, that sort of thing. The last four or five chapters are the meaty parts, covering caching, identifying bottlenecks, layering your application to improve flexibility, monitoring and defining apis. The focus is definitely on open-source tools, which is good, but he does cover some of the more common paid-for alternatives when needed. He also gives you some useful rules for working out what to choose, in terms of hardware and software.
There's some good stuff in here, that outweighs the less-relevant (to me) chapters.