Eliminating lock starvation in a high-concurrency service
How replacing a single global Redis lock with an append-only event log removed lock starvation and write races in a high-concurrency service.
Staff Software Architect · Austin, TX
I'm Mohammad Al-Khani. I design distributed systems, tune databases and build the platforms engineers ship on. 14 years of it.
Five areas, each backed by shipped work.
/distributed-systemsLocking, sharding and data models that hold up at peak traffic.
/database-performanceSQL tuning, indexing, caching and memory engineering, measured with OpenTelemetry.
/platform-engineeringTerraform, Atlantis, ArgoCD and Kubernetes paved paths with read-only cloud access.
/cloud-finopsCost visibility and architecture changes that cut spend without cutting reliability.
/developer-experience-aiReusable CI/CD, onboarding tooling and AGENTS.md review rules.
/case-studiesCase studies with the problem, the approach and the measured result.
Agile, two-week sprints. Planning and design come first; build, review and test overlap; the retro feeds the next sprint.
Problem, approach, and the measured result.
How replacing a single global Redis lock with an append-only event log removed lock starvation and write races in a high-concurrency service.
Key-level memory profiling and a shared Redis client library cut cache memory 44%, peak utilization from 94% to 56%, and ended connection drops.
Finding slow SQL behind partner-facing APIs with OpenTelemetry tracing, then removing expensive joins, partitioning indexes and shrinking payloads.
I'm a Staff Software Architect and Backend Engineering Lead at General Motors, based in Austin, Texas. Over 14 years at GM, Life360, Upstart, CodeObjects and Oracle, I've decomposed monoliths, removed distributed locking bottlenecks, rebuilt caching layers and built the platforms other engineers depend on.
A system is only as good as its observability and maintainability. I profile before I change anything.
Savings come from changing architecture, not from cutting reliability.
Paved paths, reusable workflows and clear guardrails beat documentation nobody reads.
Mentoring, reviews and hiring are part of every senior engineer's job.