Where's the value in Cloud Native

33a8eda64dec30551fd0b474443e4b35?s=47 Armakuni
September 04, 2018

Where's the value in Cloud Native

Whether you're a developer or a manager we will give you a framework to decide which cloud native practices you should adopt today. We explain the practicalities of implementing three high value cloud native practices, both from an implementation perspective, and the perspective of someone having to sell them to the wider organisation.

33a8eda64dec30551fd0b474443e4b35?s=128

Armakuni

September 04, 2018
Tweet

Transcript

  1. 1.

    Where's the value in Cloud Native High value cloud native

    practices, and how to sell them to your boss
  2. 2.

    Who are we Billie Thompson Cloud Native Consultant at Armakuni

    @PurpleBooth Zenon Hannick COO at Armakuni @ZenonHannick
  3. 8.
  4. 9.
  5. 10.
  6. 11.
  7. 12.

    Key Values: Raw • Lead Time • Process Time •

    Complete & Accurate • Number of Dependant Systems
  8. 14.

    Key Values: Observed • Work that falls outside VSM (Unplanned

    Work) • Variance in PT • Variance in LT • Common adjectives ◦ “Confusing” ◦ “Fast” ◦ “Boring”
  9. 18.

    Manager • The (difficult) conversation • Shared understanding & agreement

    • Identifies best areas to focus effort • Shows flow of value! • Numbers & Data • Allows you to track progress • Can set future desired state
  10. 19.

    Objection! • I can’t get everyone together ◦ Gather the

    statistics one to one • I don’t know all the times ◦ Find someone who does ◦ Educated guess ◦ Dig it out of a tool ▪ VCS ▪ Deployment Tool ▪ Ticketing System
  11. 22.

    The Symptoms • Merging processes • Test Deployment processes ◦

    High PT • Deployment processes ◦ High LT ◦ High PT ◦ Low C&A ◦ High Variance of LT
  12. 23.
  13. 24.
  14. 26.

    Practitioner • Building software vs Building a system • We

    share the codebase • My laptop won’t fit in a server rack • Oops I forgot to… ◦ Run the tests ◦ Check the migrations ◦ Run the security tests ◦ etc
  15. 27.

    Manager • Visualises flow of code (value) • Encourages constant

    flow • Speed • Smaller batch sizes • Reduces risk • Fully auditable trail
  16. 28.

    Objection! • I need to press a button ◦ Illusion

    of confidence in manual step ◦ Lack of trust in automated testing • I need to review changes • Governance ◦ Pipeline automatically provides audit trail ◦ Can automate governance checks as part of the pipeline • Security ◦ Add to pipeline
  17. 30.

    The Symptoms • Deployment Process ◦ High LT ◦ High

    PT ◦ Poor C&A • Unplanned Work ◦ That happens at 3am ◦ Easily recoverable errors ◦ Scaling • Large % of time & effort operating platform/infrastructure, (i.e. non-value adding work)
  18. 31.
  19. 32.
  20. 35.

    Practitioner • No need to learn about servers • My

    code, my responsibility • Prototyping is easy • I no longer need to think about: ◦ Reliability ◦ Scaling ◦ Monitoring
  21. 36.

    Manager • Focus on business value delivery • Abstracts complexity

    • Standardise across organisation • Software delivery practices for platforms • Turns platform team into a product team • Speed • Less things for people to worry about
  22. 37.

    Objection! • I need to know everything that is going

    on! • I need to control the whole stack • We are very special unique snowflake
  23. 39.

    The Symptoms • Development processes ◦ High variance ◦ Poor

    C&A • Common Adjectives ◦ “Confusing” ◦ “Complicated” • Unplanned work ◦ Misunderstanding system ◦ Wrong prioritization
  24. 40.
  25. 41.
  26. 42.
  27. 43.

    The nitty gritty Set some additional headers, with HTTP: •

    X-B3-TraceId • X-B3-ParentSpanId • X-B3-SpanId • X-B3-Sampled or X-B3-Flags (Or a bunch of other alternatives) Optionally an API call to the OpenTracing service.
  28. 45.

    Practitioner • What calls what is no longer a mystery

    • Makes me think about users • O(n) calls become really obvious • I can prove it!
  29. 46.

    Manager • Observability • Evidence of areas needing improvement •

    Enables association of user activity to system activity