60% faster partner APIs
before1.0×
after0.4×
Finding slow SQL behind partner-facing APIs with OpenTelemetry tracing, then removing expensive joins, partitioning indexes and shrinking payloads.
/database-performance
Database and query performance, measured
I started my career building database performance tooling, and I have been tuning databases since. My approach: profile first, change one thing, measure again.
What I've done
- Cut partner API response times 60% by removing expensive joins, partitioning indexes and pruning payloads.
- Fixed endpoint timeouts using SQL analysis, database performance tools and OpenTelemetry tracing.
- Reduced production cache memory 44% (peak utilization 94% → 56%) and built a shared client library with cluster-aware pooling and sane TTLs.
- Moved cache serialization from Java to Protobuf 3 with zero downtime, saving over $1M a year.
- Co-founded a SQL performance review committee; built storage growth prediction that was 70% more accurate.
Related case studies
Cutting cache memory 44%
before100%
after56%
Key-level memory profiling and a shared Redis client library cut cache memory 44%, peak utilization from 94% to 56%, and ended connection drops.
Switching cache serialization to Protobuf
Zero downtime; over $1M a year saved.
A reusable Spring Boot annotation moved cached objects from Java serialization to Protobuf 3 with zero downtime and over $1M in yearly savings.