[Glasgow] Platform Orchestrators: The Missing Middle of Internal Developer Platforms?

Slide 1

Slide 1 text

@danielbryantuk Platform Orchestrators: The Missing Middle of Internal Developer Platforms? Daniel Bryant | Platform Engineer | Head of Product Marketing @ Syntasso @danielbryantuk

Slide 2

Slide 2 text

@danielbryantuk How do you build a platform? ● Top-down, application developer-focused ○ “The Backstage service catalog is fantastic, but the support for day 2 ops… not so muchˮ ● Bottom-up, operations/infrastructure-focused ○ “The Terraform workflow is fantastic, but infrastructure abstractions leak through to developers HCL, K8s, etc)ˮ ● Middle-out, platform engineering-focused ○ X-as-a-service, process automation, fleet management ○ “Platform as a productˮ approach

Slide 3

Slide 3 text

@danielbryantuk @danielbryantuk (he/him) linktr.ee/danielbryantuk

Slide 4

Slide 4 text

@danielbryantuk Previously at

Slide 5

Slide 5 text

@danielbryantuk From Kubernetes to PaaS to… err, whatʼs next? https://www.youtube.com/watch?v=zUpYEhaUJnM

Slide 6

Slide 6 text

@danielbryantuk

Slide 7

Slide 7 text

@danielbryantuk What even is a platform? 🤔

Slide 8

Slide 8 text

@danielbryantuk What is a platform, anyway? 🚉 A digital platform is a foundation of self-service APIs, tools, services, knowledge and support which are arranged as a compelling internal product. Autonomous delivery teams can make use of the platform to deliver product features at a higher pace, with reduced coordination. Evan Bottcher martinfowler.com/articles/talk-about-platforms.html

Slide 9

Slide 9 text

@danielbryantuk Gartner: What is platform engineering? “Platform engineering improves developer experience and productivity by providing self-service capabilities with automated infrastructure operations. It is trending because of its promise to optimise the developer experience and accelerate product teamsʼ delivery of customer value.ˮ https://www.gartner.com/en/articles/what-is-platform-engineering

Slide 10

Slide 10 text

Slide 11

Slide 11 text

@danielbryantuk Platform engineering expectations gartner.com/en/newsroom/press-releases/2023-11-28-gartner-hype-cycle-shows-ai-practices-and-platform-engineering-will-reach-mainstream-adoption-in-software-engineering-in-two-to-five-years

Slide 12

Slide 12 text

@danielbryantuk Platform engineering expectations linkedin.com/feed/update/urn:li:ugcPost:7199307746356199424

Slide 13

Slide 13 text

@danielbryantuk Platform challenges

Slide 14

Slide 14 text

@danielbryantuk The “whyˮ of platforms 🚉

Slide 15

Slide 15 text

Slide 16

Slide 16 text

@danielbryantuk Current software engineering challenges You want to overcome the following challenges: ● Slow: Developers are blocked, waiting on tickets and other teams ● Risky: Critical business processes are inconsistently applied ● Inefficient: Tech sprawl leads to tech debt and operational overhead 50% of respondents are capable of deploying less than “between once per week and once per month” Accelerate State of DevOps 2023 42% of developers say they can’t release code to production without risking failures Harness State of the DecEx 2024 Overall, 59% of IT pros are frustrated by the time spent on routine infrastructure activities and 84% agreed that they “could bring more value to their organization if they spent less time on routine tasks” HorizonIQ Report 2020

Slide 17

Slide 17 text

@danielbryantuk

Slide 18

Slide 18 text

@danielbryantuk What are the goals of your platform? ● Go faster: Platform teams need to provide “everything as a serviceˮ to help rapidly and sustainably deliver value to end-users ● Decrease risk: Teams need to automate manual processes in reusable components ● Increase efficiency: You need to manage and scale your digital platform and resources as a fleet

Slide 19

Slide 19 text

@danielbryantuk The “howˮ of platforms 🚉

Slide 20

Slide 20 text

@danielbryantuk Top down, app developer-focused rollout “Backstage is my platform. Developers go here to spin up a new application, deploy it, and view metricsˮ ✅ Fantastic developer experience (and service catalog) ✅ Highly customisable ❌ Often a facade that calls a series of infrastructure APIs ❌ Day 2 (automation) aspects of the portal and plugins can be challenging

Slide 21

Slide 21 text

@danielbryantuk “Terraform is my platform. I can orchestrate all of my infrastructure via HCL and cron jobs, and the GitOps pipelines automatically deploy applicationsˮ ✅ Everything-as-code ✅ Highly automatable ❌ Infrastructure abstractions leak outwards towards developers ❌ At scale, the diversity of tech can be challenging to automate/orchestrate Bottom up, operations-focused rollout

Slide 22

Slide 22 text

@danielbryantuk The missing middle? 🏗

Slide 23

Slide 23 text

@danielbryantuk https://thenewstack.io/crossplane-what-most-people-get-wrong-and-how-to-get-it-right/ https://cnoe.io/ https://platformengineering.org/platform-tooling https://www.kratix.io/

Slide 24

Slide 24 text

@danielbryantuk syntasso.io/post/platform-engineering-orchestrating-applications-platforms-and-infrastructure

Slide 25

Slide 25 text

@danielbryantuk syntasso.io/post/platform-engineering-orchestrating-applications-platforms-and-infrastructure

Slide 26

Slide 26 text

Slide 27

Slide 27 text

@danielbryantuk Making it happen 🚉

Slide 28

Slide 28 text

@danielbryantuk Platforms: Abstract thinking ● APIs, domains, SOLID/CUPID ○ Just as important for platforms ○ Think information hiding ○ Build for progressive disclosure ● Design for UI, CLI, & API ○ Meet devs where they are at ○ Optimise for automation syntasso.io/post/when-backstage-met-terraform-a nd-platform-orchestrators-webinar-recap

Slide 29

Slide 29 text

@danielbryantuk Business requirements change, user expectations expand, APIs are at the core of sustainable platforms ● Open Application Model (OAM) / Score ● Kratix and Promises ● KubeBuilder ● Crossplane ● Massdriver ● … More user focused More implementation focused Platform abstractions (and APIs)

Slide 30

Slide 30 text

@danielbryantuk Tech "stacks" are emerging ● The “BACKˮ stack: Backstage, Argo, Crossplane, Kyverno ● CNOE Framework: Cloud Native Operation Excellence ● Kubefirst ● DIY All the other CNCF tech++ ● … More opinionated Less opinionated Platform automation (tech)

Slide 31

Slide 31 text

@danielbryantuk This can be overwhelming…

Slide 32

Slide 32 text

@danielbryantuk Example: Kratix

Slide 33

Slide 33 text

@danielbryantuk Promises, promises…

Slide 34

Slide 34 text

@danielbryantuk

Slide 35

Slide 35 text

@danielbryantuk Build it, and they will come Solve problems, and they will come

Slide 36

Slide 36 text

Slide 37

Slide 37 text

@danielbryantuk Product focus thoughtworks.com/en-gb/insights/looking-glass/platforms-as-products

Slide 38

Slide 38 text

@danielbryantuk Product focus thoughtworks.com/en-gb/insights/looking-glass/platforms-as-products

Slide 39

Slide 39 text

@danielbryantuk What gets measured, gets managed ● Establish goals and measurements ● Leading indicators ○ Adoption rates ○ Onboarding times ○ Time to nth PR ● Lagging indicators ○ App retention rate ○ Incidents/near misses mitigated ○ ROI (time saved)

Slide 40

Slide 40 text

@danielbryantuk Wrapping up 🎉

Slide 41

Slide 41 text

@danielbryantuk Conclusion ● 🏗 Build your platform intentionally ● 🚉 Watch out for the missing middle: “platform orchestratorsˮ ● 👀 Struggling with scaling day 2 operations with your portal? ● 👀 Infrastructure abstractions leaking to developers? ● 🎯 Focus on “platform as a productˮ

Slide 42

Slide 42 text

@danielbryantuk Thank you! @danielbryantuk syntasso.io/post/platform-engineering-orchestrating-applications-platforms-and-infrastructure docs.kratix.io/main/quick-start speakerdeck.com/danielbryantuk slideshare.net/dbryant_uk/presentations