- Everyone is building a platform, whether they realize it or not
- Platform as product FTW π
- Getting exec/C-level buy-in is challenging
- Platform Product Manager will be a hot role π
- Balance devex, CLI, UIs, & IaC βοΈ
π§΅π
1/ Everyone is building a platform, whether they realize it or not π€
There was a real mix of platform tech at the event:
- Kubernetes
- Serverless
- On-prem
One key theme: every "platform" helped devs to code, ship, and run, reducing toil and increasing speed and safety π βοΈ
A lot of (successful) platform builds and adoption appeared to be driven bottom-up by developers π§°
And yes, even that janky "setup-local-dev. sh" script and clumsily assembled GitHub Actions building and deploying from your repo onto an EC2 instance count as a platform π
I learned a lot about the value of bottom-up platform and tooling adoption from Bo Daley, DevOps Platform Engineer in a recent @ambassadorlabs podcast ποΈ
All of the thought leaders agreed on this point, and this was best articulated by my buddy @manupaisable of @TeamTopologies fame in his talk:
@ambassadorlabs@manupaisable@TeamTopologies I also pitched "treat the platform as a product" as one of my top three requirements for building a platform in my #PlatformCon talk "From Kubernetes to PaaS to β¦ err, whatβs next?"
Several attendees asked about this. As others suggested, I believe the success of a platform as a product build will depend a lot on getting the right product manager to manage upwards as well as across eng (more details below)
Based on my previous experience, I believe a lot of folks will not appreciate the benefits of a good PM and will instead power ahead with simply building things (π’ vs π)
You can canary release on K8s (with @argoproj CD) and update ingress mappings (with Emissary-ingress) via the UI, and behind the scenes we generate the updated YAML and config and issue a PR against your repo
#KubeCon EU Takeaway 2: β‘οΈ Platforms and βgolden pathsβ enable productivity and reduce developer friction
I saw several great talks, and also presented on why I think golden paths and platform engineering are the next big thing π₯
Let's explore this in more detail: 𧡠π
The first mention of "golden paths" was from @MercedesBenz in the opening keynote, where they talked about the K8s-based platform they had built over the past 7 years ποΈ
Lots of thought, effort, and iteration had been applied to the dev experience π§°
@MercedesBenz Golden paths are all about making it easy for a developer to code, ship, and run applications; to go from biz idea, to code, to test, to running in prod, to collecting telemetry to enable iteration β‘
There can be one golden path or many, depending on your use cases π£οΈ
1. Cloud education is vitally important 2. Platforms and βgolden pathsβ enable productivity 3. Developer experience is top of mind 4. Cloud networking is simplifying 5. Increasing focus on security
Let's explore 1 in more detail 𧡠π
First, the complete #KubeConEU summary blog post that provides in-depth coverage can be found here:
My top Twitter threads on cloud, containers, and microservices for this year so far:
- Platform engineering
- API gateway vs service mesh
- @Kubernetesio debugging
- @Docker chaos testing
- Fast dev/test with Telepresence
- @buildpacks_io
- Microservice testing
A 𧡠of 𧡠s π
I'm predicting big things for the "platform engineering" space over the next year. Whether you β€οΈ or π‘ the name, I think this is the new DevOps.
Watch this space for lots of knowledge sharing, innovation, and VC money π° !
Think about coupling and cohesion when designing microservices (yeah, yeah, I know, but I mean seriously think about this, and even do some upfront design) π¨