Scaled databases
Closed this issue · 1 comments
Storing everything under one database server is not only a horrible idea but could lead to performance issues but storage issues as well, when multiple servers are available at disposal; it is a good idea to setup more than one component servers to work together and use a pre-defined prefix to identify the server to retrieve and send data to
This will require a rewrite and an additional component to SocialvoidLib called “Slave Server” which will serve the purpose of handling queries and operations for that specific server while the master server will have a configuration file that tells the master server where and how to contact the slave servers.
Added scaled databases and it seems to be working accordingly, more scaled services can be added down the road and more managers can supported scaled objects.