Rescued a slow API that was blocking user growth
Cuez is a live broadcast production tool used by TV teams on air across Europe. I inherited a backend API averaging 3 seconds per response and cut it to 300ms, while reducing infrastructure costs by 40% and leaving the system stable under real production load.
Always with many ideas to add and open to discuss the best approach to create the most scalable software as possible.
Cuez is live production software. Broadcast teams use it in the control room during live shows to manage rundowns, script cues, graphics, and media triggers — all in real time, all while a show is on air. At 3 seconds average API response time, the system was failing that use case. Operators hit an action and waited, sometimes mid-countdown. The root causes were compounding: database queries on the rundown endpoint ran in N+1 loops without eager loading, FFMPEG media processing ran synchronously on the HTTP thread and blocked every response that touched media, and the infrastructure had been sized to absorb the slowness rather than fix it. Every new production added to the pressure.
Profiled the full request path to isolate the two largest bottlenecks. First, the rundown endpoint loaded related script items, graphics, and cue records in separate loops instead of joining at the query level. Rewrote the Eloquent query layer using eager loading and selective column projection. Second, FFMPEG media processing was running synchronously and blocking the HTTP response. Moved it to an async queue via Laravel Horizon, fully decoupled from the request cycle. Added a Redis caching layer over the most-read rundown objects. Realigned AWS resource allocation to the actual post-optimization workload — the infrastructure had been over-provisioned to compensate for slow code. Response time dropped from 3 seconds to 300ms.
Laravel 10 with Eloquent query layer rewritten for eager loading and selective column projection. Redis caching for hot rundown objects. FFMPEG media processing moved to async queue via Laravel Horizon, decoupled from the HTTP response cycle. AWS instance sizing revised to match the real optimized workload profile. Vue.js frontend with TypeScript.
Results
Measurable outcomes that drove real business value
Core API latency cut by 90% (10x). Broadcast teams stopped waiting mid-production.
Optimized queries and async processing cut resource consumption. Same infrastructure, more headroom for new productions.
System now handles real broadcast loads without degradation. Teams run shows on Cuez with confidence.
Project Gallery
Visual highlights of the delivered solution
Endorsed by Technical Peers
See what Engineering Managers and Senior Developers say about working with me.
I strongly recommend Adriano as a highly competent and qualified back-end developer. I had the pleasure of working with him in the same company and it was always a great experience. He is an experienced professional, always open to new ideas and innovations, and careful with the code, ensuring the quality and efficiency of teamwork. In addition, Adriano has a very positive and collaborative attitude, and it has always been a pleasure to work with him. Undoubtedly, he is a great addition to any development team.
Adriano is a great software engineer. Always with many ideas do add and open to discuss the best approach to create the most scalable software as possible. Adriano is an extremely easy person to work with and very dedicated to their job. It was a huge pleasure to work with him.
Further Reading
Custom Web App Development: Process, Cost & What to Expect (2026)
A founder's guide to custom web applications — from defining scope to understanding what drives costs.
Custom Web App Development: Process, Cost & What to Expect (2026)How to Build an MVP with Laravel and React: Timeline, Cost & Process
Step-by-step guide to shipping a validated MVP using Laravel and React without over-engineering.
How to Build an MVP with Laravel and React: Timeline, Cost & ProcessAPI Integration Guide: Connect Your Systems and Scale
How to connect your business systems with APIs — REST, GraphQL, security, and real implementation costs.
API Integration Guide: Connect Your Systems and ScaleWant a similar result?
Tell me what you need in 60 seconds. Tailored proposal in your inbox within 6 hours.