Picture 40,000 phones in a stadium, each connected, each waiting for a signal. When the operator presses a button, every screen needs to change colour within 100 milliseconds. That is not a software feature. It is an infrastructure challenge. The way it is solved determines whether a crowd display looks spectacular or looks broken.
Why traditional server architecture fails at stadium scale
A conventional client-server architecture, where each phone maintains a connection to a single application server, hits a wall at scale. A single server handling 2,000 concurrent WebSocket connections while also processing commands and broadcasting state changes introduces latency that compounds as load increases. At 5,000 connections, the system degrades. At 20,000, it fails entirely.
Stadium events are also inherently spiky. Connections surge in the 20 minutes before kick-off, hit peak load during the match, and drop sharply at full time. A fixed-capacity server is either over-provisioned and expensive, or under-provisioned and unreliable at the moments that matter most.
How Cloud Run handles elastic load
Google Cloud Platform's Cloud Run service allows containerised applications to scale horizontally based on demand. When connection requests spike (say, 800 fans scanning a QR code in the same two-minute window), additional container instances spin up automatically. When demand drops, they scale back down. You pay for what you use, and you never hit a fixed ceiling.
This elasticity is particularly valuable for crowd display platforms because the load profile is predictable but extreme. You know when the match starts. You know when the most popular effects fire. Cloud Run lets you meet that demand without maintaining expensive always-on capacity for traffic patterns that only occur for a few hours per event.
Pub/Sub as the broadcast layer
The fan-facing problem in crowd displays is not sending a command. It is broadcasting that command to thousands of clients simultaneously and consistently. Google Cloud Pub/Sub is designed exactly for this pattern. The operator's command publishes a message to a topic. Subscribers, the WebSocket connections for each phone, receive it in parallel.
Pub/Sub's delivery guarantees and low latency make it well-suited to real-time broadcast scenarios. It decouples the command sender from the receivers, meaning the system can handle subscriber counts that would overwhelm a direct broadcasting model. Adding 500 more connections does not increase the complexity of the command pipeline: it just adds 500 more subscribers.
WebSocket connections for persistent real-time state
HTTP polling, where each phone checks for updates on a timer, introduces latency proportional to the polling interval. For a crowd display where sub-100ms synchronisation is the target, polling is not viable. WebSocket connections maintain a persistent bi-directional channel between each phone and the server, enabling push notifications the moment a command is issued.
The technical result is that when an operator triggers a goal celebration, the signal propagates to connected phones effectively instantaneously. The visual effect is tight synchronisation: thousands of screens changing colour simultaneously rather than staggering across a second or two.
What the admin view reflects
Good cloud architecture makes the operational experience simpler, not more complex. In platforms like Seatwave, the admin interface shows a live 2D seat map populated in real time as fans connect. Each seat indicator changes state as the fan's phone is assigned to the show. The operator can see at a glance which sections are well-connected and where participation is thin.
- Live seat map: Confirms which phones are active before the show starts
- Latency monitoring: Flags connection quality issues before they affect the display
- Session metrics: Post-event reports on peak connections, command delivery times, and participation by section
The infrastructure is invisible to fans and largely invisible to operators. That invisibility is the point. When the cloud backend is working correctly, the operator thinks about the show, not the technology.
Ready to turn your crowd into the canvas?
Seatwave turns every fan's phone into a synchronized pixel, controlled live from a single dashboard.