DevOps is dead ๐, long live Platform Engineering!
1) Developers don't like dealing with infra
2) Companies need control of their infra as they grow
Platform Engineering (and Internal Developer Platforms) enable these two facts to coexist. Here's how:
(1/n)
1) Developers don't like dealing with infra
2) Companies need control of their infra as they grow
Platform Engineering (and Internal Developer Platforms) enable these two facts to coexist. Here's how:
(1/n)
Fact 1: Most developers don't like dealing with infrastructure.
They want to write code and run it somewhere but don't care much where that is.
Functions as a Service (e.g. Lambda) or Platforms as a Service (e.g. Vercel) provide this experience.
(2/n)
They want to write code and run it somewhere but don't care much where that is.
Functions as a Service (e.g. Lambda) or Platforms as a Service (e.g. Vercel) provide this experience.
(2/n)
Fact 2: As a company/organization grows, its needs may "outgrow" the constraints imposed by the FaaS and PaaS offerings.
The challenge then becomes moving up the control axis without exiting the Developer Comfort Zone.
This is where platform engineering comes into play!
(3/n)
The challenge then becomes moving up the control axis without exiting the Developer Comfort Zone.
This is where platform engineering comes into play!
(3/n)
Platform engineers build the tooling and abstractions around the complex infrastructure configurations such that most software engineers don't need to worry about those aspects as much.
The resulting system is what is known as an "Internal Developer Platform" (IDP)
(4/n)
The resulting system is what is known as an "Internal Developer Platform" (IDP)
(4/n)
The exact form of an IDP will vary greatly from one organization to the next.
At a small company, it could be a set of helm charts that prescribe best practices for deploying services.
At a large company, it might be a fully automated Infrastructure as Code solution.
(5/n)
At a small company, it could be a set of helm charts that prescribe best practices for deploying services.
At a large company, it might be a fully automated Infrastructure as Code solution.
(5/n)
The key is that it provides the control the company needs while keeping the DevOps effort within the Developer Comfort Zone!
(6/n)
(6/n)
I recently spoke with Chris Stephenson of @humanitec_com and we did a deep dive on IDP's. The interview can be found on my YouTube Channel here:
In that discussion, Chris highlighted many of the key elements/design principles of IDPs:
(7/n)
In that discussion, Chris highlighted many of the key elements/design principles of IDPs:
(7/n)
1) Treat the Internal Developer Platform as a product!
Your customers are the developers using it. Get feedback from them, iterate, and confirm that you are solving real problems and not building in a vacuum.
(8/n)
Your customers are the developers using it. Get feedback from them, iterate, and confirm that you are solving real problems and not building in a vacuum.
(8/n)
2) Enable self-service!
IDP's empower developers to get their code running, without the need for intervention from someone else. This greatly increases their ability to quickly iterate on their solutions and leads to increased developer velocity.
(9/n)
IDP's empower developers to get their code running, without the need for intervention from someone else. This greatly increases their ability to quickly iterate on their solutions and leads to increased developer velocity.
(9/n)
3) Provide structure and standardization!
On the flip side of self-service, IDPs provide the opportunity to standardize how resources are provisioned and configured. It offers a place for operations and security teams to encode best practices into the system.
(10/n)
On the flip side of self-service, IDPs provide the opportunity to standardize how resources are provisioned and configured. It offers a place for operations and security teams to encode best practices into the system.
(10/n)
Internal Developer Platforms evolve alongside engineering orgs
A 10-person startup has very different needs from a 1000-person corporation!
However, strategically designing the developer experience is critical at any scale and Platform Engineering / IDPs are the future!
(11/n)
A 10-person startup has very different needs from a 1000-person corporation!
However, strategically designing the developer experience is critical at any scale and Platform Engineering / IDPs are the future!
(11/n)
Found this thread helpful?
Like/retweet the first tweet and follow me
@sidpalas for more Platform Engineering content! ๐
Like/retweet the first tweet and follow me
@sidpalas for more Platform Engineering content! ๐
https://twitter.com/sidpalas/status/1551936840453820417
โข โข โข
Missing some Tweet in this thread? You can try to
force a refresh
ใ
