CheckPulse
Multi-region uptime, DNS, and SSL monitoring for agencies. Deployed, public, and handling real traffic.
Available for opportunities
I build and operate backend systems end to end: a monitoring SaaS live in production, a Go gateway and a distributed log analyzer, all running on a seven-host vSphere cluster I administer myself.
Flagship work demonstrating system design and engineering depth.
Multi-region uptime, DNS, and SSL monitoring for agencies. Deployed, public, and handling real traffic.
A ~250-line Python watchdog that runs on a different host from the agent fleet it watches, built after a cron job failed 970 times in four days and alerted exactly once.
Go master-worker system that parses a 3.3 GB, 10M-line access log. 36s single worker, 6s at 8-11 workers.
A Go gateway written from scratch: JWT auth with RBAC, layered rate limiting, round-robin load balancing, Prometheus metrics.
dev, staging and production RKE2 clusters on bare vSphere, with VIP failover proved by forcing a leadership transfer rather than assuming one.
Deep dives into infrastructure, DevOps, and building real systems.
Planning and operating production Kubernetes: cluster architecture decisions and declarative GitOps delivery with ArgoCD.
Designing a centralized logging architecture with the ELK stack: what to collect, where it lands, and what it costs to keep.
Patterns I use for CI/CD pipeline design and Terraform at scale.
Three times a green signal meant nothing: a backup that restored an empty file, a failover test that proved the opposite of what it claimed, and a runbook that had never once worked.
I'm a backend and platform engineer. CS graduate from UT Dallas, most useful in Go and Python, and happiest somewhere near the line between an application and the infrastructure it runs on.
Most of what I know came from running things rather than reading about them. I operate a seven-host vSphere cluster at home, and the projects on this site are deployed on it or on a VPS I pay for. which means I am also the one who gets paged when they break.
I try to keep the claims on this site matched to what the code actually does. Where a project is unfinished, its page says so; where there is a number, it was measured. The write-ups include the incidents too, including the abuse of a signup endpoint on CheckPulse taught me more than any of the features did.
I'm always interested in discussing new opportunities, technical challenges, or just chatting about infrastructure.