Scaling and reliability
A backend that kept up with fast growth and went down less often.
Tech Lead at Sourcy Global, Feb 2024 to Dec 2025. Database and backend work as Full Stack Engineer, Aug 2023 to Jan 2024.
- 30%
- month-over-month growth in transaction volume that the infrastructure was scaled to support
- 25%
- less platform downtime after introducing monitoring
- 40%
- faster database queries through normalization, indexing and caching
Problem
Transactions were growing 30% month over month. Growth like that compounds: by month 12, after 11 months of it, traffic is almost 18 times month 1. The backend had to keep up, stay fast and stay up.
Approach
We designed the backend as modular microservices and scaled it with cloud optimization and serverless functions that grow with traffic. Database queries got faster through normalization, indexing and caching. Monitoring now watches the system and raises alerts. CI/CD and testing keep changes safe to ship.
Result
We scaled the infrastructure to support a 30% month-over-month increase in transaction volume. The growth came from the business; the work was keeping up with it. Database query response time fell 40% through normalization, indexing and caching, and platform downtime fell 25% after we introduced monitoring. Drag from month 1 to month 12 of 30% monthly growth below, then turn the cache off to see what the database would face.
Simulation
Serverless functions running: 1
Database load: 5% of capacity
Need something like this built?
Pick a 30-minute slot and tell me what you're building.