Among the many improvements in the latest release of SVN MultiSite Plus, the ability to add new nodes on the fly to replication groups really stands out. SVN MultiSite Plus helps a Subversion administrator cope with uncertainty: you don’t know very far in advance how many developers you have, where they’ll be located, and how much build automation they’ll use. When I worked as a consultant I would often ask these basic questions in the process of hardware sizing for a deployment, but in reality you’re just guessing if you try to figure out how many servers you need years in advance. SVN MultiSite Plus gives you a dynamic Subversion deployment that grows in response to your environment.
As a simple example, let’s say that I start out with three nodes in a single office. After six months I need to add two more nodes to handle additional build automation load, then after a year I need to add a node at a remote site to support a new office. These routine capacity events shouldn’t cause a big disruption to your Subversion service.
With SVN MultiSite Plus I can simply add a new server to the deployment on the fly. After the server is provisioned and configured, I simply go to the administration console and add the new server to the replication group:
After I add a node, SVN MultiSite Plus walks me through the process of synchronizing data onto the new node. While the new node is being synchronized it is not usable, of course, but it is automatically activated once the data transfer is complete.
If you’re tired of constantly scrambling to keep your Subversion deployments up to speed, grab a free trial of SVN MultiSite Plus. If you face the same problem for Git, Git MultiSite offers the same support for quickly expanding a Git deployment.