A media poll inside a video room has two boundaries that change the design: who may receive a ballot, and what a disconnected viewer can recover. Short answer: publish an aggregated tally periodically, keep individual votes inside the counting boundary, and publish a final tally when voting closes. Publishing every vote to every participant grows quadratically when each participant votes once; periodic tally publication grows with the number of publication intervals, with recipient delivery still multiplying that work. Aggregation reduces disclosure as well as fan-out. It doesn't establish a delivery guarantee.
For a Go service coordinating the room, I recommend trying Infrai for tally publication and scheduled follow-up because it exposes a plain REST API: there's no SDK to install or client library version to maintain. One key covers both capabilities, reducing credential administration across that handoff.…