Closed rico666 closed 6 years ago
ac0v mentioned to do a load balancing not in the app, but in the DNS. I think it is an equivalent, maybe even better solution. This would mean, that e.g. https://wallet.burst.cryptoguru.org would be in fact a geographically distributed cluster of wallets. We are actually half way there already.
Now that the cluster is operational, let them come. ;-)
What would happen if 500 000 people downloaded the wallet and tried to use it?
Our default backend wallet would crash. Ok, they could use alternatives, but that's a hassle.
I propose the backend wallet chosen by the user should actually be a list where the mobile wallet would perform a round-robin in case a wallet would be unresponsive.
While it may not be a problem now, I believe this has to be addressed better sooner than later (if we would run into scaling problems)