the way we build applications is changing
play

The way we build applications is changing: The way we understand - PowerPoint PPT Presentation

The way we build applications is changing: The way we understand and manage them needs to change too Adrian Colyer, Accel @adriancolyer In association with Agenda How we got here The rules have changed Where were heading?


  1. The way we build applications is changing: The way we understand and manage them needs to change too Adrian Colyer, Accel @adriancolyer In association with

  2. Agenda • How we got here • The rules have changed • Where we’re heading…?

  3. Some buzzwords Cloud native Kubernetes microservices serverless

  4. Some buzzwords Cloud native Kubernetes microservices serverless

  5. Focus on delivery of value

  6. Optimising for throughput and latency

  7. Things become finer-grained over time Image credit: Khan Academy, “Introduction to Integral Calculus”

  8. Shift left

  9. Shift left means… • In the loop, not after the loop • For the many, not the few • Taking an application/service perspective

  10. WHERE HAS ALL THE THE RIVER COMPLEXITY GONE? Consequences EMERGENT GRAY FAILURES BEHAVIOURS

  11. https://www.complexityexplorer.org/courses/105-introduction-to-dynamical-systems-and-chaos • Bifurcations • Randomness • Stable averages, unstable details • Complex emergent behaviours

  12. The rules have changed

  13. Instrument rated Image credit: “5 3 Visual Flight Rules”, Robert Kowalksi. https://www.youtube.com/watch?v=r7u 8zj9m7EU

  14. “Embrace Complexity, Scale Agility”, Dave Snowdon 2015 https://www.youtube.com/watch?v=lYlqhvzI_VQ&feature=youtu.be

  15. Where we’re heading…

  16. Some challenges • Raising the level of abstraction • Rethinking design assumptions (especially relating to hardware advances) • Software supply chain • Sustainable OSS • Increasing automation • Interpretability • Bias and Fairness • Operating at the limits

  17. Image Credit: Wikipedia (public domain)

  18. See also: “Above the Line, Below the Line”, Richard I. Cook, M.D., ACM Queue Vol 17, Issue 6

  19. APM as a sense- making instrument STAN as a ‘team player’

  20. Thank you. acolyer@accel.com @adriancolyer

  21. Q&A

  22. Selected Resources • Project to Product , Mik Kersten, 2018 • Resilience Engineering in practice , Hollnagel et al, 2010 • Value Stream Mapping , Martin & Osterling, 2013 • Ironies of Automa tion, Bainbridge 1983 • Accelerate State of DevOps Report , • Ten challenges for making automation a Forsgren 2019 team player in join human-agent activity, Klein et al., 2004 • Cynefin framework, see e.g.: Embrace Complexity, Scale Agility , Snowdon 2015 • Trade-offs under pressure: heuristics and observations of teams resolving internet • Introduction to dynamical systems and service outages , Allspaw 2015 chaos, Sante Fe Institute ‘Complexity Explorer’ • STELLA: report from the SNAFU-catchers workshop on coping with complexity , • Above the Line, Below the Line , Cook Woods 2017 2020 • Gray failure: the achilles heel of cloud- scale systems , Huang et al., 2017

Recommend


More recommend