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

The IDP space is evolving rapidly. In order to build a dynamic platform that can handle both app and infra configs dynamically, you need to have a Platform Orchestrator at the core of it. <@U02H30PA00P> recently wrote an article on our evolving understanding on the topic. It’s a <https://humanitec.com/blog/what-is-a-platform-orchestrator|good read>, curious what folks here think about it.

Interesting so basically argocd + crossplane with abstration on top?, the blog post is a bit confusing without comparisons

Good idea - so it's in the end an API layer that accepts a declarative application model as input and then dynamically create the representation of the application at deployment time. The orchestrator can be fed with crossplane, TF, really any IaC and it can hand over to Argo as well. What it comes down to is a new approach to configuration management. <https://humanitec.com/blog/what-is-dynamic-configuration-management|Dynamic configuration management>.

`approach to configuration management whereby an entire application, including its dependent infrastructure resources, is described in a Declarative Application Model. This model is consistent across any environment. The deployable representation is generated with every deployment and results into the running application. Applications configured using this dynamic approach are easier to maintain, easier to operate for developers, and allow for higher standardization.`

Ahh makes more sense now, I read some of the other blog posts about it, how is it different from <https://oam.dev/|https://oam.dev/> , think people might draw comparisons to it :relaxed:

Good one! OAM is K8s based. This model doesn't care about what resources + runtime environments it orchestrates.