I architect distributed systems that hold up at 3 AM.
Two careers, one instinct: design for the load before you draw the details. I build event-driven architectures, real-time platforms, and the developer tooling that holds them together.
§02 — LOAD-BEARING NUMBERS
SOURCE: PRODUCTION TELEMETRY · 2024–202647-minute pipeline → under 8 minutes via per-app change detection + JIB.
EKS 1.32 + Karpenter v1, solo DevOps owner across a 7-person team.
EventHorizon, the pattern that crystallized after four companies of the same problem.
§03 — FIELD WORK
Selected Case Studies
CI/CD Pipeline Optimization
How I restructured a monolith's build system and CI pipeline: replacing Dockerfile builds with JIB, adding per-app change detection, and cutting pipeline times by 83%.
EventHorizon: The Ultimate Data Detection Engine
Designing a generic, pluggable anomaly detection platform using Apache Flink, Kafka, Micronaut, and ML/LLM integration. The culmination of building similar systems in Ruby, Java, Python, and TypeScript across multiple industries.
EKS Cluster Migrations
Upgrading EKS clusters to v1.32 and migrating Karpenter to v1 across 100+ production services with zero downtime, all as a solo DevOps engineer racing to avoid extended support charges.
Performance Optimization
47-minute CI pipelines down to under 8. JIB + change detection + a structural untangle of 32 Gradle projects.
System Architecture
Real-time anomaly detection on Flink + Kafka. Same backbone, four industries.
Cloud Infrastructure
EKS clusters upgraded to 1.32 across 100+ services. Solo, deadline pressure, zero downtime.
Explorations
Agent orchestration, shared context layers, the next layer of developer tooling.