From dd728936b2ad1444261e49f762cbc202c85d15f6 Mon Sep 17 00:00:00 2001 From: Anja Kammer Date: Wed, 6 Mar 2024 15:03:00 +0100 Subject: [PATCH 1/7] mention serverless concept in 1. chapter --- .../01-duration-terms.adoc | 4 ++-- .../02-learning-goals.adoc | 8 ++++++-- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/01-Fundamentals-of-Modern-Infrastructures/01-duration-terms.adoc b/docs/01-Fundamentals-of-Modern-Infrastructures/01-duration-terms.adoc index 450aad8..06cb9fb 100644 --- a/docs/01-Fundamentals-of-Modern-Infrastructures/01-duration-terms.adoc +++ b/docs/01-Fundamentals-of-Modern-Infrastructures/01-duration-terms.adoc @@ -4,7 +4,7 @@ |=== === Begriffe und Konzepte -Cloud, Cloud-Arten, Cloud-Anbieter, On Premise, Bare Metal, Cloud Service Modelle (*aaS), Vendor Lock-in, Managed Services, Cloud Native Services, Cloud-Muster, Cloud-Migrationsmuster, Multi/Hybrid Cloud, Organisatorische Aspekte der Cloud Migration, Rechtliche Rahmenbedingungen, Time-to-Market, Verfügbarkeit, Skalierung, Geo Redundanz und Skalierung, Performance, IOPS, Decoupling Operations, Networking. +Cloud, Cloud-Arten, Cloud-Anbieter, On Premise, Bare Metal, Cloud Service Modelle (*aaS), Vendor Lock-in, Managed Services, Serverless, Cloud Native Services, Cloud-Muster, Cloud-Migrationsmuster, Multi/Hybrid Cloud, Organisatorische Aspekte der Cloud Migration, Rechtliche Rahmenbedingungen, Time-to-Market, Verfügbarkeit, Skalierung, Geo Redundanz und Skalierung, Performance, IOPS, Decoupling Operations, Networking. // end::DE[] @@ -14,7 +14,7 @@ Cloud, Cloud-Arten, Cloud-Anbieter, On Premise, Bare Metal, Cloud Service Modell |=== === Terms and Principles -Cloud, cloud types, cloud provider, on premise, bare metal, cloud service models (*aaS), vendor lock-in, managed services, cloud native services, cloud patterns, cloud migration patterns, multi/hybrid cloud, organizational aspects of cloud migration, legal conditions, time-to-market, availability, geo redundancy and scalability, performance, IOPS, decoupling operations, networking. +Cloud, cloud types, cloud provider, on premise, bare metal, cloud service models (*aaS), vendor lock-in, managed services, serverless, cloud native services, cloud patterns, cloud migration patterns, multi/hybrid cloud, organizational aspects of cloud migration, legal conditions, time-to-market, availability, geo redundancy and scalability, performance, IOPS, decoupling operations, networking. // end::EN[] diff --git a/docs/01-Fundamentals-of-Modern-Infrastructures/02-learning-goals.adoc b/docs/01-Fundamentals-of-Modern-Infrastructures/02-learning-goals.adoc index 9a2e752..f3fb519 100644 --- a/docs/01-Fundamentals-of-Modern-Infrastructures/02-learning-goals.adoc +++ b/docs/01-Fundamentals-of-Modern-Infrastructures/02-learning-goals.adoc @@ -15,7 +15,9 @@ Sie verstehen den Unterschied zwischen Cloud- und On-Premise-Betrieb sowie die A Softwarearchitekt:innen kennen unterschiedliche Cloud Service Modelle (*aaS) und können Services anhand dieser Modelle klassifizieren. -Sie verstehen das Shared-Responsibility-Modell und dessen Relevanz für Kosten- und Risikobewertungen bei der Nutzung von managed Cloud Services. +Sie verstehen darüber hinaus das Serverless Konzept und können es den Cloud Service Modellen zuordnen. + +Softwarearchitekt:innen verstehen das Shared-Responsibility-Modell und dessen Relevanz für Kosten- und Risikobewertungen bei der Nutzung von managed Cloud Services. Sie kennen das Konzept des Vendor Lock-in und seine Relevanz für die Entscheidungsfindung zwischen managed und self-managed Services. @@ -56,7 +58,9 @@ They understand the difference between cloud and on-premise operations, as well Software architects know different cloud service models (*aaS) and can classify services based on these models. -They understand the shared responsibility model and its relevance for cost and risk assessments when using managed cloud services. +They also understand the serverless concept and can assign it to the cloud service models. + +Software architects understand the shared responsibility model and its relevance for cost and risk assessments when using managed cloud services. They know the concept of vendor lock-in and its relevance for decision-making between managed and self-managed services. From cf1f79802c896d284554840dd98c6d6bbbfa44a7 Mon Sep 17 00:00:00 2001 From: Anja Kammer Date: Wed, 6 Mar 2024 15:07:17 +0100 Subject: [PATCH 2/7] Add Functions as a Service technology explicitly --- docs/04-Patterns/01-duration-terms.adoc | 4 ++-- docs/04-Patterns/02-learning-goals.adoc | 28 +++++++++++++++++++++++-- 2 files changed, 28 insertions(+), 4 deletions(-) diff --git a/docs/04-Patterns/01-duration-terms.adoc b/docs/04-Patterns/01-duration-terms.adoc index a13d49e..c1d3ca7 100644 --- a/docs/04-Patterns/01-duration-terms.adoc +++ b/docs/04-Patterns/01-duration-terms.adoc @@ -4,7 +4,7 @@ |=== === Begriffe und Konzepte -Resilienz Muster, Container Application Design, Cloud Native Architekturen, Container Pattern, Service Mesh +Resilienz Muster, Container Application Design, Cloud Native Architekturen, Functions as a Service (FaaS), Container Pattern, Service Mesh // end::DE[] @@ -14,7 +14,7 @@ Resilienz Muster, Container Application Design, Cloud Native Architekturen, Cont |=== === Terms and Principles -Resilience Patterns, Container Application Design, Cloud Native Architectures, Container Patterns, Service Mesh +Resilience Patterns, Container Application Design, Cloud Native Architectures, Functions as a Service (FaaS), Container Patterns, Service Mesh // end::EN[] diff --git a/docs/04-Patterns/02-learning-goals.adoc b/docs/04-Patterns/02-learning-goals.adoc index 18eb22c..d1aefad 100644 --- a/docs/04-Patterns/02-learning-goals.adoc +++ b/docs/04-Patterns/02-learning-goals.adoc @@ -19,7 +19,19 @@ Softwarearchitekt:innen kennen Methoden, um technische von fachlichen Aufgaben d * Container Management durch Operator bzw. Controller [[LZ-4-2]] -==== LZ 4-2: Passende Resilienzmuster zur Erhöhung von Fehlertoleranz auswählen +==== LZ 4-2: Passende Technologien für den Betrieb von Modulen auswählen + +Softwarearchitekt:innen können geeignete Technologien zum Betrieb von Modulen eines verteilten Systems auswählen, z.B. mit Functions as a Service (FaaS) und Container Orchestrierung. + +Darüber hinaus können Sie die Anwendung dieser Technologien Anforderungsgetrieben anwenden. Dabei gibt es verschiedene Aspekte zu beachten wie: + +* Skalierungsanforderungen und Ausführungszeit +* Komplexität des Betriebs und fachlichen Schnitts +* Zugriff auf Persistenz +* Limitierungen für Observability und Debugging + +[[LZ-4-3]] +==== LZ 4-3: Passende Resilienzmuster zur Erhöhung von Fehlertoleranz auswählen Softwarearchitekt:innen verstehen, wie bei einer verteilten Anwendung die Kommunikation zwischen den Services fehlertolerant realisiert werden kann. @@ -54,7 +66,19 @@ Software architects are familiar with methods for separating technical and busin * Container management through operators or controllers [[LG-4-2]] -==== LG 4-2: Ability to Select Appropriate Resilience Patterns to Increase Fault Tolerance +==== LG 4-2: Ability to Select Suitable Technologies for Operating Modules + +Software architects can select suitable technologies for operating modules of a distributed system, e.g. with Functions as a Service (FaaS) and container orchestration. + +They select these technologies in a requirements-driven manner. Various aspects must be taken into account, such as + +* Scaling requirements and runtime duration +* Complexity of operation and domain boundaries +* Access to persistence +* Limitations on observability and debugging + +[[LG-4-3]] +==== LG 4-3: Ability to Select Appropriate Resilience Patterns to Increase Fault Tolerance Software architects understand how communication between services in a distributed application can be made fault-tolerant. From a4a3fcccff58b4353760e1a00417d2d9f05f3233 Mon Sep 17 00:00:00 2001 From: Anja Kammer Date: Wed, 6 Mar 2024 15:07:34 +0100 Subject: [PATCH 3/7] adjust changelog accordingly --- CHANGELOG.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index f50644c..288900f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,11 +8,13 @@ - DevOps, DevSecOps, and SRE - Abstraction Layers of Container Managers -## Added/Changed wording +## Naming concepts more explicitly - Chaos engineering - Eventual consistency - Platform quality requirements +- Serverless +- Functions as a Service (FaaS) ## Removed - Mentioning of tool names for automation and operation (Ansible, Chef, Terraform, Rancher, Tectonic, Kops, Kubeadm, OpenShift) From 3abeecd39b8f406821d7f245d50d56cf1eccc211 Mon Sep 17 00:00:00 2001 From: Anja Kammer Date: Wed, 6 Mar 2024 15:17:32 +0100 Subject: [PATCH 4/7] serverless -> serverless computing --- .../01-duration-terms.adoc | 4 ++-- .../02-learning-goals.adoc | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/01-Fundamentals-of-Modern-Infrastructures/01-duration-terms.adoc b/docs/01-Fundamentals-of-Modern-Infrastructures/01-duration-terms.adoc index 06cb9fb..2dc78f5 100644 --- a/docs/01-Fundamentals-of-Modern-Infrastructures/01-duration-terms.adoc +++ b/docs/01-Fundamentals-of-Modern-Infrastructures/01-duration-terms.adoc @@ -4,7 +4,7 @@ |=== === Begriffe und Konzepte -Cloud, Cloud-Arten, Cloud-Anbieter, On Premise, Bare Metal, Cloud Service Modelle (*aaS), Vendor Lock-in, Managed Services, Serverless, Cloud Native Services, Cloud-Muster, Cloud-Migrationsmuster, Multi/Hybrid Cloud, Organisatorische Aspekte der Cloud Migration, Rechtliche Rahmenbedingungen, Time-to-Market, Verfügbarkeit, Skalierung, Geo Redundanz und Skalierung, Performance, IOPS, Decoupling Operations, Networking. +Cloud, Cloud-Arten, Cloud-Anbieter, On Premise, Bare Metal, Cloud Service Modelle (*aaS), Vendor Lock-in, Managed Services, Serverless Computing, Cloud Native Services, Cloud-Muster, Cloud-Migrationsmuster, Multi/Hybrid Cloud, Organisatorische Aspekte der Cloud Migration, Rechtliche Rahmenbedingungen, Time-to-Market, Verfügbarkeit, Skalierung, Geo Redundanz und Skalierung, Performance, IOPS, Decoupling Operations, Networking. // end::DE[] @@ -14,7 +14,7 @@ Cloud, Cloud-Arten, Cloud-Anbieter, On Premise, Bare Metal, Cloud Service Modell |=== === Terms and Principles -Cloud, cloud types, cloud provider, on premise, bare metal, cloud service models (*aaS), vendor lock-in, managed services, serverless, cloud native services, cloud patterns, cloud migration patterns, multi/hybrid cloud, organizational aspects of cloud migration, legal conditions, time-to-market, availability, geo redundancy and scalability, performance, IOPS, decoupling operations, networking. +Cloud, cloud types, cloud provider, on premise, bare metal, cloud service models (*aaS), vendor lock-in, managed services, serverless computing, cloud native services, cloud patterns, cloud migration patterns, multi/hybrid cloud, organizational aspects of cloud migration, legal conditions, time-to-market, availability, geo redundancy and scalability, performance, IOPS, decoupling operations, networking. // end::EN[] diff --git a/docs/01-Fundamentals-of-Modern-Infrastructures/02-learning-goals.adoc b/docs/01-Fundamentals-of-Modern-Infrastructures/02-learning-goals.adoc index f3fb519..e30d80e 100644 --- a/docs/01-Fundamentals-of-Modern-Infrastructures/02-learning-goals.adoc +++ b/docs/01-Fundamentals-of-Modern-Infrastructures/02-learning-goals.adoc @@ -15,7 +15,7 @@ Sie verstehen den Unterschied zwischen Cloud- und On-Premise-Betrieb sowie die A Softwarearchitekt:innen kennen unterschiedliche Cloud Service Modelle (*aaS) und können Services anhand dieser Modelle klassifizieren. -Sie verstehen darüber hinaus das Serverless Konzept und können es den Cloud Service Modellen zuordnen. +Sie verstehen darüber hinaus das Serverless Computing Konzept und können es den Cloud Service Modellen zuordnen. Softwarearchitekt:innen verstehen das Shared-Responsibility-Modell und dessen Relevanz für Kosten- und Risikobewertungen bei der Nutzung von managed Cloud Services. @@ -58,7 +58,7 @@ They understand the difference between cloud and on-premise operations, as well Software architects know different cloud service models (*aaS) and can classify services based on these models. -They also understand the serverless concept and can assign it to the cloud service models. +They also understand the serverless computing concept and can assign it to the cloud service models. Software architects understand the shared responsibility model and its relevance for cost and risk assessments when using managed cloud services. From f9adf03586e9f58e7a56ebad9b8363986ed59ee0 Mon Sep 17 00:00:00 2001 From: Anja Kammer Date: Mon, 11 Mar 2024 14:47:27 +0100 Subject: [PATCH 5/7] add start time aspects to FaaS --- docs/04-Patterns/02-learning-goals.adoc | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/04-Patterns/02-learning-goals.adoc b/docs/04-Patterns/02-learning-goals.adoc index d1aefad..b8921ea 100644 --- a/docs/04-Patterns/02-learning-goals.adoc +++ b/docs/04-Patterns/02-learning-goals.adoc @@ -25,7 +25,8 @@ Softwarearchitekt:innen können geeignete Technologien zum Betrieb von Modulen e Darüber hinaus können Sie die Anwendung dieser Technologien Anforderungsgetrieben anwenden. Dabei gibt es verschiedene Aspekte zu beachten wie: -* Skalierungsanforderungen und Ausführungszeit +* Skalierungsanforderungen +* Start- und Ausführungszeit * Komplexität des Betriebs und fachlichen Schnitts * Zugriff auf Persistenz * Limitierungen für Observability und Debugging @@ -72,7 +73,8 @@ Software architects can select suitable technologies for operating modules of a They select these technologies in a requirements-driven manner. Various aspects must be taken into account, such as -* Scaling requirements and runtime duration +* Scaling requirements +* start and runtime duration * Complexity of operation and domain boundaries * Access to persistence * Limitations on observability and debugging From 4e9f8b5557e3fbfa8e6f361a20a0827244468043 Mon Sep 17 00:00:00 2001 From: Anja Kammer Date: Mon, 11 Mar 2024 14:47:42 +0100 Subject: [PATCH 6/7] reorder terms chapter 4 --- docs/04-Patterns/01-duration-terms.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/04-Patterns/01-duration-terms.adoc b/docs/04-Patterns/01-duration-terms.adoc index c1d3ca7..144c3fa 100644 --- a/docs/04-Patterns/01-duration-terms.adoc +++ b/docs/04-Patterns/01-duration-terms.adoc @@ -4,7 +4,7 @@ |=== === Begriffe und Konzepte -Resilienz Muster, Container Application Design, Cloud Native Architekturen, Functions as a Service (FaaS), Container Pattern, Service Mesh +Resilienz Muster, Container Application Design, Cloud Native Architekturen, Container Pattern, Functions as a Service (FaaS), Service Mesh // end::DE[] @@ -14,7 +14,7 @@ Resilienz Muster, Container Application Design, Cloud Native Architekturen, Func |=== === Terms and Principles -Resilience Patterns, Container Application Design, Cloud Native Architectures, Functions as a Service (FaaS), Container Patterns, Service Mesh +Resilience Patterns, Container Application Design, Cloud Native Architectures, Container Patterns, Functions as a Service (FaaS), Service Mesh // end::EN[] From b4c9b47450241640cdb4ebcb33721a8bc8e668df Mon Sep 17 00:00:00 2001 From: Anja Kammer Date: Mon, 11 Mar 2024 14:49:44 +0100 Subject: [PATCH 7/7] minor typo --- docs/04-Patterns/02-learning-goals.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/04-Patterns/02-learning-goals.adoc b/docs/04-Patterns/02-learning-goals.adoc index b8921ea..e17be62 100644 --- a/docs/04-Patterns/02-learning-goals.adoc +++ b/docs/04-Patterns/02-learning-goals.adoc @@ -74,7 +74,7 @@ Software architects can select suitable technologies for operating modules of a They select these technologies in a requirements-driven manner. Various aspects must be taken into account, such as * Scaling requirements -* start and runtime duration +* Start and runtime duration * Complexity of operation and domain boundaries * Access to persistence * Limitations on observability and debugging