Full Stack DeveloperGames World League2024 - 2025
Gaming platform performance
Slow PostgreSQL queries on high-traffic endpoints, fixed with query plans and new indexes.
✓ VERIFIED10K+
Daily active usersDaily active users on the platform.The problem
High-traffic endpoints were slow for a platform with 10,000+ daily active users.
What I built
I read the query plans for the slow endpoints and added indexes. I also moved parts of the monolith into Dockerized services with CI/CD.
Architecture
After the split
Parts of the monolith moved into Docker services.
01
Players10,000+ daily.02
Docker servicesMoved out of the monolith.03
PostgreSQLNew indexes from query plans.Players → Docker services · requestsDocker services → PostgreSQL · queries
Decision log
What I chose, and what I gave up
01Indexes based on query plansover adding a cacheThe slowness was in a few high-traffic queries.
The query plans showed where the time went. Indexing fixed those queries directly.
+ Slightly slower writes on indexed tables− Keeping a cache in sync
Scaling story
How it grew
01
Found the slow queriesRead the query plans for the high-traffic endpoints.
02
Split the monolithMoved parts of it into Dockerized services with CI/CD.
Next case studyAI safety guardrailsMissed crisis phrasings went from 21 of 27 to 0 of 24 test cases, with zero false alarms.