Patrick.Sy/website-and-documentation
1
0
Fork 0
forked from DevFW-CICD/website-and-documentation
Code Pull requests Activity

doc(stakeholder-workeshop)

Browse source
This commit is contained in:
Stephan Lo 2024-11-07 12:47:08 +01:00
parent 64c020de47
commit e6a44cdc80
4 changed files with 36 additions and 108 deletions
Download patch file Download diff file Expand all files Collapse all files

45
content/en/docs/project/intro-stakeholder-workshop/DevOps-Story.md
View file

@ -1,45 +0,0 @@
---
title: DevOps Story
weight: 2
description: The storyline of DevOps - why we need Platforms
---
## Platforms as the result of DevOps
#### DevOps since 2010
![alt text](DevOps-Lifecycle.jpg)
```mermaid
block-beta
columns 1
a["Platform-Orchestrating"]
b["Platforming"]
c["DevOps"]
style a fill:yellow
style b fill:lightblue
style c fill:orange
```
* Spotify
* Airbnb
* Zalando
* Uber
* Netflix
* Salesforce
* Google
* Booking.com
* Amazon
* Autodesk
* Adobe
* Cisco
* ...

39
content/en/docs/project/intro-stakeholder-workshop/_index.md
View file

@ -5,10 +5,10 @@ description: Another overall eDF introduction for stakeholders
---
> This section is derived from [conceptual-onboarding-intro](../conceptual-onboarding/1_intro/)
## Edge Developer Framework Solution Overview
> This section is derived from [conceptual-onboarding-intro](../conceptual-onboarding/1_intro/)
1. We have the ['Edge Developer Framework'](./edgel-developer-framework/). \
In short the mission is:
* Build a european edge cloud IPCEI-CIS
@ -28,4 +28,37 @@ description: Another overall eDF introduction for stakeholders
2. CNOE aims to embrace change and customization!
![alt text](DevOps-Lifecycle-1.jpg)
## Platforms as the result of DevOps
### DevOps since 2010
![alt text](DevOps-Lifecycle.jpg)
* from 'left' to 'right' - plan to monitor
* 'leftshift'
* --> turns out to be a right shift for developers with cognitive overload
* 'DevOps isd dead' -> we need Platforms
### platforming to provide 'golden paths'
> don't mix up 'golden paths' with pipelines or CI/CD
![alt text](../conceptual-onboarding/3_platforming/humanitec-history.png)
#### small list of platform using companies
* Spotify
* Airbnb
* Zalando
* Uber
* Netflix
* Salesforce
* Google
* Booking.com
* Amazon
* Autodesk
* Adobe
* Cisco
* ...

31
content/en/docs/project/intro-stakeholder-workshop/devops-layers.c4
View file

@ -1,31 +0,0 @@
specification {
element layer
tag devopstag
}
model {
layer orchestrationlayer "Platform-Orchestration" {
#devopstag
style {
color amber
}
}
layer platformlayer "Platforming" {
#devopstag
style {
color indigo
}
}
layer devopslayer "DevOps" {
#devopstag
style {
color sky
}
}
}
views {
view {
include * where tag == #devopstag
}
}

29
content/en/docs/project/intro-stakeholder-workshop/eDF-Story.md
View file

@ -1,29 +0,0 @@
---
title: eDF Story
weight: 1
description: The storyline of the eDF solution - from requirements to the POC
---
> This section is derived from [conceptual-onboarding-intro](../conceptual-onboarding/1_intro/)
## Edge Developer Framework Solution Overview
1. We have the ['Edge Developer Framework'](./edgel-developer-framework/). \
In short the mission is:
* Build a european edge cloud IPCEI-CIS
* which contains typical layers infrastructure, platform, application
* and on top has a new layer 'developer platform'
* which delivers a **cutting edge developer experience** and enables **easy deploying** of applications onto the IPCEI-CIS
2. We think the solution for EDF is in relation to ['Platforming' (Digital Platforms)](./platforming/)
1. The next evolution after DevOps
2. Gartner predicts 80% of SWE companies to have platforms in 2026
3. Platforms have a history since roundabout 2019
4. CNCF has a working group which created capabilities and a maturity model
3. Platforms evolve - nowadys there are [Platform Orchestrators](./orchestrators/)
1. Humanitec set up a Reference Architecture
2. There is this 'Orchestrator' thing - declaratively describe, customize and change platforms!
4. Mapping our assumptions to the [CNOE solution](./cnoe/)
1. CNOE is a hot candidate to help and fulfill our platform building
2. CNOE aims to embrace change and customization!