Sky Sports - Real-Time Sports Data Platform for 11M Users
Replaced legacy Flash-based live scores system with scalable hybrid application serving real-time sports data to 11 million active users across web, iOS, and Android.
Project Goals
Replace end-of-life Flash technology with modern hybrid application, deliver real-time sports scores from stadiums to millions of users with sub-second latency, build scalable API infrastructure to handle massive traffic spikes during major sporting events, and ensure pixel-perfect design on retina iOS devices.
The Problem
Adobe was killing Flash, and Sky Sports' entire live scores platform ran on it.
Millions of football fans checking scores during matches. All of them about to lose access when browsers stopped supporting Flash.
The timeline was tight. The stakes were high. Downtime during a Premier League match wasn't an option.
Oh, and the backend API? That was falling over during big games too.
What We Built
We rebuilt everything—frontend, backend, mobile apps—while keeping the old system running. No downtime. No disruption. Fans checking scores during matches never noticed we were basically rewiring the entire platform underneath them.
The New Frontend
Flash didn't work on mobile. Half of Sky Sports' audience was on phones. This wasn't just a replacement project—it was an expansion.
We built a hybrid application that worked everywhere:
One codebase. Three platforms. iOS, Android, web—all getting the same experience.
Native performance where it mattered. Web technologies where they made sense. The best of both worlds.
The design had to be pixel-perfect on retina displays. Art directors notice when things look fuzzy. We made sure they didn't have anything to complain about.
The Real-Time System
Live scores aren't valuable if they're late. Fans want to know what's happening before the TV broadcast shows it.
We built a real-time pipeline that moved data from stadiums to screens in under a second:
Direct feeds from venues. Multiple data sources for redundancy. WebSocket connections pushing updates instantly. No polling, no delays, no refresh button.
When a goal happens, 11 million phones buzz within seconds. That's the requirement.
The Backend Rebuild
The old API had a problem: it treated every request the same. Didn't matter if you wanted real-time updates or just checking yesterday's scores—same slow process.
We rebuilt it event-driven:
Updates only happen when scores change. Not every second whether something happened or not.
WebSocket connections for live matches. REST APIs for historical data. The right tool for each job.
Caching everywhere it made sense. Geographic distribution to reduce latency. Auto-scaling for traffic spikes.
Handling the Chaos
Sports traffic is predictable chaos. You know exactly when matches start. You have no idea how many people will watch.
A regular Saturday: Moderate traffic.
Cup final day: 11 million concurrent users.
The system had to handle both without manual intervention.
We built auto-scaling that actually works. Traffic goes up, servers spin up. Match ends, servers spin down. Infrastructure costs track actual usage instead of "what if" scenarios.
The Launch
You don't just flip a switch on something this big.
We ran old and new systems in parallel. Gradually shifted traffic to the new platform. A/B tested with real users during actual matches.
Started with friendlies (low stakes, low traffic). Moved to league games. Finally, the big one: Champions League finals.
Zero downtime. Zero complaints. The biggest test of all was when nobody noticed we'd changed anything.
Well, except for the mobile users. They noticed they could finally check scores on their phones.
The Results
11 million concurrent users during peak events. The system handled it without breaking a sweat.
Sub-second latency from stadium to screen. Faster than TV broadcasts. Fans saw goals before the commentary.
Zero downtime during major sporting events. Not during the migration. Not during launches. Not during Champions League finals.
100% Flash replacement. Every platform. Every device. All working.
Mobile access unlocked. Half the audience could now use a product that literally didn't work for them before.
Error detection and response improved 90%. We knew about problems before users noticed them. The old system? Users called to tell us it was broken.
What We Learned
Real-time at scale is about architecture, not just speed. You can write fast code all day. But if your architecture fundamentally can't scale, fast code doesn't matter.
Event-driven design. Async communication. Geographic distribution. Caching strategies. That's what handles millions of users.
Hybrid apps can match native performance. For content-driven applications, hybrid frameworks deliver 90% of native performance at 50% of the development cost.
Three platforms from one codebase. Same features. Same updates. Half the team.
Sports traffic requires special planning. It's not like SaaS where usage grows gradually. It's zero to millions in minutes, sustained for two hours, then back to baseline.
Auto-scaling isn't optional. It's the only way to survive without massive infrastructure waste.
Observability beats reactive support. Knowing about problems before users do transforms everything.
We went from learning about outages from phone calls to catching issues in monitoring dashboards before they affected anyone.
Gradual migration beats big bang. A/B testing with real users during real matches gave us confidence. If something went wrong, we could roll back instantly.
The boring, careful approach wins when downtime isn't acceptable.
Sky Sports fans expected scores to just work. During the biggest migration in the platform's history, that's exactly what happened. They just worked.
Need help building real-time applications at scale? Let's talk →
See more platforms we've built View case studies →