Subreddit

Top books from r/devops

A subreddit for practitioners and engineers working in DevOps, focused on culture, tooling, automation, and the organizational side of software delivery.

Updated September 2026 — rankings refresh with each new pull of comment data.

Books ranked

472

Published mentions

sum of exact per-book subreddit rows

490k

Members

Years tracked

About this ranking

r/devops is dominated by two books to a degree unusual even among technical subs: The Phoenix Project pulls 324 mentions and The DevOps Handbook 174, together accounting for the vast majority of all recommendations. That pair has almost no presence in r/learnprogramming or r/programming, where the conversation centres on language fundamentals and craft. Continuous Delivery (42 mentions) and Accelerate (32) round out a list that stays tightly focused on deployment pipelines and organizational change rather than algorithms or language idioms. Designing Data-Intensive Applications shows up at 28 mentions — high enough to signal that infrastructure engineers here care about data systems, though nowhere near its dominance in r/ExperiencedDevs (247 mentions).

Guides built from this community

Ranked best-of lists and editorial guides that draw on r/devops's tracked mentions.

By year

2026 2025 2024 2023 2022 2021 2020 2019

Most-mentioned in r/devops

Ordered by tracked mention count across all published years. Sentiment is shown as context and does not change the order. The Upvotes toggle re-sorts by comment-score weight — display only, the canonical order stays mention-count.

Sort by upvotes = sum of comment scores on recognized mentions

The Phoenix Project

Gene Kim

A struggling IT VP inherits a doomed project, a company on the edge of collapse, and one coworker who has quietly become the company's entire bottleneck.

165 in this sub positive

The DevOps Handbook

Gene Kim

Why a company doing 10,000 deploys a day breaks less often than one doing four a year, and what it takes to get from the second number to the first.

88 in this sub positive

Accelerate

Nicole Forsgren

Four researchers measure what actually makes software teams fast, and the findings keep getting cited against companies mistaking speed for shortcuts.

48 in this sub positive

The Unicorn Project

Gene Kim

A senior engineer gets exiled to a doomed payroll project and finds a rogue skunkworks team racing to save the company's flagship app before the deadline kills it.

32 in this sub positive

Continuous Delivery

Jez Humble

The devops book the internet's most skeptical devops subreddit never actually argues with.

27 in this sub positive

Designing Data-Intensive Applications

Martin Kleppmann

Martin Kleppmann walks backend engineers through every database, queue, and consistency tradeoff they'll eventually get paged about.

15 in this sub Not scored

TCP/IP Illustrated, Vol. 1

W. Richard Stevens

You run tcpdump on a mystery connection and finally understand every line it prints, packet by packet.

10 in this sub positive

Clean Code

Robert C. Martin

Robert Martin's case that unreadable functions are a discipline failure, not an inevitability, argued one renamed variable and one extracted method at a time.

5 in this sub Not scored

The Practice of Cloud System Administration

Thomas A. Limoncelli

Limoncelli's sequel to the sysadmin bible, rebuilt for teams who rent their servers by the hour instead of racking them.

5 in this sub mixed

#10

Network Warrior

Gary A. Donahue

Gary Donahue's field manual for the network engineer who inherits a closet full of Cisco gear and has to keep packets moving by Monday.

4 in this sub Not scored

#11

Systems Performance: Enterprise and the Cloud

Brendan Gregg

A production service is degrading and nobody can say why, so you reach for the book that turns 'it feels slow' into a flame graph pointing at the actual line.

4 in this sub Not scored

#12

The C Programming Language

Brian W. Kernighan

Two authors write the book that becomes 'K&R,' and forty years later Reddit still uses it as shorthand for programmers who had to know everything themselves.

4 in this sub Not scored

#13

UNIX and Linux System Administration Handbook

Evi Nemeth

A five-edition reference guide sysadmins have called 'the bible' since Evi Nemeth wrote the first one in 1989.

4 in this sub Not scored

#14

An Elegant Puzzle

Will Larson

Will Larson treats engineering management as a systems problem, headcount and career ladders, and r/ExperiencedDevs keeps filing it next to Designing Data-Intensive Applications.

3 in this sub positive

#15

Cracking the Coding Interview

Gayle Laakmann McDowell

The book credited with inventing the modern coding interview, argued about like it's also on trial for it.

3 in this sub Not scored

#16

Design Patterns

Erich Gamma

Four authors catalog twenty-three recurring object-oriented problems in 1994 and hand every future code review the same argument to have.

3 in this sub Not scored

#17

Effective Python

Brett Slatkin

Brett Slatkin's Python style guide gets read cover to cover, while its usual shelf-mate Fluent Python becomes something to scare junior devs with instead.

3 in this sub Not scored