Reddit Reddit reviews Practice of Cloud System Administration, The: Designing and Operating Large Distributed Systems, Volume 2

We found 24 Reddit comments about Practice of Cloud System Administration, The: Designing and Operating Large Distributed Systems, Volume 2. Here are the top ones, ranked by their Reddit score.

Production & Operations
Business Management & Leadership
Business & Money
Practice of Cloud System Administration, The: Designing and Operating Large Distributed Systems, Volume 2
Addison-Wesley Professional
Check price on Amazon

24 Reddit comments about Practice of Cloud System Administration, The: Designing and Operating Large Distributed Systems, Volume 2:

u/jwaters · 99 pointsr/sysadmin

The "Practice of System and Network Administration"; probably a bit too early in your career but has some strong advice.

There's also a volume 2 which is cloud/site reliability engineering related.

u/OSUTechie · 26 pointsr/ITCareerQuestions

This book has been suggested a few times so I finally got around to reading it. I think it has some good information in it. I'm only about halfway through it, but I like it so far.

Time Management for System Administrators

Other books would be any of the social books like "How to influence people", "7 healthy habits..." Etc.

I haven't read this one yet, but It has been suggested to me if you plan to go more into management/leadership Start with Why

Other books that have I have ear marked due to being mentioned:

u/mu71l473d · 23 pointsr/sysadmin
  • The Practice of System and Network Administration, Third Edition
  • UNIX and Linux System Administration Handbook, Fifth Edition
  • The Practice of Cloud System Administration: DevOps and SRE Practices for Web Services, Volume 2, First Edition
  • Windows Server 2016 Unleashed, First edition
u/davethebarb · 11 pointsr/sysadmin

This mentions The Practice of Network and System Administration, and how it could do with an update; that would be here, in The Practice of Cloud System Administration, which as I understand is effectively the 'replacement' book, at least for an approach more suited to modern infrastructure.

u/polycarpgyarados · 8 pointsr/ITCareerQuestions

The senior part is more of a technical grade level and not necessarily management... granted I'm in the lead role here, it's my first time as one. All I can say is what help me spring forward at a lull at mid-level was picking up Thomas Limoncelli's books, [the sysadmin one] ( and [the cloud one] ( /r/sysadmin recommends them too. These are your best practice books, these tell you why to do things, not how. It will turn you from being the guy that mops the floor in a burning building into knowing when to yell, "FIRE!"

Cert wise, unless a specific company or contract requires it, I don't bother with the time and money on certs if you already have years of experience on the books. I'd probably go for a Security+ and then go for a Red Hat and/or CCNA certification as they are both prestigious. Red Hat is a big deal just by its practical application test.

If you want to go into cloud related stuff, you might want to brush up on your programming. This is what is limiting me, I have very minimal bash scripting experience coming from military in the Windows world then making a move to Linux.

Honestly, I would focus on being both as they both overlap very often unless you are in really large stovepipe enterprise environments, but you never know if you need to make a move to something smaller where you have the many hats role. I'd get your degree in something Computer science related (CS, CIS, EE, CE, etc) and then go RHCSA/CE and maybe Sec+/Net+ or instead of Net+ just go for something Cisco related. My networking is Net+ strength at best and I resent not doing better when I was younger.

EDIT: Also, if you can do the math, BS is Computer Science all the way... sysadmins are still really kind of not doing well in the degree program department, mainly because were so... trade-like I guess. Honestly, we're the new Millwrights like my dad was. We keep the factory going and fix it when production stops. It's kind of cool actually, it's nice to be able to have some kinship to my dad in that way.

u/btvn · 6 pointsr/devops

Might as well get the follow up:

The book is good, but again a little too Google focused.

u/jonconley · 6 pointsr/sysadmin

If the Practice of System and Network Administration is a bit dated, check out The Practice of Cloud System Administration: Designing and Operating Large Distributed Systems, Volume 2, September 15, 2014, by the same author.

u/levi_mccormick · 4 pointsr/devops

"The Practice of Cloud System Administration" is my bible. Every time I have a question like this, I find the answer in here.

u/dundir · 4 pointsr/learnpython

This is more of an operational problem and less of a programming problem. The troubleshooting aspect is about the only thing problem related, i.e. stack traces, perf, flame graphs, and logs on the programming side.

The operational side is how do you keep the program running adequately and the simple answer is to detect when it fails automatically, and have a new process start if its failed. So healthchecks, triggers, siem, and probably a cloud based 3-4 tier topology (load balancers, orchestration [docker], app, databases/fileshare [state]) if it needs high availability or the ability to scale.

The Practice of Cloud System Administration is a must have for a starting point in developing resilient services.

u/harimau22 · 4 pointsr/sysadmin

And [The Practice of Cloud System Administration: DevOps and SRE Practices for Web Services] (

u/jrnt30 · 3 pointsr/devops

I think all of those things you've listed are valuable in their own right, however I think a bit of focus may help. First, determine what you are actually trying to accomplish because learning all those at once is not really feasible. Break that long term goal down into more meaningful steps.

For example, a good long term goal may be:
> Deploy an source controlled application on AWS using a configuration management tool, leveraging Infrastructure as Code to make it repeatable and Immutable Infrastructure to provide stability.

Breaking that down we have a series of things to learn:

  1. Getting comfortable with source control systems (Git is obviously popular but others work just fine as well)
  2. Learning the core constructs of AWS
  3. Configuration Management
  4. Infrastructure as Code
  5. Immutable Infrastructure

    These things can be done somewhat in parallel, but I would say focus your efforts will most likely provide the best value. The order in which I've listed these I find is the most useful to instruct people that are new to the area.

    Building A Scalable Web App on AWS

    General Cloud Architecture
    The Practice of Cloud Systems Administration

    Git Book
u/AccomplishedAdmin · 3 pointsr/ITCareerQuestions

Sysadmin, I've been doing Lead SysEng/DevOps/SRE for the past 4 years and literally have multiple written offers I'm trying to choose from right now.

I only started looking 3 weeks ago.

Learn multiple clouds(I've done the big 3 in prod and other ones for utils/tools/hobby/legacy systems), Kubernets/docker, Linux, distributed systems and ansible/puppet/chef

Read this:
and this:

See if you can buy time for the internship offer, having multiple offers is always better :)
Is the internship paid?

u/redoctet · 3 pointsr/aws

Though you're asking in the context of AWS, there are many best practices for designing and operating a distributed system at scale whether it's under AWS or not. The Practice of Cloud System Administration is platform agnostic and a fantastic place to start. No referral link!

u/mattstratton · 2 pointsr/devops

The title is a little misleading, but the latest version of The Practice Of Cloud System Administration is excellent.

u/zinver · 2 pointsr/sysadmin

> What knowledge do you carry over from the history of our field that you can't easily learn or discover now?


> Instead of one system to do everything for the business, I am starting to see a trend towards many specialized systems that are built to interface with other systems.

Go together nicely. This is how things were before the PC took over. What did the old-timers do? What approaches to system design need to be taken into consideration when dealing with multiple vendors that are not interoperable? What about support contract management? These things haven't changed much. And they are hard questions to answer through a book.

Books to read? Hmm. I generally suggest:

u/motodoto · 2 pointsr/sysadmin

Well I'll be the first one to give you generic information that you could have found with the search function.

You just do the needful.

Good screwdriver set.

A network tone tester in case you need to map out your network and document everything. Also functions as a basic cable tester.

A punch down tool.

An ethernet crimper.

A quick cable stripper.

A usb hard drive dock.

A notebook.

Your necessities may vary, this applies to more of a one-man shop, and there's plenty of other things you'll want to get that I don't have listed here depending on your job.

I dunno how much you should get paid.

u/mfinnigan · 2 pointsr/sysadmin

Stay on-prem.

Unfortunately, you're asking a very broad and vague set of questions. All of those topics you're asking about are an issue to be managed even if you're only using a single cloud provider, let alone multiple ones. Books have been written on these topics. Read those books and build the answers that apply to your job. That's the best way to handle those challenges. There's no silver bullet, not for any one of those topics.

Here's a good starting point, especially if you literally don't know where to start.

u/CSMastermind · 2 pointsr/AskComputerScience

Senior Level Software Engineer Reading List

Read This First

  1. Mastery: The Keys to Success and Long-Term Fulfillment


  2. Patterns of Enterprise Application Architecture
  3. Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions
  4. Enterprise Patterns and MDA: Building Better Software with Archetype Patterns and UML
  5. Systemantics: How Systems Work and Especially How They Fail
  6. Rework
  7. Writing Secure Code
  8. Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries

    Development Theory

  9. Growing Object-Oriented Software, Guided by Tests
  10. Object-Oriented Analysis and Design with Applications
  11. Introduction to Functional Programming
  12. Design Concepts in Programming Languages
  13. Code Reading: The Open Source Perspective
  14. Modern Operating Systems
  15. Extreme Programming Explained: Embrace Change
  16. The Elements of Computing Systems: Building a Modern Computer from First Principles
  17. Code: The Hidden Language of Computer Hardware and Software

    Philosophy of Programming

  18. Making Software: What Really Works, and Why We Believe It
  19. Beautiful Code: Leading Programmers Explain How They Think
  20. The Elements of Programming Style
  21. A Discipline of Programming
  22. The Practice of Programming
  23. Computer Systems: A Programmer's Perspective
  24. Object Thinking
  25. How to Solve It by Computer
  26. 97 Things Every Programmer Should Know: Collective Wisdom from the Experts


  27. Hackers and Painters: Big Ideas from the Computer Age
  28. The Intentional Stance
  29. Things That Make Us Smart: Defending Human Attributes In The Age Of The Machine
  30. The Back of the Napkin: Solving Problems and Selling Ideas with Pictures
  31. The Timeless Way of Building
  32. The Soul Of A New Machine
  34. YOUTH
  35. Understanding Comics: The Invisible Art

    Software Engineering Skill Sets

  36. Software Tools
  37. UML Distilled: A Brief Guide to the Standard Object Modeling Language
  38. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development
  39. Practical Parallel Programming
  40. Past, Present, Parallel: A Survey of Available Parallel Computer Systems
  41. Mastering Regular Expressions
  42. Compilers: Principles, Techniques, and Tools
  43. Computer Graphics: Principles and Practice in C
  44. Michael Abrash's Graphics Programming Black Book
  45. The Art of Deception: Controlling the Human Element of Security
  46. SOA in Practice: The Art of Distributed System Design
  47. Data Mining: Practical Machine Learning Tools and Techniques
  48. Data Crunching: Solve Everyday Problems Using Java, Python, and more.


  49. The Psychology Of Everyday Things
  50. About Face 3: The Essentials of Interaction Design
  51. Design for Hackers: Reverse Engineering Beauty
  52. The Non-Designer's Design Book


  53. Micro-ISV: From Vision to Reality
  54. Death March
  55. Showstopper! the Breakneck Race to Create Windows NT and the Next Generation at Microsoft
  56. The PayPal Wars: Battles with eBay, the Media, the Mafia, and the Rest of Planet Earth
  57. The Business of Software: What Every Manager, Programmer, and Entrepreneur Must Know to Thrive and Survive in Good Times and Bad
  58. In the Beginning...was the Command Line

    Specialist Skills

  59. The Art of UNIX Programming
  60. Advanced Programming in the UNIX Environment
  61. Programming Windows
  62. Cocoa Programming for Mac OS X
  63. Starting Forth: An Introduction to the Forth Language and Operating System for Beginners and Professionals
  64. lex & yacc
  65. The TCP/IP Guide: A Comprehensive, Illustrated Internet Protocols Reference
  66. C Programming Language
  67. No Bugs!: Delivering Error Free Code in C and C++
  68. Modern C++ Design: Generic Programming and Design Patterns Applied
  69. Agile Principles, Patterns, and Practices in C#
  70. Pragmatic Unit Testing in C# with NUnit

    DevOps Reading List

  71. Time Management for System Administrators: Stop Working Late and Start Working Smart
  72. The Practice of Cloud System Administration: DevOps and SRE Practices for Web Services
  73. The Practice of System and Network Administration: DevOps and other Best Practices for Enterprise IT
  74. Effective DevOps: Building a Culture of Collaboration, Affinity, and Tooling at Scale
  75. DevOps: A Software Architect's Perspective
  76. The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations
  77. Site Reliability Engineering: How Google Runs Production Systems
  78. Cloud Native Java: Designing Resilient Systems with Spring Boot, Spring Cloud, and Cloud Foundry
  79. Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation
  80. Migrating Large-Scale Services to the Cloud
u/100hp100armour · 1 pointr/sysadmin

It sounds like you're trying to use technology to solve a problem that correct and useful documentation and processes would solve.

You don't want your team to have to re-invent the wheel every-time a patch is required.

Here is a useful book I would recommend.


u/Kynaeus · 1 pointr/sysadmin

Good for you, you're seeking out your knowledge and it sounds like you're dedicated to learning as well.

You won't get a good sense of what we do alone, especially because it is a very diverse field and can include specializations in storage, virtualization, databases, helpdesk, desktop support, mobile device management, security (which in itself has a number of specializations), operations, project management, monitoring and reporting, copper and fiber networking, firewall management, programming or developing... See my point? You can read a little more on the fields here

Anyway, if your computer is capable I would suggest you at least familiarize yourself with SOME of what we do, try and get Hyper-V running and learn some of the Powershell commands for interacting with the VMs, then use those VMs to run some *nix stuff and learn how to use those.

There is honestly a ton of free stuff, books, documentation and such available for you, you just have to know where to look and what you might want to see. The search bar here sucks but use the google advanced search for this subreddit and there is a ton of stuff to find, here's a few examples you may find useful: