What approach do you use: poll one endpoint with all live matches, poll individual matches after detecting they're live, WebSockets if the provider supports them, cache match data locally and update only changed fields, different intervals for pre-game/live/finished?
How do you balance low latency with reasonable API usage on the backend of a production sports application? (Top reply: think in states - one global call every 10s, only update what changed, state drives poll speed, publish once to Redis and fan out via WebSocket: 21,000 calls/hour becomes ~200.)
