We Hold These Truths Sacred:
Servers, Disks, Files, & Databases, Meet Geo-Optimized Redundancy
Redundant systems of the modern era require a fault tolerant solution for replicating files and database records across an array of servers each with one or more disks.
Having each of your files and databases copied onto multiple drives is a great way to prevent data loss.
Moving file storage away from your primary server by replicating across multiple commodity servers is a great way to utilize production resources.
The more the merrier!
Perform CRUD operations on any of the servers. Upload files to any server. File storing and fetching is distributed across servers and disks.
Websites of the future will need to offer more and more computing resources to the user in order to compete. The sun sets on the days of running a top million ranked site off a single drive.
Specify the databases you wish to replicate on each of the cluster's servers. Each Replicated Database has a single server specified as the king server and the others are pawn servers. CRUD operations can be made on any server(just update the timestamp and _srvr fields in conjunction). Make any change to the structure of the database on the King Server and it will permeate to each of the pawns.
A server can be added to a cluster by running the flo.php command --JoinCluster with the new cluster King's endpoint and access code specified
Amplify With Confidence
Join the growing list of developers using Huge.Global!
Files should be stored in multiple disks(on separate servers, preferably) to prevent any data loss if hardware failure should occur.