Platform engineering is the discipline of designing and building toolchains and workflows that enable self-service capabilities for software engineering organizations in the cloud-native era.

Platform Engineering

Hi <@U04E1FVPJ04>. One of the best talks from today. I got interested in the process of creating new blueprints. Can you elaborate on this and also the process of extending the platform's capabilities? Also, how do you ensure the scalability and maintainability of these blueprints, considering the evolving needs of different engineering teams? Thanks in advance

Hi <@U03GWUX539C>, thank you for the wonderful feedback.

Let me answer the first question about extending the platform’s capabilities. For creating new blueprints you start by surveying and analyzing what are your users using the most, what are the most common compositions or resources - those are good candidates of blueprints. We insist that our blueprints are compositions not abstractions, so the user can always look under the hood if needed. These are the types of blueprints a user experience team can provide to the rest of the company. Next to that, if teams have specific set of resources they often use in their team, but other teams do not - they can build their own blueprint and use it.

`Also, how do you ensure the scalability and maintainability of these blueprints, considering the evolving needs of different engineering teams?`
Blueprints like any "library" need to be versioned and updated properly using either semver or other way of proper version management, so do not introduce breaking changes in stable blueprint versions etc. If using upstream resources when composing your blueprints, think of the update strategy they offer.