Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Cloud Native London 2018 - Journeys To Cloud Na...

Nicki Watt
September 27, 2018

Cloud Native London 2018 - Journeys To Cloud Native Architecture: Sun, Sea And Emergencies

Nicki Watt

September 27, 2018
Tweet

More Decks by Nicki Watt

Other Decks in Technology

Transcript

  1. JOURNEYS TO 
 CLOUD NATIVE ARCHITECTURE: SUN, SEA AND EMERGENCIES

    Nicki Watt, CTO - OpenCredo
 @techiewatt 1
  2. @techiewatt ABOUT ME / OPENCREDO ▸CTO at OpenCredo ▸Hands on

    software development consultancy ▸Cloud Native; Data Engineering & ML !4
  3. @techiewatt THE CLOUD NATIVE DREAM (BUSINESS DRIVERS) !8 Micro
 services

    CI / 
 CD DevOps Containers Uses Cloud Native
 Architecture … Tools & Techniques
  4. @techiewatt ▸Faster Time to 
 Market ▸Allow business to grow

    (Scalability) THE CLOUD NATIVE DREAM (BUSINESS DRIVERS) !9 Micro
 services CI / 
 CD DevOps Containers Uses Business
 Objectives Cloud Native
 Architecture To
 Achieve … Tools & Techniques Cost also a factor …
  5. @techiewatt !10 Micro
 services CI / 
 CD DevOps Containers

    Uses Business
 Objectives Cloud Native
 Architecture To
 Achieve THE CLOUD NATIVE DREAM (BUSINESS DRIVERS) … Tools & Techniques People, Teams & Processes Impacts 
 On ▸Faster Time to 
 Market ▸Allow business to grow (Scalability) Cost also a factor …
  6. @techiewatt !17 #1 
 Sunburn (Tackling Too Much 
 Too

    Quickly) https://www.flickr.com/photos/timparkinson/1312737125
  7. @techiewatt ▸Taking on the world from day 1 ▸Compromise -

    Do minimum get away with ▸Operating under a false sense of security ▸Only happy path testing ▸Inconsistent environments ▸The single instance fallacy !18 TACKLING TOO MUCH, TOO QUICKLY Can’t expect to gain a 
 fully rounded & reliable 
 cloud native system overnight!
  8. @techiewatt ▸Quality is Compromised ▸Pain is delayed - focusing on

    easy not risky ▸Operate under a false sense of security ▸Only happy path testing (platform testing neglected) ▸Lack of robust CI/CD - Inconsistent environments ▸ !20 TACKLING TOO MUCH, TOO QUICKLY - OBSERVATIONS
  9. @techiewatt ▸Quality is Compromised ▸Pain is delayed - focusing on

    easy not risky ▸Operate under a false sense of security ▸Only happy path testing (platform testing neglected) ▸Lack of robust CI/CD - Inconsistent environments ▸ !21 image credit: http:// www.guinnessworldrec ords.com/world- records/most-tennis- balls-held-in-the- mouth-dog TACKLING TOO MUCH, TOO QUICKLY - OBSERVATIONS
  10. @techiewatt ▸Quality is Compromised ▸Pain is delayed - focusing on

    easy not risky ▸Operate under a false sense of security ▸Only happy path testing (platform testing neglected) ▸Lack of robust CI/CD - Inconsistent environments ▸ !22 TACKLING TOO MUCH, TOO QUICKLY - OBSERVATIONS
  11. @techiewatt ▸Quality is Compromised ▸Pain is delayed - focusing on

    easy not risky ▸Operate under a false sense of security ▸Only happy path testing (platform testing neglected) ▸Lack of robust CI/CD - Inconsistent environments ▸ !23 TACKLING TOO MUCH, TOO QUICKLY - OBSERVATIONS
  12. @techiewatt !26 #2 
 Caught In Deep Water (Relying on

    a 
 Surface Level Understanding)
  13. @techiewatt ▸Taking on the world from day 1 ▸Compromise -

    Do minimum get away with ▸Operating under a false sense of security ▸Only happy path testing ▸Inconsistent environments ▸The single instance fallacy !27 Distributed Systems are hard. 
 The devil is in the detail
 And the detail matters RELYING ON A SURFACE LEVEL UNDERSTANDING
  14. @techiewatt ▸Skills & Real World Experience ▸Kubernetes in 24 hours

    != Expert ▸Outsource commodity, in-house business value ▸Missing out on optimising for the Bigger Picture ▸Artificial Boundaries ▸Artificial Centralisation !28 RELYING ON A SURFACE LEVEL UNDERSTANDING
  15. @techiewatt ▸Skills & Real World Experience ▸Kubernetes in 24 hours

    != Expert ▸Outsource commodity, in-house business value ▸Missing out on optimising for the Bigger Picture ▸Artificial Boundaries ▸Artificial Centralisation !29 RELYING ON A SURFACE LEVEL UNDERSTANDING
  16. @techiewatt !31 ▸Skills & Real World Experience ▸Kubernetes in 24

    hours != Expert ▸Outsource commodity, in-house business value ▸Missing out on optimising for the Bigger Picture ▸Artificial Boundaries ▸Artificial Centralisation RELYING ON A SURFACE LEVEL UNDERSTANDING
  17. @techiewatt !32 ▸Other War Stories … ▸DRY Dependency Hell ▸The

    Singularity Fallacy ▸Shallow Data (ref John Allspaw) RELYING ON A SURFACE LEVEL UNDERSTANDING
  18. @techiewatt !33 Gain basic skills & expertise 
 
 Make

    commodity problems 
 somebody else’s Learn by 
 Optimising for the bigger picture RELYING ON A SURFACE LEVEL UNDERSTANDING
  19. @techiewatt !34 #3 
 Susie & Jacob 
 assd asda


    d (Ineffective Tools & Processes)
  20. @techiewatt !35 #3 
 Between a rock 
 and a

    hard 
 place (Ineffective Tools & Processes)
  21. @techiewatt ▸Often traditional tools just don’t cut it ▸Mileage varies

    … ▸Slow you down ▸Take you the long way round ▸Downright hurt you in long run !37 INEFFECTIVE TOOLS & PROCESSES
  22. @techiewatt !38 ▸Mileage varies … ▸Slow you down ▸Take you

    the long way round ▸Downright hurt you in long run ▸More Forward Looking INEFFECTIVE TOOLS & PROCESSES
  23. @techiewatt !39 ▸Slow you down ▸Unnecessarily Heavy tooling 
 (Some

    Enterprise Databases, 
 Base Container Images) INEFFECTIVE TOOLS & PROCESSES
  24. @techiewatt !40 INEFFECTIVE TOOLS & PROCESSES ▸Take you the long

    way around ▸DIY or “Build Your Own” category
  25. @techiewatt !41 INEFFECTIVE TOOLS & PROCESSES ▸Downright hurt you ▸No

    API ▸Non Automatable ▸Horizontally challenged
  26. @techiewatt ▸Taking on the world from day 1 ▸Compromise -

    Do minimum get away with ▸Operating under a false sense of security ▸Only happy path testing ▸Inconsistent environments ▸The single instance fallacy !44 Considered Thought & Pragmatism …
 (CNCF Recommendations - good start) Rule of Thumb: 
 Automation, API & Horizontally scale friendly INEFFECTIVE TOOLS & PROCESSES - SO WHAT SHOULD YOU USE?
  27. @techiewatt !47 IGNORING SECURITY CONCERNS ▸Enterprise Security has not kept

    up ▸No excuse to ignore it though! ▸Devs/Ops are the new Gatekeepers ▸Help a CISO, help yourself ▸Provide tools/reports to help understand new world ▸Shift Security Left, make it a 1st class citizen
  28. @techiewatt !48 IGNORING SECURITY CONCERNS ▸Enterprise Security has not kept

    up ▸No excuse to ignore it though! ▸Devs/Ops are the new Gatekeepers ▸Help a CISO, help yourself ▸Provide tools/reports to help understand new world ▸Shift Security Left, make it a 1st class citizen DevOps CI CD
  29. @techiewatt ▸Shift Security Left ▸No excuse to ignore it though!

    ▸Devs/Ops are the new Gatekeepers ▸Help a CISO, help yourself ▸Provide tools/reports to help understand new world ▸Shift Security Left, make it a 1st class citizen !49 IGNORING SECURITY CONCERNS DevSecOps <— Shifting Security to the left <— Shift Security Left
  30. @techiewatt ▸Get Security Insight Out ▸No excuse to ignore it

    though! ▸Devs/Ops are the new Gatekeepers ▸Help a CISO, help yourself ▸Provide tools/reports to help understand new world ▸Shift Security Left, make it a 1st class citizen !50 IGNORING SECURITY CONCERNS DevSecOps <— Shifting Security to the left Get Security Insight Out —> Deploy Security Runtime Security
  31. @techiewatt ▸Get Security Insight Out ▸Help a CISO, help yourself

    ▸Provide tools/reports to help understand 
 new world ▸Help a CISO, help yourself ▸Provide tools/reports to help understand new world ▸Shift Security Left, make it a 1st class citizen !51 IGNORING SECURITY CONCERNS
  32. @techiewatt ▸Taking on the world from day 1 ▸Compromise -

    Do minimum get away with ▸Operating under a false sense of security ▸Only happy path testing ▸Inconsistent environments ▸The single instance fallacy !53 <— Shift Security Left Get Security Insights Out —> Engage don’t enrage! IGNORING SECURITY CONCERNS
  33. @techiewatt !55 NOT ANTICIPATING FAILURE ▸Test app & platform level

    sad paths ▸Observability ▸Chaos Engineering ▸Optimise for Recovery & Learning!
  34. @techiewatt !56 NOT ANTICIPATING FAILURE ▸Test app & platform level

    sad paths ▸Observability ▸Chaos Engineering ▸Optimise for Recovery & Learning!
  35. @techiewatt !57 NOT ANTICIPATING FAILURE ▸Test app & platform level

    sad paths ▸Observability ▸First address unnecessary Chaos …
 then do … Chaos Engineering ▸Optimise for Recovery & Learning!
  36. @techiewatt !58 NOT ANTICIPATING FAILURE ▸Test app & platform level

    sad paths ▸Observability ▸First address unnecessary Chaos …
 then do … Chaos Engineering ▸Optimise for Recovery!
  37. @techiewatt !61 ▸Needs A Different ▸Approach ▸Tooling ▸Skills THE CLOUD

    NATIVE JOURNEY Micro
 services CI / 
 CD DevOps Containers Uses Business
 Objectives Cloud Native
 Architecture To
 Achieve … Tools & Techniques People, Teams & Processes Impacts 
 On !61
  38. @techiewatt !63 PRINCIPLES FOR SUCCESS ▸ Don’t take on too

    much too quickly ▸ Acquire enough expertise to journey safely ▸ Choose your Tools wisely ▸ Engage don’t enrage Security ▸ Anticipate, Plan and Actively Test for Failure
  39. @techiewatt !64 Thanks! @techiewatt Get in touch if you’re looking

    for a partner to help on your Cloud Native Journey!