2/9 🚀 So first, let’s do the what - basically, platform engineering (PE) is the discipline of designing and building toolchains and workflows that enable self-service capabilities for engineering organizations in the cloud-native era 🌩️
3/9 Platform engineers build an integrated product, often referred to as an “Internal Developer Platform” (IDP), covering the operational necessities of the entire lifecycle of an application💻
4/9 An Internal Developer Platform (IDP) is the sum of all tech & tools that a PE team binds together to pave golden paths for developers helping operations structure their setup & enable developer self-service & drive standardization by design across the application lifecycle🔧
5/9 Think an internal platform that includes diff techs & tools, glued together in a way that lowers cognitive load on devs w/o abstracting away context & underlying tech.
PE done right means providing golden paths & paved roads that match the pref abstraction level of the dev
6/9 And now the why? In the past, the "throw over the fence" workflow led to poor experiences on both sides of the fence. DevOps emerged as a solution to this problem.
As cloud native technology advanced, setups became more complex.
7/9 But then we enter the last few years, with engineers having to master a buttload of different tools just to deploy and test a simple code change.
8/9 The DevOps paradigm was championed as the way to achieve a high performing setup. Devs should be able to deploy & run their apps & services end to end.
For most, this is unrealistic. Antipatterns tend to emerge when trying to work true DevOps in a regular engineering org
9/9 And so, in comes PE. It brings with it a more efficient, more effective way of working that results in less cognitive load for devs.
If you're reading this, you're halfway there! If you want more, make sure to check the Slack & engage with other PE & platform nerds🔥
• • •
Missing some Tweet in this thread? You can try to
force a refresh
1/9 DevOps is not platform engineering, and platform engineering is not DevOps
I see a lot of confusion on this topic and so want to break it all down. What actually is #platformengineering?
And why do I think it's going to change everything?
A thread👇
2/9 First, what actually is DevOps?🤔
Simply, DevOps is the combination of cultural philosophies, practices, & tools that increases an orgs ability to deliver apps & services at high velocity
It’s not some next level dev, or super engineer. It’s a set of practices and tools
3/9 “You build it, you run it”🛠
Anyone who suffered through the “throw it over the wall" to operations model of development knows how big a game changer DevOps was
2/8 First, what does a platform engineer (PE) actually do? Basically platform engineers provide an integrated product most often referred to as an “Internal Developer Platform” covering the operational necessities of the entire lifecycle of an application💻
3/8: Platform engineers are going to need to work hands-on with software and cloud-native infrastructure, we’re talking AWS, GCP, and Azure. And you want a strong understanding of Infrastructure as Code (IaC) and/or GitOps plus required tooling.
After a few months of combing through #PlatformCon talks for the best platform engineering insights, surveying the folks in our community, and digging deep into the best resources we could find...
We dove into the hottest topics, like:
✅The emergence of platform engineering
✅The platform tooling landscape
✅Platform engineering salary comparison
✅Community growth and opportunities
And imagine trying to force a one-size-fits-all approach onto you team.
It would be (and often is) a disaster 🧵
BUT.
“This is the niche where platform engineering and internal developer platforms are striking: In an ideal '#DevOps done right' world the devs should be able to self-service themselves the resources they need without needing to learn that much on the operations side.”
Linking to the original comment on Reddit here because I hit the character limit 🥲: reddit.com/r/devops/comme…