
How I Built a Two-Tier Data Platform in 9 Phases (Spark, Kafka, dbt, Kubernetes)
A complete data platform — batch + streaming, single-node + distributed, local + Kubernetes. What I built, what broke, and what I learned.
Tag archive

A complete data platform — batch + streaming, single-node + distributed, local + Kubernetes. What I built, what broke, and what I learned.

Knowing what LLM you're routing to, whether or not failover for more expensive tasks exists, what...
Temporal Workflow for Microservices: Why We Replaced 40 CronJobs With One Engine We...
Linkerd in Production: 18 Months, 220 Services, Zero Mesh-Wide Outages We replaced Istio...
OPA Gatekeeper in Production: 18 Months, 47 Policies, Zero Bypass Incidents We adopted OPA...
We built a cost monitoring stack for EKS that reduced waste by 40% in the first month — not through automation, but by making costs visible to the teams creating them. Kubecost, Prometheus, Grafana, CloudWatch alarms, and Slack alerts with real configs.

This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend What I...
WebAssembly's origin story is the browser. Designed to run near-native-speed code in web...
A page saying "checkout API unavailable" is already late. The on-call needs to see which pods stopped...
PostgreSQL Point-in-Time Recovery in Kubernetes: WAL-G + Stolon Pattern We recovered a 2TB...
Karpenter Consolidation Isn't Magic: The 4 Configs That Matter We adopted Karpenter in...
Crossplane Composition vs Helm: When Each Wins We migrated our multi-cloud resource...