Platform engineering
Articles tagged Platform engineering — notes and deep-dives grouped under this topic.
-
Kubernetes multi-tenancy: namespace, vCluster or a separate cluster
The three models are usually laid out on one scale — cheap and weak on the left, expensive and solid on the right. The scale breaks in two places, and the decision rests on three independent questions.
-
DORA metrics and the SPACE framework: measurement that doesn't break teams
How many metrics does DORA have — four or five? The answer changed in 2025, along with the Elite–Low levels and the name of the organisation itself.
-
Atomic static site deploys where there is neither git nor transactions
An atomic static site deploy without git on the server: the receiving end offers only scp and ssh. No transaction can be built from that, but a deploy that survives a drop and repeats without consequence can.
-
Crossplane vs Terraform: a control plane instead of a state file
Terraform keeps a snapshot of state in a file and reconciles it on demand; Crossplane turns the Kubernetes API into a control plane and reconciles continuously. What version two changed, where continuous reconciliation wins and what it costs.
-
Argo Rollouts: canary and blue-green with metric-driven auto-rollback
A standard RollingUpdate declares success once pods pass the readiness probe. Argo Rollouts turns the release into a testable hypothesis: stepped canary traffic, blue-green with preview, PromQL-driven AnalysisTemplates and SLO burn rate as an automatic rollback.
-
Multi-cluster ArgoCD: hub-and-spoke vs per-cluster and where both need pull-mode
Hub-and-spoke is the default, but it breaks against blast radius, inbound networking and compliance. When to pick per-cluster local, when pull-mode, and what a hybrid without ideology looks like.
-
Policy as Code in the AI-code era: the speed-versus-control paradox
Production-code velocity now outruns human review. Without deterministic guardrails at CI and admission, an AI agent turns into an amplifier of mistakes — not throughput.
-
The golden path as a product: why the thinnest viable platform beats the five-year build
Build the platform thin — one path at a time — and standardize the process before you automate it. Otherwise you ship a monument no one uses.
-
Internal Developer Platform: Six Layers and Three Adoption Drivers
An IDP isn't "yet another portal" — it's a product for developers. Why platform engineering took off now, the six layers a working Kubernetes platform is built from, and the four mistakes that kill a portal in six months.