Why Are Distributed Systems So Hard?

Why Are Distributed Systems So Hard?

USENIX via YouTube Direct link

Designing Systems for Humans

45 of 46

45 of 46

Designing Systems for Humans

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Why Are Distributed Systems So Hard?

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Introduction
  2. 2 Agenda
  3. 3 Storytime
  4. 4 Data Evolution
  5. 5 Scaling
  6. 6 Cloud Computing
  7. 7 Why Scale Horizontally
  8. 8 What Does It Mean To Run A Distributed System
  9. 9 A Node On Distributed Computing
  10. 10 Summary
  11. 11 Shared Nothing Architecture
  12. 12 Unreliable Message Delivery
  13. 13 Why Are We Fenced Off
  14. 14 Building Observability
  15. 15 What We Can Know
  16. 16 The Cap Theorem
  17. 17 C
  18. 18 Replication Lag
  19. 19 Consistency is a Spectrum
  20. 20 Availability is Not Binary
  21. 21 Partition Tolerance
  22. 22 Hardware
  23. 23 Hardware Failure
  24. 24 Cables
  25. 25 Sharks
  26. 26 Kevlar
  27. 27 Network Partitions
  28. 28 Resource Isolation
  29. 29 Process Suspension
  30. 30 Network Glitch
  31. 31 People do bad things
  32. 32 Why does this matter
  33. 33 Practical reality
  34. 34 The correctness result
  35. 35 Mitigation strategies
  36. 36 Consensus Algorithms
  37. 37 The Woods Theorem
  38. 38 Building Mental Models
  39. 39 Incident Analysis
  40. 40 Blameless Discussions
  41. 41 Mental Models
  42. 42 Human Failure
  43. 43 Alert Fatigue
  44. 44 User Mindsets
  45. 45 Designing Systems for Humans
  46. 46 HugOps

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.