{
  "id": 15115439,
  "title": "Pushing Beats Polling Explained: Live Poll Trust Above a Handful of Viewers",
  "url": "https://urgent.news/2026/10/17/pushing-beats-polling-explained-live-poll-trust-above-a-handful-of",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-17T04:11:59.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/liamfoster1844/pushing-beats-polling-explained-live-poll-trust-above-a-handful-of-viewers-3ma3"
  },
  "original_language": "en",
  "account": "The key takeaways from this source are:\n\n1) Pushing beats polling when delivering poll results to viewers because polling creates unnecessary repeated reads that scale poorly with more viewers. Pushing delivers updates only when they actually happen, reducing unnecessary load.\n\n2) The cost of polling comes from duplicated work - more viewers means more reads even when the result hasn't changed. Pushing avoids this by only pushing when the result actually changes, matching the application's actual workload.\n\n3) Trust in the delivery system is critical. The client is untrusted and must be authenticated and authorized for each vote and session. Trust should be enforced at the server level, not simply by the transport layer.\n\n4) Polling state should be kept small - only the poll ID, revision, status, totals and timestamp are necessary. Sensitive data like buyer/seller identity and raw ballots should be stored separately.\n\n5) A snapshot-based approach where each push contains a newer revision of the public poll state is safer. Reconnecting clients should request a fresh authorized snapshot to establish a correct, up-to-date view.\n\n6) Whether to use a managed delivery system or self-hosted solution depends on SLOs and operational constraints, not just aesthetic preferences. Both approaches still need to handle claim scope, authorization, and recovery.\n\nIn summary, pushing poll results rather than polling is more operationally efficient and aligns better with the actual workload. Trust must be established independently of the transport layer, and the system should keep poll state small while using immutable snapshots for reconnects. The choice of delivery mechanism should be guided by SLOs and operational constraints, not just the perceived benefits of a particular approach.",
  "summary": "Short answer: pushing beats polling above a handful of viewers because one state change should not trigger repeated reads for every screen, but treat delivery as an optimization, not as authorization. Scope every subscription token to one session, keep vote acceptance on a trusted server path, and retain a slow refresh route for recovery. Polling is operationally attractive at first because its…",
  "key_points": [
    "Pushing poll results, not polling, reduces unnecessary load and scaling issues with more viewers",
    "Trust must be established independently of transport layer for untrusted clients",
    "Small, immutable poll state snapshots enable reconnects with correct, up-to-date view"
  ],
  "editors_take": "Transitioning from polling to pushing optimizes server efficiency by aligning data delivery with actual workload changes rather than scaling redundant reads alongside an increasing number of viewers.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}