Understanding Distributed Systems: What every developer should know about large distributed applications
Roberto Vitillo
4.37 average rating, · 544 ratings
Engineering & Computing Specializations
A practical curriculum for building APIs, services, databases, distributed systems, and reliable server-side software.
30 Books Every Backend Engineer Should Read is a deliberately bounded reading path for backend engineers, platform developers, software architects, and technical leads. Rather than inventing a futuristic niche and stretching unrelated books to fill it, this collection begins with a field that already has a substantial literature and then selects thirty titles that genuinely belong inside that scope.
The ranking balances direct topical fit, enduring influence, practical usefulness, reader evidence, and variety of perspective. The opening books are intended to establish the field; the middle of the list adds methods, applications, cases, and counterarguments; the final portion expands the reader’s range without abandoning the subject.
Use the list as a map rather than a compulsory syllabus. Start with one broad foundation, one book closest to a live problem, and one critical or historical counterweight. The page should remain a draft until an editor has inspected every membership, defended the top-ten order, and replaced any title whose relationship to backend engineering is merely incidental.
Ranked 1–24 of 30 — curated order, not the site-wide popularity formula.
Backend engineering sits where application logic, data, infrastructure, security, and operations meet. This list emphasizes books that directly improve the design and operation of server-side systems rather than generic programming inspiration. The value of this page is not the number thirty by itself. Its value comes from keeping the promise narrow enough that a reader can trust the relationship between the headline and the books underneath it. For LinkedIn readers, that makes the collection useful as a professional curriculum, a team discussion resource, and a credible starting point for deeper study.
The list was constrained to an established literature on backend engineering. Candidates were resolved against the verified Topreads dataset, then reviewed for direct title and domain fit, author and genre signals, readership evidence, breadth, and duplicate suppression. Thirty was chosen as a quality ceiling for this release: large enough to offer paths, small enough to inspect. Final publication requires a human editor to verify every membership and the top-ten order.
Topreads must identify the actual curator or reviewer, display a genuine review date, explain the catalogue basis, and provide a way to report weak or mismatched selections. Do not claim expert review, personal reading, or field consensus unless those statements are literally true.
Roberto Vitillo
4.37 average rating, · 544 ratings
Alex Petrov
4.27 average rating, · 579 ratings
Eric Evans
4.15 average rating, · 5.9k ratings
Bill Karwin
4.02 average rating, · 563 ratings
Michael T. Nygard
4.25 average rating, · 3.3k ratings
Ross J. Anderson
4.21 average rating, · 710 ratings
Vlad Khononov
4.43 average rating, · 785 ratings
Stoyan Stefanov
4.17 average rating, · 1.6k ratings
Betsy Beyer
4.21 average rating, · 2.9k ratings
Michael Kerrisk
4.64 average rating, · 727 ratings
Robert C. Martin
4.35 average rating, · 23.7k ratings
Debbie Lafferty
4.24 average rating, · 883 ratings
Erich Gamma
4.20 average rating, · 12k ratings
Spotted a book that doesn't belong here? Tell us — lists are reviewed and corrected.
