Case study · Databases

60% faster partner APIs

Finding slow SQL behind partner-facing APIs with OpenTelemetry tracing, then removing expensive joins, partitioning indexes and shrinking payloads.

before1.0×

after0.4×

Result: API response time: down 60%.

Context

A set of partner-facing APIs served data from a relational database.

Problem

Partner-facing endpoints were slow, and one ranking endpoint regularly timed out.

Approach

Traced requests end to end with OpenTelemetry and database performance tools, then removed expensive implicit joins, partitioned indexes and selected only the columns each endpoint needed.

Result

API response times down 60%.
Ranking endpoint timeouts resolved.

More case studies

Concurrency

Eliminating lock starvation in a high-concurrency service

before100%

after0%

How replacing a single global Redis lock with an append-only event log removed lock starvation and write races in a high-concurrency service.

Caching

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.

Platform

Infrastructure changes through pull requests

Engineers moved to read-only cloud access; every change reviewed and logged.

How I won buy-in for GitOps, moved engineers to read-only cloud access and made every infrastructure change reviewed and auditable.