[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Multiple vs Single Repositories

From: Irvine, Chuck R [EQ] <Chuck.R.Irvine_at_Embarq.com>
Date: 2007-05-02 20:25:09 CEST

We have a very large number of applications. Our current plan is to have
just one SVN repo with a structure like:


In total, I'd say we have well over a 100 active applications. However,
I'm getting a little nervous about the possibility of a repo corruption
causing all of our application teams to lose SVN access. So, I'm
wondering if a better approach would be to have each application, more
or less, in its own repository.

I'm curious to know the communities opinion on this in general.

Also, if a repo corruption does occur would it usually be isolated to a
single application, or do corruptions often affect the entire repo?

Finally, in general how common are these repo corruptions? I see reports
of them on the mailing list, but perhaps they are really very uncommon.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 2 20:25:30 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.