Cloud, das „New Normal“?

1. #WISSENTEILEN Lars Röwekamp (@mobileLarson) | open knowledge (@_openKnowledge) Cloud Computing Das “New Normal“?

2. DISCLAIMER By cloud, we mean any computing environment in which computing, networking, and storage resources can be provisioned and released elastically in an on-demand, self-service manner.* “ * public and private/cooperate cloud Infrastructure (Matt Stine, CTO Software Architecture, Pivotal.)

3. Warum Cloud?

4. 0% 20% 40% 60% 80% 100% Cloud Computing Cloud Monitor 2020 aktive Nutzer Planer/Diskutierer (noch) kein Thema 76% 73% 66% 19% 19% 21% 6% 8% 13%2017 2018 2019 (Quelle: Bitcom Research, 2020, https://www.bitkom.org/Presse/Presseinformation/Drei-von-vier-Unternehmen-nutzen-Cloud-Computing)

5. Private Cloud Computing Public Cloud Computing Cloud Monitor 2020 58% 55% 51% 38% 35% 31% 25% 23% 22% 30% 28% 27% 16% 21% 28% 31% 37% 42%2017 2018 2019 2017 2018 2019 0% 20% 40% 60% 80% 100% aktive Nutzer Planer/Diskutierer (noch) kein Thema (Quelle: Bitcom Research, 2020, https://www.bitkom.org/Presse/Presseinformation/Drei-von-vier-Unternehmen-nutzen-Cloud-Computing)

6. From idea to App The biggest advantage of a cloud(-native) architecture is that it takes you from idea to app in the quikest possible time. “ (Pavan Belagatti, Groth Marketing Manager, jfrog)

7. I promise! (Amazon, Google, Microsoft, IBM…)

8. Die 6 Cloud-Versprechen 1. … 2. … 3. … 4. … 5. … 6. …

9. Die 6 Cloud-Versprechen 1. einfacheres Management 2. … 3. … 4. … 5. … 6. …

10. Die 6 Cloud-Versprechen 1. einfacheres Management 2. schnellere Releases 3. … 4. … 5. … 6. …

11. Die 6 Cloud-Versprechen 1. einfacheres Management 2. schnellere Releases 3. verbesserte Kosteneffizienz 4. … 5. … 6. …

12. Die 6 Cloud-Versprechen 1. einfacheres Management 2. schnellere Releases 3. verbesserte Kosteneffizienz 4. mehr Zuverlässigkeit/Sicherheit 5. … 6. …

13. Die 6 Cloud-Versprechen 1. einfacheres Management 2. schnellere Releases 3. verbesserte Kosteneffizienz 4. mehr Zuverlässigkeit/Sicherheit 5. beliebige Skalierbarkeit 6. …

14. Die 6 Cloud-Versprechen 1. einfacheres Management 2. schnellere Releases 3. verbesserte Kosteneffizienz 4. mehr Zuverlässigkeit/Sicherheit 5. beliebige Skalierbarkeit 6. besseres Kundenerlebnis

15. Die 6 Cloud-Versprechen 1. einfacheres Management 2. schnellere Releases 3. verbesserte Kosteneffizienz 4. mehr Zuverlässigkeit/Sicherheit 5. beliebige Skalierbarkeit 6. besseres Kundenerlebnis BTW: keine Lock-In Effekte mehr** Cloud-native

16. #1 Agilität

17. #2 Plattform

18. #3 Kosten

19. #4 Innovationen

20. Wieviel Cloud?* * … passt zu mir?

21. Road to the Cloud Running applications on the cloud is not a binary decision. You don‘t just move to the cloud and call it a day. “ (Paul Fremantle, CTO, WSO2)

22. Systems for the Cloud For systems behave well on the cloud, they need to be written for the cloud.* “ (Paul Fremantle, CTO, WSO2) * Applications vs. Software-as-a-Service

23. … or here? Cloud Friendly … or maybe here! Cloud Native … or maybe here .. Cloud ready But you want to be here … Cloud Resilient 00 01 02 03 04 You are here … On Premise Das „Cloud Maturity“ Model

24. aka “repeatable” Cloud Friendly aka “architecture” Cloud Native aka “lift & shift” Cloud ready aka ”self-healing” Cloud Resilient 00 01 02 03 04 You are here … On Premise Das „Cloud Maturity“ Model

25. Stage #0 No Cloud

26. 00 01 02 03 04 No-Cloud aka „???“ keine zentrale IT Governance keine zentrale IT Innovationsstrategie getrennte Entwicklungs- und Operation-Teams Legacy Anwendungen von Client-Server bis 3-Tier laufen auf „bare metal“ kaum bis keine Automatisierung

27. Die 6 Cloud-Versprechen 1. einfacheres Management 2. schnellere Releases 3. verbesserte Kosteneffizienz 4. mehr Zuverlässigkeit/Sicherheit 5. beliebige Skalierbarkeit 6. besseres Kundenerlebnis BTW: keine Lock-In Effekte mehr*

28. Stage #1 Cloud Ready

29. 00 01 02 03 04 Cloud-Ready aka „lift & shift“

30. 00 01 02 03 04 Cloud-Ready aka „lift & shift“ Infrastructure Services (IaaS/VMs) erste Plattform Services (PaaS light) Self-contained Applications Ports/Networking Plattform-managed

31. myApp myApp myApp EC2 Instance EC2 Instance EC2 Instance Routing PROD Load Balancer myDB EC2 Instance

32. myApp myApp myApp EC2 Instance EC2 Instance EC2 Instance Routing PROD Load Balancer myDB EC2 Instance

33. myApp myApp myApp EC2 Instance EC2 Instance EC2 Instance Routing PROD Load Balancer myDB EC2 Instance myFS EC2 Instance myMQ EC2 Instance

34. myApp myApp myApp EC2 Instance EC2 Instance EC2 Instance Routing PROD Load Balancer myDB EC2 Instance myFS EC2 Instance myMQ EC2 Instance

35. myApp myApp myApp EC2 Instance EC2 Instance EC2 Instance Routing PROD Load Balancer Queue RDBMS File Storage

38. Stage #2 Cloud Friendly

39. 00 01 02 03 04 Cloud-Friendly aka „repeatable“

40. 00 01 02 03 04 Cloud-Friendly aka „repeatable“ 12-factor App Design mehr Plattform Services (PaaS) Skalierung via Cloud Plattform Verfügbarkeit (HA) via Cloud Plattform

41. Eine Codebase Explizite Abhängigkeiten Konfiguration via EnvVars Unterstützende Dienste Build, Release, Run Stateless Prozesse Bindung an Ports Nebenläufigkeit Elastizität & Verfügbarkeit Dev-Prod Vergleichbarkeit Logs als Streams Admin-Prozesse VII. VIII. IX. X. XI. XII. I. II. III. IV. V. VI.

42. Eine Codebase Explizite Abhängigkeiten Konfiguration via EnvVars Unterstützende Dienste Build, Release, Run Stateless Prozesse Bindung an Ports Nebenläufigkeit Elastizität & Verfügbarkeit Dev-Prod Vergleichbarkeit Logs als Streams Admin-Prozesse VII. VIII. IX. X. XI. XII. I. II. III. IV. V. VI. APP DESIGN MANAGE BUILD & RELEASE

43. myApp myApp myApp EC2 Instance EC2 Instance EC2 Instance Routing PROD Load Balancer Queue RDBMS File Storage

44. myApp myApp myApp EC2 Instance EC2 Instance EC2 Instance Routing PROD Load Balancer noSQL Queue RDBMS File Storage Archive

45. myApp myApp myApp Routing Elastic Kubernetes Service Backing Services ALB Controller PROD noSQL Queue RDBMS File Storage Archive

46. myApp myApp myApp Routing Elastic Kubernetes Service Backing Services ALB Controller PROD noSQL Queue RDBMS CI/CD app.yml Declarative API File Storage Archive

47. myApp myApp myApp Routing Queue Elastic Kubernetes Service Backing Services ALB Controller CI/CD app.yml Declarative API myApp myApp Code Base Log Stream Trace Info Config Users Monitorring File Storage Archive RDBMS noSQL IAM Certificates PROD DEV

50. Stage #2 Cloud Resilient

51. 00 01 02 03 04 Cloud-Resilient aka „self-healing“

52. 00 01 02 03 04 Cloud-Resilient aka „self-healing“ Metriken & Monitoring als Systembestandteil Apps resilient gegen Ausfälle von Teilsystemen proaktives Design für Ausfälle proaktives Testen von Ausfällen* *antifragiles System

53. Ensure fault tolerance Build without taking steps to ensure fault tolerance, 30 dependencies each with 99.99% uptime would result in 2+ hours downtime per month. “ (netflix Techblog)

54. myApp myApp myApp Routing Queue Elastic Kubernetes Service Backing Services ALB Controller CI/CD app.yml Declarative API myApp myApp Code Base Log Stream Trace Info Config Users Monitorring File Storage Archive RDBMS noSQL IAM Certificates PROD DEV

55. myApp myApp myApp Routing Queue Elastic Kubernetes Service Backing Services ALB Controller CI/CD app.yml Declarative API myApp myApp Code Base Config Users Monitorring File Storage Archive RDBMS noSQL IAM Certificates PROD DEV Log Stream Trace Info Healt Probes Metrics

56. myApp myApp myApp Routing Queue Elastic Kubernetes Service Backing Services ALB Controller CI/CD app.yml Declarative API myApp myApp Code Base Config Users Monitorring File Storage Archive RDBMS noSQL IAM Certificates PROD DEV self healing Log Stream Trace Info Healt Probes Metrics

57. myApp myApp myApp Routing Queue Elastic Kubernetes Service Backing Services ALB Controller CI/CD app.yml Declarative API myApp myApp Code Base Config Users Monitorring File Storage Archive RDBMS noSQL IAM Certificates PROD TEST DEV proactive test for failure self healing Log Stream Trace Info Healt Probes Metrics

60. Stage #3 Cloud Native

61. 00 01 02 03 04 Cloud-Native aka „architectured“

62. 00 01 02 03 04 Cloud-Native aka „architectured“ Microservices statt Monolithen Loose gekoppelte Komponenten API First Design Ansatz Consumer-driven Contract Testing

63. myApp myApp myApp Routing Queue Elastic Kubernetes Service Backing Services ALB Controller CI/CD app.yml Declarative API myApp myApp Code Base Config Users Monitorring File Storage Archive RDBMS noSQL IAM Certificates PROD TEST DEV proactive test for failure self healing Log Stream Trace Info Healt Probes Metrics

64. Routing Queue Elastic Kubernetes Service Backing Services ALB Controller CI/CD app.yml Declarative API myApp myApp Code Base Config Users Monitorring File Storage Archive RDBMS noSQL IAM Certificates PROD TEST DEV proactive test for failure MS self healing Log Stream Trace Info Healt Probes Metrics MS MS MS MS MS

67. Stage #4 Cloud Voodoo

68. aka “repeatable” Cloud Friendly aka “architecture” Cloud Native aka “lift & shift” Cloud ready aka ”self-healing” Cloud Resilient 00 01 02 03 04 You are here … On Premise Das „Cloud Maturity“ Model

69. Routing Queue Elastic Kubernetes Service Backing Services ALB Controller CI/CD app.yml Declarative API myApp myApp Code Base Config Users Monitorring File Storage Archive RDBMS noSQL IAM Certificates PROD TEST DEV proactive test for failure MS self healing Log Stream Trace Info Healt Probes Metrics MS MS MS MS MS

70. Routing Queue Backing Services CI/CD app.yml myApp myApp Code Base Config Users Monitorring File Storage Archive RDBMS noSQL IAM Certificates PROD TEST DEV proactive test for failure Fn Fn Fn Fn Fn Fn FnFn Serverless Functions API Gateway Fn Fn Fn Fn FnFnFn FnFn Fn Fn Fn Fn Log Stream Trace Info Healt Probes Metrics Declarative API

73. (M)ein Fazit zur Cloud …

74. (M)ein Fazit zur Cloud Cloud ist mehr als nur Technologie Cloud ist auch • Architektur • Vorgehen • Organisation

75. Cloud braucht Mut zur Veränderung …

76. Mut und Willen zur Veränderung Technologie • fachliches Splitten der Monolithen • fachliches Splitten der Daten • Einführung von Containerisierung • leichtgewichtige Prozesse* *Choreographie wenn möglich, Orchestrierung wenn nötig

77. Mut und Willen zur Veränderung Organisation • Einführung Business Capability Teams • Einführung Platform Operation Team

78. Mut und Willen zur Veränderung Kultur • DevOps vs Silos • Continuous Delivery vs Releases • Autonomie vs Governance* • Fault Tolerant vs Static Systems *gilt für Micro Architektur, nicht für Marco Archhitektur

79. Was ihr mitnehmen solltet …

80. ? ? ? @mobileLarson lars.roewekamp@openknowledge.de

81. Lars Röwekamp, @mobileLarson Kontakt: lars.roewekamp@openknowledge.de kontakt@openknowledge.de Besten Dank! #WISSENTEILEN

82. © you – shutterstock.com (Folie 1) © krakenimages.com – shutterstock.com (Folie 7) © rawpixel.com – shutterstock.com (Folie 16) © foxaon1987 – shutterstock (Folie 75) © ligthspring – shutterstock.com (Folie 77) © re:invent 2019 (Folie 81) Alle weiteren Bilder der Präsentation sind entweder von pixabay.com oder von mir selbst erstellt. Bildernachweis

Cloud, das „New Normal“?

open knowledge GmbH

Cloud, das „New Normal“?