CNCF_ A step to step guide to platforming your delivery setup.pdf

1. 1
A step to step guide to platforming
your delivery setup
Kaspar von Grünberg
Humanitec

2. 2
Kaspar
➔ Internaldeveloperplatform.org
➔ Platformengineering.org
➔ Platform Engineering Slack
➔ Platform Engineers Meetups
➔ PlatformCon.com
➔ Humanitec
Ping me at kaspar@humanitec.com or @kaspar_official
2

3. 3
In this talk
➔ Platforming, what are we talking about?
➔ A step by step guide to nailing your platform journey
3

4. The problem
Teams waste 25% of their time
operating apps as complexity
increases
4
More services and
infrastructure resources
per app than 2010.
25X
More specialist tools in
the toolchain to meet
scale.
5X
Evolving global
environment drives
demand & complexity.

5. We’re trying to control this chaos with manual work and
scripts
Sample App
Tool Infrastructure
Action
Jenkins
AWS Cluster
GCP Cluster
Artifactory
GithubActions
Terraform Crossplane
cloudsql
RDS
Redis
Microservice
Payments
ReactFronted
API
Cloudflare
Ingress Vault
Gateway
User Auth
User Auth
Deploy
Add service
Debug
Roll back
Maintain
Spin up env
Request resource
Filestorage Onboard team
Stream Logs
Datadog
Snyk
Rabbitmq
MariaDB
Infra Orchestration
Env Management
Deploy Pipeline
Istio
Developers wait,
Ops drowns.
Complex Operative Environment of App
5

6. 6
Application developers
➔ Enable self-service
➔ Reduce cognitive load
➔ Without abstracting
6
Platform/SRE
➔ Standardization by
design
➔ Reduced ticket ops
➔ Focus
Why platforms?

7. Immature organizations tell teams to build a car, give
them a credit card and tell where to find a store with
raw materials.
When they struggle they send people to help them
organize and call this “DevOps”.

8. Mature organizations tell teams to build a car, give them
a credit card and tell them where to find the raw
materials.
If teams struggle, DevOps helps them organize and
cloud operations teams help them find the right
materials and prep those for them.

9. 9
Advanced organizations tell teams to build a car.
The platform team prepares a platform, developers
build on top.

10. 10
10
Internal Developer Platforms - the sum of many
components that form golden paths for developers

11. 11
But where do you get started?
11

12. 12
12
Step #1 All in or nothing - treat you platform as a product
➔ Assign a PO, even if only half time
➔ A platform team has software engineers!
➔ A roadmap
➔ User interviews
➔ Users!

13. 13
13
Step #2 Prioritize - don’t fall for the prioritization fallacy
Procedure Frequency (%of
deployments)
Dev time in hours
(including waiting
and errors)
Ops time in hours
(including waiting
and errors)
Adding env variable 5%* 1h* 1h*
Add services and dependencies 1%* 16h* 8h*
Refactoring 0,18%* 40h* 8h*
Changing resources/ Adding resources 0,18%* 8h* 24h*
Waiting due to blocked environment 0,5%* 15h* 0h*
Spinning up environment 0,33%* 24h* 24h*
Onboarding developers 3%* 80h* 16h*

14. 14
14
Step #3 agree on the lowest common denominator tech stack
You will NOT be able to build a platform for everything. And yes,
it’s probably containers and K8s.

15. 15
15
#Step 4 - identify your team of future evangelists
➔ One team of innovators
➔ With an app EXACTLY on your target tech stack
➔ That really wants to do it

16. 16
16
#Step 4 - dynamic or static?

17. 17
17
#Step 4 - dynamic or static?

18. 18
18
#Step 5 - start building
➔ Build something that’s 10X better, even if it’s small
➔ Build it where the ROI is
➔ Spend too much time on this one, you have to get it
right
➔ Make your evangelist team love it

19. 19
19
#Step 6 - it’s a long journey
➔ And it never stops. Iterate, iterate iterate
➔ Join in on platformengineering.org, PlatformCon and
Platform Engineering meetups
➔ Check out Humanitec, a Platform Orchestrator that
can help you build reliable platforms fast.

20. Thank you.