I don't really understand your plan here. I believe you are talking about autobet system which is available in all dice websites. You need to select your initial bet amount an then few conditions are given like if you would want to increase the bet amount after every win or not and so on. I don't really understand what is the need of the central cloud server to roll the bets! can you please elaborate in clear and concise way? Also I don't think any dice website will allow you to execute even 100 bets per second.
no i'm not talking about autobets.
and you answered your own question
"what is the need of the central cloud server to roll the bets"
Also I don't think any dice website will allow you to execute even 100 bets per second.
they don't allow it because it uses too much resources.
imagine 1000 users playing rolling 100bets per second. they can't do it.
they would need to rent a cloud service to handle processing bets.
and the user would need a way to transfer this data so the bets get processed. ideally this would eliminate 95% of data being transferred.
i'm not sure how to be more clear about this. "and it's my fault idk how to put it into words.
i think everyone is getting caught up in the purpose more then the question.
the virtual machine will act as a middle man
instead of the normal way user sending data the the server then vice versa.
the user would send data to the vmachine with predefined settings then the vmachine would send data back and forth to the server. on a local network
removing almost all latency. "besides the bet history the user would be shown"