You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is less about handling excessive demand (the existing setup already does that incredibly well, not to toot my own horn) and more just to improve uptime and also potentially response times from the bot.
Essentially, host the different shards of the bot on different servers on different physical nodes rather than how it's currently setup of all the shards on a single container on a single physical server.
Current ideas for this are mainly assuming most of the bot will still be in the same/nearby datacentres however shards will be on nodes all over the world. This is so if a physical server has issues for whatever reason, most shards won't be affected and will go online to handle the increased number of requests.
This idea likely won't be acted on anytime soon, if at all. But I'd like to document this so I know it's something that can be worked on.
The text was updated successfully, but these errors were encountered:
This is less about handling excessive demand (the existing setup already does that incredibly well, not to toot my own horn) and more just to improve uptime and also potentially response times from the bot.
Essentially, host the different shards of the bot on different servers on different physical nodes rather than how it's currently setup of all the shards on a single container on a single physical server.
Current ideas for this are mainly assuming most of the bot will still be in the same/nearby datacentres however shards will be on nodes all over the world. This is so if a physical server has issues for whatever reason, most shards won't be affected and will go online to handle the increased number of requests.
This idea likely won't be acted on anytime soon, if at all. But I'd like to document this so I know it's something that can be worked on.
The text was updated successfully, but these errors were encountered: