- When a viewer clicks to vote
- That makes a HTTP request to my server
- I score the vote
- I send back the results/current score to the channel every 1 second or slower via Twitch Extension PubSub
- My bare metal server does the counting, don’t need kinesis/cloud for that
If my solution gets close to overloading the server then I’ll add a server to the pool.
Last November/December I was running 3 voting websites and/or extensions off the same single bare metal server. One of which being for The Game Awards.
I got no where near maxing the limit.
At any given point theres between, say 3 to 5 thousand channels live at any given point on Twitch.
Of which, even if you assume half of them are running your extension.
Not all of them will be running a poll to vote on at the same time.
So your peak loads are a concern but your average traffic loads are not.
Billions of inputs/votes can be handle by a single bare metal server if needed without havign to consider the request counts of a cloud solution.
I guess you can start with cloud and if your extension takes off rearchiture the backend to fit within your costing allocations.
Additional case in point I run two game matched extensions which both accept data from the game and sends the collected data to the channels live with the extension each second and it just purrs along. All from the one bare metal server.
Sure theres not generall more than 10 channels live at once with each game extension but that server is also running a hell of a lot of other stuff. Including my IGDB extension which fields quite a fair chunk of traffic at any given point.