Something really big is coming - the era of Platform Orchestration. From Thoughtworks to Microsoft and back; There's no denying. Platform Orchestration is reading in abstract relationships between workload and dependent resources provided by the application developers. Based on the context (I'm deploying this app to staging) the Orchestrator picks the right recipe and updates/creates app and infra configurations. It does this dynamically with every deployment. If the recipe changes all impacted resources get updated. If the workload has a new dependency (a new DB of type Postgres for instance) this will automatically be created across all environments. The implications are extreme: - Zero load on the developer -> speed (4X the deployment frequency) - 95% less configuration surface area -> we only need a fraction of the ops FTEs we needed in "old" setups. - hyper-converged infrastructure. It simply doesn't matter where you run. This isn't science fiction, it's a reality. We're running this at large scale at the Enterprise. You can keep looking away for another year but you will not be able to escape it. Every single enterprise will have an Internal Developer Platform. Every single Internal Developer Platform will have a Platform Orchestrator. And sure, you can try to mimic this in bash scripts and Terraform. Just like you built the first CI yourself. But no matter how much invest, you will not remotely meet the sophistication level, security and feature-richness Humanitec Orchestrator will give you. Your cost of ownership will be in no proportion. Brace yourself - 2024 is coming. And with it a level of automation you considered impossible. And don't ever tell me again you can do this with Backstage. You can't. https://lnkd.in/gDpbXB9j
Anton Weiss
10mo
Kaspar, why would anyone think orchestration can be done with Backstage? Even if the rest of your claims seem plausible this last sentence makes the whole post sound like competition bashing done for its own sake.
Pierre Noel
9mo
Most places are not even able to think about reusability or software architecture. They can't even comprehend platforming and push back when you try approaching those concept. So to say that this is an era is a bit far fetch
Pavel Pikat
10mo
Do you support non-Kunernetes workloads yet? "Does not matter where you run" is quite a bold statement. Last time I checked Humanitec was Kubernetes-only tool.
Chris Ford
10mo
From the point of view of the user, could I think of this as a "declarative platform"? Does that capture the intent of your vision?
Cloud Architect and Sr. Developer | 9xAWS certified | Azure
10moJust what ChatGPT says of the text: The provided text appears to utilize a propaganda style known as "Card Stacking." This technique involves presenting only one side of the argument in a way that heavily favors a particular product, idea, or solution, while dismissing or understating alternatives. Here's a breakdown of how "Card Stacking" is used in the text: Selective Presentation: The text emphasizes the superiority of the "Humanitec Orchestrator" by highlighting its sophistication, security, and feature-richness. It presents it as the optimal solution for Internal Developer Platforms. Dismissal of Alternatives: Alternatives like bash scripts and Terraform are mentioned, but they are quickly dismissed as inadequate in comparison to the proposed solution. This creates a biased view that other methods are inferior. Lack of Comparative Analysis: There is no objective comparison between the Humanitec Orchestrator and other methods. The text assumes the Orchestrator's superiority without presenting any evidence or detailed analysis.