Forum Discussion

vibedriftreal's avatar
vibedriftreal
Copper Contributor
Oct 07, 2026

Azure SignalR vs Web PubSub for a real-time live score website – which one fits better?

Hi everyone,

I'm building a live football score website from scratch as a personal project, mostly using AI-assisted coding. The core requirement is pushing score updates, match events (goals, cards, substitutions) and minute changes to visitors in real time without them refreshing the page.

I'm considering Azure for the real-time layer and I'm trying to decide between Azure SignalR Service and Azure Web PubSub. Traffic will be uneven: quiet most of the week, then spikes of concurrent users during big matches.

A few questions:

1. Which service handles sudden traffic spikes more cost-effectively?

2. Is Web PubSub simpler if my backend isn't ASP.NET?

3. Would polling an external score API every few seconds and broadcasting changes be a reasonable architecture, or is there a better pattern?

Any experience or advice would be appreciated. Thanks!

2 Replies

  • Jamony's comparison is the right one, so I'll just add the bit that matters most for a personal project like this: you don't need an always-on backend at all.

     

    Both services have a serverless mode through Azure Functions, and that's the shape I'd build this in. A timer-triggered function does the polling — one function, every few seconds, calling the score API once — and then pushes only the changes out through the service's output binding. For SignalR that's the SignalR Service output binding for Functions; Web PubSub has the same idea with its own Functions trigger and bindings. Either way there's no app server to keep running and pay for between matches, which is where the cost difference actually shows up for a hobby site: you're paying for function executions and messages, not an idle VM or App Service plan.

     

    On the choice itself, Jamony's steer holds: Web PubSub if you want plain WebSockets and a publish call from any language, SignalR if you want the hub model and its client libraries. And start both on the free tier while you're proving it out — 20 concurrent connections and 20,000 messages a day is plenty to find out whether your polling rhythm and group-per-match design hold up under a real match, before you spend anything on a paid tier.

  • For your live scores, Web PubSub is a good fit if you want straightforward WebSocket publishing from a non-ASP.NET backend; choose SignalR when its client libraries, hub model, RPC, or transport fallbacks are useful. Neither is automatically cheaper during spikes: compare concurrent connections, allocated unit-hours, outbound message volume, and region-specific pricing. Broadcasting one update to thousands of viewers multiplies outbound traffic. Web PubSub autoscale requires Premium and usually takes minutes, so schedule capacity before major matches and keep headroom. Use one backend polling worker, subject to the score provider’s rate limits, rather than letting every visitor call the external API. Cache the latest match state, publish only changes to match-specific groups, and serve a snapshot when clients connect or reconnect. If the provider offers webhooks or streaming, prefer that input. Test a match-day load profile and cost estimate before choosing the production tier.