Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

What is Cloud Native and why should I care

220 views

Published on

Presented at DevOpsDays Warsaw.

Abstract:
We hear a lot about building cloud native applications and platforms. But what does it really mean? Is it just about using a public cloud? Or is it relevant when you want to benefit from microservices architecture? And how is it related to DevOps? I will try to dig into what are the reasons why Cloud Native is worth investing our time. And also what are the patterns of it and how can we benefit from them.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

What is Cloud Native and why should I care

  1. 1. What is Cloud Native and why should I care? Tomasz Tarczyński, Gigaset @ttarczynski
  2. 2. @ttarczynski Cloud Native
  3. 3. Gigaset elements @ttarczynski
  4. 4. Gigaset elements @ttarczynski
  5. 5. Gigaset elements @ttarczynski
  6. 6. Requirements of IoT Backend 1. Reliability @ttarczynski
  7. 7. Requirements of IoT Backend 1. Reliability 2. Velocity @ttarczynski
  8. 8. Evolution of IoT Backend 1. Containers @ttarczynski
  9. 9. Evolution of IoT Backend 1. Containers 2. Microservices @ttarczynski
  10. 10. Evolution of IoT Backend 1. Containers 2. Microservices 3. Automation @ttarczynski
  11. 11. Evolution of IoT Backend 1. Growing number of apps @ttarczynski
  12. 12. Evolution of IoT Backend 1. Growing number of apps 2. Automation with puppet @ttarczynski
  13. 13. Evolution of IoT Backend 1. Growing number of apps 2. Automation with puppet 3. Puppet is host-centric @ttarczynski
  14. 14. Alternative Need for orchestration @ttarczynski
  15. 15. How is it defined?
  16. 16. WHY Cloud Native?
  17. 17. Case Studies
  18. 18. Case study: Financial Times https://container-solutions.com/study-tech-transformation-financial-times/
  19. 19. Case study: Financial Times Before After Change Rollback ratio 20% 0.1% 200x Lead time Deployment frequency https://container-solutions.com/study-tech-transformation-financial-times/
  20. 20. Case study: Financial Times Before After Change Rollback ratio 20% 0.1% 200x Lead time 120 days 15 min 4000x Deployment frequency https://container-solutions.com/study-tech-transformation-financial-times/
  21. 21. Case study: Financial Times Before After Change Rollback ratio 20% 0.1% 200x Lead time 120 days 15 min 4000x Deployment frequency 12 / year 2000 / year 170x https://container-solutions.com/study-tech-transformation-financial-times/
  22. 22. Case study: Financial Times https://kccnceu18.sched.com/speaker/sarah.wells1
  23. 23. Case study: Gigaset Before After Change Rollback ratio 40% 1% 40x MTTR Lead time @ttarczynski
  24. 24. Case study: Gigaset Before After Change Rollback ratio 40% 1% 40x MTTR 8 hours 15 min 32x Lead time @ttarczynski
  25. 25. Case study: Gigaset Before After Change Rollback ratio 40% 1% 40x MTTR 8 hours 15 min 32x Lead time 60 days 2 hours 240x @ttarczynski
  26. 26. 2018 State of DevOps Report https://cloudplatformonline.com/2018-state-of-devops.html
  27. 27. WHY Cloud Native? @ttarczynski 1. Reliability
  28. 28. WHY Cloud Native? @ttarczynski 1. Reliability 2. Velocity
  29. 29. https://www.slideshare.net/AmazonWebServices/dmg206
  30. 30. WHY Cloud Native? @ttarczynski 1. Reliability 2. Velocity 3. Efficiency
  31. 31. HOW?
  32. 32. Containers
  33. 33. Dynamic Management
  34. 34. Microservices
  35. 35. Cloud Native: A Technological Paradigm 1. Containers 2. Dynamic Management 3. Microservices @ttarczynski
  36. 36. 12 Factor Apps https://12factor.net/ # Factor I Codebase One codebase in version control, many deploys II Dependencies Explicitly declare and isolate dependencies III Config Store configuration in the environment IV Backing services Treat backing services as attached resources V Build, release, run Strictly separate build and run stages VI Processes One or more stateless processes
  37. 37. 12 Factor Apps https://12factor.net/ # Factor VII Port binding Export services via port binding VIII Concurrency Scale out via the process model IX Disposability Fast startup and graceful shutdown X Dev/Prod parity Dev / stg / prod as similar as possible XI Logs Treat logs as event streams XII Admin Processes Admin tasks as one-off processes
  38. 38. Cloud Native: Infrastructure Useful Abstractions @ttarczynski
  39. 39. Cloud Native: Infrastructure Infrastructure Managed by Software @ttarczynski
  40. 40. Cloud Native: Applications Applications Managed by Software @ttarczynski
  41. 41. Cloud Native and DevOps Should we forget about DevOps? @ttarczynski
  42. 42. Cloud Native and DevOps DevOps “A cultural and professional movement” “Focused on high velocity” Adam Jacob: https://chef.github.io/devops-kungfu/
  43. 43. Cloud Native and DevOps Coulture Automation Measurement Sharing John Willis: http://itrevolution.com/devops-culture-part-1/
  44. 44. Coulture Automation Measurement Sharing Cloud Native and DevOps John Willis: http://itrevolution.com/devops-culture-part-1/
  45. 45. Cloud Native Is this all new? @ttarczynski
  46. 46. Cloud Native: History @ttarczynski Containers: 2006 – cgroups started at Google 2008 – cgroups in Linux kernel mainline (v2.6.24) 2008 – LXC (Linux Containers) 2013 – Docker
  47. 47. Cloud Native: History @ttarczynski Orchestration: 200X – Google Borg 2009 – Mesos project started 2010 – Twitter using Mesos 2014 – Kubernetes release
  48. 48. Cloud Native: History @ttarczynski Cloud / Microservices: 2006 – AWS with: S3, SQS, EC2 2006 –“You build it, you run it” – Werner Vogels 2010 – Amazon moves all retail to AWS 2010 – Netflix moved to AWS 2010 – Netflix OSS started 2011 – 12 Factor apps
  49. 49. Cloud Native: Today @ttarczynski
  50. 50. Thanks!

×