Practicalities of Productionizing Distributed Systems

Practicalities of Productionizing Distributed Systems

GOTO Conferences via YouTube Direct link

Intro

1 of 31

1 of 31

Intro

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Practicalities of Productionizing Distributed Systems

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

  1. 1 Intro
  2. 2 Why you should listen to me
  3. 3 Quick foundation
  4. 4 What makes distributed systems different
  5. 5 A subset of failures
  6. 6 Clients stuck to an overloaded process
  7. 7 Partial failure
  8. 8 "It's slow" is the hardest problem you'll ever debug
  9. 9 Create partial availability
  10. 10 "Who to Follow" in the monorail
  11. 11 Knowing what the system has done
  12. 12 Percentiles, not averages
  13. 13 Tracing
  14. 14 On profiling
  15. 15 Releases should change a metric
  16. 16 Free-form logs are liars
  17. 17 Common "problems" are overlogged
  18. 18 Uncommon problems
  19. 19 Avoid coordination
  20. 20 Backpressure
  21. 21 Dropping new messages on the floor
  22. 22 Returning "overload" error responses
  23. 23 Timeouts and exponential back-offs
  24. 24 Roll out infrastructure with feature flags
  25. 25 if (Decider.available..)
  26. 26 Multiple versions are the norm
  27. 27 Datacenter schedulers are worth it
  28. 28 Collaboration is politics
  29. 29 No time-traveling stalkers
  30. 30 moral necessity
  31. 31 Data minimization is a

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.