Goto Chicago 2019 - Journeys To Cloud Native Architecture: Sun, Sea And Emergencies

Talk given at Goto Chicago 2019. https://gotochgo.com/2019/sessions/715

Transcript

1. JOURNEYS TO CLOUD NATIVE ARCHITECTURES Nicki Watt - CTO @techiewatt SUN, SEA & EMERGENCIES
2. @techiewatt How do you learn? How do you decide what works, and what doesn’t?
3. @techiewatt Feeling pain Learning from failures
4. @techiewatt JOURNEYS TO CLOUD NATIVE ARCHITECTURES SUN, SEA & EMERGENCIES
5. @techiewatt JOURNEYS TO CLOUD NATIVE ARCHITECTURES SUN, SEA & EMERGENCIES
6. @techiewatt ABOUT ME / OPENCREDO • CTO at OpenCredo • Hands on software development consultancy • Cloud Native; Data Engineering & ML
7. AGENDA OVERVIEW • OVERVIEW - THE DREAM • ISSUES & CHALLENGES • CONCLUSION @techiewatt
8. @techiewatt Overview - The Dream
9. @techiewatt
10. @techiewatt THE CLOUD NATIVE DREAM (BUSINESS DRIVERS) Micro
 services CI / 
 CD DevOps Containers Uses Cloud Native
 Architecture … Tools & Techniques
11. @techiewatt ▸Faster Time to 
 Market ▸Allow business to grow (Scalability) THE CLOUD NATIVE DREAM (BUSINESS DRIVERS) Micro
 services CI / 
 CD DevOps Containers Uses Business
 Objectives Cloud Native
 Architecture To
 Achieve … Tools & Techniques
12. @techiewatt 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)
13. @techiewatt “Going Cloud-Native” is an approach to build and run applications capable of exploiting and taking advantage of modern, scalable cloud like delivery techniques and tools in order to meet business objectives!
14. @techiewatt Check In …
15. @techiewatt Underlying Challenge:
 
 Too Much 
 Baggage Photo by Laura Gilmore (Flickr)
16. @techiewatt ▸Needs A Different ▸Approach ▸Tooling ▸Skills THE CLOUD NATIVE JOURNEY Photo by Laura Gilmore (Flickr)
17. @techiewatt Departure …
 Arrival …
 The Holiday Begins …
18. @techiewatt Issues & Challenges
19. @techiewatt #1 
 The Jones’
20. @techiewatt #1 
 Tackling Too Much 
 Too Quickly (Sunburn)
21. @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 TACKLING TOO MUCH, TOO QUICKLY Can’t expect to gain a 
 fully rounded & reliable 
 cloud native system overnight!
22. @techiewatt • Many Moving Parts • App Architecture • Ops • Infrastructure TACKLING TOO MUCH, TOO QUICKLY
23. @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 • TACKLING TOO MUCH, TOO QUICKLY - OBSERVATIONS
24. @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 • image credit: http:// www.guinnessworldrec ords.com/world- records/most-tennis- balls-held-in-the- mouth-dog TACKLING TOO MUCH, TOO QUICKLY - OBSERVATIONS
25. @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 • TACKLING TOO MUCH, TOO QUICKLY - OBSERVATIONS
26. @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 • TACKLING TOO MUCH, TOO QUICKLY - OBSERVATIONS
27. @techiewatt Slow Down Take Baby Steps Focus On Quality! TACKLING TOO MUCH, TOO QUICKLY
28. @techiewatt #2 
 Deepak and 
 friends
29. @techiewatt #2 
 Relying on a 
 Surface Level Understanding (Caught In Deep Water)
30. @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 Distributed Systems are hard. 
 The devil is in the detail
 And the detail matters RELYING ON A SURFACE LEVEL UNDERSTANDING
31. @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 RELYING ON A SURFACE LEVEL UNDERSTANDING
32. @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 RELYING ON A SURFACE LEVEL UNDERSTANDING
33. @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 RELYING ON A SURFACE LEVEL UNDERSTANDING
34. @techiewatt • Other War Stories … • DRY Dependency Hell • The Singularity Fallacy • Shallow Data (ref John Allspaw) RELYING ON A SURFACE LEVEL UNDERSTANDING
35. @techiewatt Gain basic skills & expertise 
 
 Make commodity problems 
 somebody else’s Learn by 
 Optimising for the bigger picture RELYING ON A SURFACE LEVEL UNDERSTANDING
36. @techiewatt #3 
 Susie & Jacob 

37. @techiewatt #3 
 Ineffective Tools & Processes (Between a rock and a hard place)
38. @techiewatt Me Simultaneously petrified & enjoying myself …
39. @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 INEFFECTIVE TOOLS & PROCESSES
40. @techiewatt • Mileage varies … • Slow you down • Take you the long way round • Downright hurt you in long run • More Forward Looking INEFFECTIVE TOOLS & PROCESSES
41. @techiewatt • Slow you down • Unnecessarily Heavy tooling 
 (Some Enterprise Databases, 
 Base Container Images) INEFFECTIVE TOOLS & PROCESSES
42. @techiewatt INEFFECTIVE TOOLS & PROCESSES • Take you the long way around • DIY or “Build Your Own” category
43. @techiewatt INEFFECTIVE TOOLS & PROCESSES • Downright hurt you • No API • Non Automatable • Horizontally challenged
44. @techiewatt • More forward looking … • Imperative —> Declarative
 
 INEFFECTIVE TOOLS & PROCESSES
45. @techiewatt INEFFECTIVE TOOLS & PROCESSES - SO WHAT SHOULD YOU USE? Guidance from 
 CNCF
46. @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 Considered Thought & Pragmatism …
 (CNCF Recommendations - good start) Rule of Thumb: 
 Automation, API & Horizontally scale friendly INEFFECTIVE TOOLS & PROCESSES - SO WHAT SHOULD YOU USE?
47. @techiewatt #4 
 The Smiths’ @techiewatt
48. @techiewatt #4 
 Ignoring 
 Security (Living Dangerously)
49. @techiewatt 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
50. @techiewatt 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
51. @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 IGNORING SECURITY CONCERNS DevSecOps <— Shifting Security to the left <— Shift Security Left
52. @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 IGNORING SECURITY CONCERNS DevSecOps <— Shifting Security to the left Get Security Insight Out —> Deploy Security Runtime Security
53. @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 IGNORING SECURITY CONCERNS
54. @techiewatt
55. @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 <— Shift Security Left Get Security Insights Out —> Engage don’t enrage! IGNORING SECURITY CONCERNS
56. @techiewatt #5 
 Thandi
 Failure (The Unexpected
 Accident)
57. @techiewatt #5 
 Not Anticipating Failure (The Unexpected
 Accident)
58. @techiewatt NOT ANTICIPATING FAILURE • Test app & platform level sad paths • Observability • Chaos Engineering • Optimise for Recovery & Learning!
59. @techiewatt NOT ANTICIPATING FAILURE • Test app & platform level sad paths • Observability • Chaos Engineering • Optimise for Recovery & Learning!
60. @techiewatt NOT ANTICIPATING FAILURE • Test app & platform level sad paths • Observability • First address unnecessary Chaos …
 then do … Chaos Engineering • Optimise for Recovery & Learning!
61. @techiewatt NOT ANTICIPATING FAILURE • Test app & platform level sad paths • Observability • First address unnecessary Chaos …
 then do … Chaos Engineering • Optimise for Recovery!
62. @techiewatt Failure is only really failure
 if you fail to learn from it
63. @techiewatt Summary & 
 Principles for 
 Success
64. @techiewatt Micro
 services CI / 
 CD DevOps Containers Uses Business
 Objectives Cloud Native
 Architecture To
 Achieve … Tools & Techniques People, Teams & Processes Impacts 
 On !67 • Needs A Different • Approach • Tooling • Skills THE CLOUD NATIVE JOURNEY
65. @techiewatt • Needs To Cohesively Address: • App Architecture • Ops • Infrastructure THE CLOUD NATIVE JOURNEY
66. @techiewatt 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
67. @techiewatt Thanks! @techiewatt Get in touch if you’re looking for a partner to help on your Cloud Native Journey!