$30 off During Our Annual Pro Sale. View Details »

Observability and Control Theory

Piyush Verma
November 16, 2019

Observability and Control Theory

Piyush Verma

November 16, 2019
Tweet

More Decks by Piyush Verma

Other Decks in Programming

Transcript

  1. Observability & Control Theory

  2. Question

  3. Question

  4. Question

  5. Monitoring!! Answer

  6. • You monitor what you know • You react after

    it has failed. • What about unknown-unknowns? • Doesn’t avoid failures. • Tells something broke and now it isn’t. • Always a comparative operator. Question: What is Monitoring?
  7. • Systems are Distributed. • What about? ◦ Accuracy ◦

    Latency ◦ Correctness ◦ Consistency • It’s till or from Now. What are we missing?
  8. Monitoring Timeline Late 2000s • SOA Early 2010 • Microservices

    1990s • Servers 2000s • Monolith Now Lambda
  9. The REAL question If a tree falls in a forest

    and nobody heard it, did it make a sound?
  10. The REAL answer All falling trees yield Logs.

  11. Software, by default, is opaque. To debug & control a

    running system, you need observation pre-built.
  12. Observability

  13. Need - Debugging - Pattern Detection

  14. None
  15. Unlike monitoring, observability is not failure-centric. If your job allows,

    you can use it to understand system performance, just-like-that. ¯\_(ツ)_/¯
  16. Stability

  17. Control Theory

  18. Control Theory

  19. Example

  20. TCP Flow Control

  21. TCP Flow Control

  22. TCP Congestion Control

  23. TCP Congestion Control

  24. Practical Applications

  25. • Constrained Optimization Problems • Constraint Scaling Problems Practical Applications

  26. Auto-Scaling

  27. Cache

  28. Gateway

  29. Load-Balancer

  30. Progressive Streaming

  31. Software, by default, is opaque. To debug & control a

    running system, you need observation pre-built.
  32. Thank You - Piyush Verma