SPOF - Single "Person" of Failure
24 likes5,653 views
The document discusses the concept of a single point of failure (SPOF) in systems, emphasizing the importance of high availability and redundancy to prevent system shutdowns due to component failures. It also highlights the risks associated with having single admins and the need for role-based access and documentation to mitigate these risks. The speaker advocates for a balanced approach to work, including mandatory vacation, to maintain productivity and prevent burnout.
SPOF - Single "Person" of Failure
- 1. Single Point of Failure… Expert Sasha Rosenbaum, @DivineOps
- 2. Who am I? Sasha Rosenbaum Azure & DevOps consultant at 10th Magnitude for 4 years Co-organizer of - DevOps Days Chicago Conference - Chicago Azure meetup @DivineOps
- 3. What is a Single Point of Failure? @DivineOps
- 4. A single point of failure (SPOF) is a part of a system that, if it fails, will stop the entire system from working @DivineOps
- 5. High Availability Achieving redundancy by removing single points of failure Having reliable cross-over capabilities to switch between components Detection of failures as they occur, so that cross-over can be initiated @DivineOps
- 8. How is the entire system down? @DivineOps
- 9. We forgot a dependency! @DivineOps
- 10. Oh… @DivineOps
- 11. Just imagine buying a server that Uptime of roughly 16 hours a day With interruptions Single one of its kind Cannot be replicated! @DivineOps
- 12. Humans are NOT highly available @DivineOps
- 13. How did we get here? Lack of budget Lack of people Human nature @DivineOps
- 14. How to recognize that you have a problem? @DivineOps
- 15. 1 @DivineOps
- 16. Keys to the Kingdom @DivineOps
- 17. TO MY PRODUCTION SERVER @DivineOps
- 18. Even when the systems are automated there are still humans who manage them @DivineOps
- 19. Why is there a single admin? The situation evolved organically from having a small team Someone took over deliberately @DivineOps
- 20. Role Based Access Grant access based on a role/group Admin group size > 1 Service accounts @DivineOps
- 21. Make sure that the person on call has the necessary access to fix the problem @DivineOps
- 23. 2 @DivineOps
- 24. Beware of the Expert! @DivineOps
- 25. “This will take 15 minutes to fix And 8 hours to explain” @DivineOps
- 26. We cannot afford the loss of productivity! @DivineOps
- 27. Can you afford losing this knowledge? @DivineOps
- 29. Juniors are wonderful people They ask tough questions @DivineOps
- 30. Your new hires haven’t yet caught the “This is how it’s always been” virus @DivineOps
- 31. You are emotionally invested in your code It is hard not to get protective of it @DivineOps
- 33. 3 @DivineOps
- 34. “I cannot afford to take vacation!” @DivineOps
- 38. Research shows that working longer hours DOES NOT increase productivity @DivineOps
- 39. You need rest to be at your best! @DivineOps
- 40. Cell phones are the single worse thing that happened to people AND businesses in the last century @DivineOps
- 41. If people were actually unreachable we would find a more reliable way to solve problems @DivineOps
- 44. Say NO to having a Single PERSON of Failure ;-) @DivineOps
- 45. Great job, DoD Silicon Valley! @DivineOps