To deal with Drupal's growth, we're adding a second database server to drupal.org which is useful for at least two reasons. First, we'll be able to handle more SQL queries as we can distribute them between multiple database servers (load balancing). Secondly, this new server can act as a "hot spare" that can immediately take over if the other database server fails (high availability / fail-over).
The current plan is to configure both database servers in
master-slave configuration, which is the most
common replication model for websites. This model provides
scalability, but not necessarily fail-over. With a master-slave
configuration, all data modification queries (like
INSERT, UPDATE and DELETE
queries) are sent to the master. The master writes …