<p>Is it possible to create "federated" Subversion servers?
As in one server at location A and another at location B that sync up their local versions of the repository automatically.  That way when someone at either location interacts with the repository they are accessing their respective local server and therefore has faster response times.</p>

[{'answer_id': 1794, 'author': 'Peter Coulton', 'author_id': 117, 'author_profile': 'https://Stackoverflow.com/users/117', 'pm_score': 2, 'selected': False, 'text': '<p>Sounds like you might like <a href="http://git.or.cz/" rel="nofollow noreferrer">Git</a>. There\'s a Google Talk <a href="http://www.youtube.com/watch?v=4XpnKHJAok8" rel="nofollow noreferrer">explaining all about it</a>.</p>\n'}, {'answer_id': 1806, 'author': 'shsteimer', 'author_id': 292, 'author_profile': 'https://Stackoverflow.com/users/292', 'pm_score': 0, 'selected': False, 'text': '<p>Its probably not exactly what your looking for, but you may be able to implement OS level clustering.</p>\n'}, {'answer_id': 2017, 'author': 'Mat', 'author_id': 48, 'author_profile': 'https://Stackoverflow.com/users/48', 'pm_score': 3, 'selected': True, 'text': '<p>This is more or less the perfect use case for <a href="http://svk.bestpractical.com/view/HomePage" rel="nofollow noreferrer">SVK</a>.  SVK is a command line front end for subversion that works with an entire local copy of the repository.  So your commits, updates, etc. work on the local repository and you can then sync with a master.  I would generally recommend SVK over plain subversion anyway as it makes a lot of things nicer.  No .svn folders, better branching and merging, better conflict resolution.</p>\n'}, {'answer_id': 187292, 'author': 'Bert Huijben', 'author_id': 2094, 'author_profile': 'https://Stackoverflow.com/users/2094', 'pm_score': 3, 'selected': False, 'text': '<p>Subversion 1.5 introduced write through proxy support for webdav servers over the existing SvnSync support that was added in 1.4. This allows you to have local mirrors for retrieving files and history, but commits are committed directly to the master repository. If setup correctly the local mirrors receive the changes immediately.</p>\n\n<p>See the <a href="http://svnbook.red-bean.com" rel="noreferrer">Svn Book</a> for more details.</p>\n'}, {'answer_id': 60893155, 'author': 'bahrep', 'author_id': 761095, 'author_profile': 'https://Stackoverflow.com/users/761095', 'pm_score': 0, 'selected': False, 'text': '<p>There are different ways to implement replication of SVN repositories without using external tools such as <code>SVK</code> (which appears to be abandoned today). The replication of Subversion repositories and servers helps to address the challenges of distributed workflow, and brings performance improvements for geographically distributed teams.</p>\n\n<p>Subversion supports <a href="http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra.writethruproxy" rel="nofollow noreferrer">write-through proxying</a> based on hook scripts and the <code>svnsync</code> tool. And if you use VisualSVN Server you can use <a href="https://www.visualsvn.com/server/features/multisite-replication/" rel="nofollow noreferrer">VisualSVN Distributed File System (VDFS)</a> that has several major benefits over <code>svnsync</code>. For example, VDFS is much faster than <code>svnsync</code> and fully supports locking.</p>\n\n<p><a href="https://i.stack.imgur.com/4XOgs.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/4XOgs.png" alt="enter image description here"></a></p>\n'}]
['https://Stackoverflow.com/questions/1790', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/194/']