Stop copying big-tech platform architecture: right-size to your scale
Right-sizing platform architecture means copying the principles behind big-tech systems, not the stack itself, so small teams avoid operational debt they do not need.
Blog
Technical writing on Kubernetes, delivery workflows, cloud foundations, observability, and the systems around modern platform engineering.
Right-sizing platform architecture means copying the principles behind big-tech systems, not the stack itself, so small teams avoid operational debt they do not need.
Learn how to use Argo Rollouts on Kubernetes for canary and blue-green deployments, automated rollback, and GitOps-based progressive delivery.
Karpenter changes EKS node autoscaling by launching right-sized EC2 nodes from pending pods, then consolidating and replacing them as the fleet drifts.
Use KEDA on Kubernetes to scale from queue depth, lag, and schedules, and understand when scale to zero is worth the cold-start trade-off.
Cilium changes Kubernetes networking by replacing more of kube-proxy with eBPF, enforcing identity-aware policy, and adding flow visibility through Hubble.
Use Kueue to queue Kubernetes batch workloads before they hit the scheduler, so shared cluster quota is admitted deliberately instead of all at once.
Use Crossplane to make Kubernetes your infrastructure control plane — a self-service platform API for cloud resources, reconciled continuously.
LLM-generated code arrives quickly, so fast feedback loops for tests, review, and runtime checks matter even more if you want to ship safely.
Node drains are ordinary Kubernetes maintenance, but they only stay boring when replicas are spread out, disruptions are budgeted, and pods shut down cleanly.