On Sat, Jan 10, 2009 at 9:19 AM, Kurt Mackey <[email protected]> wrote: > Now, the obvious downside is that it makes it more difficult to do > cross-customer queries. But what other problems are there with this idea? > Assuming that there were lots and lots and lots of accounts, what performance > implications are there to giving each their own DB rather than making them > all share? >
CouchDB keeps each database in it's own file, so if you can spread the files across disks (using symlinks for now) you should get better performance with many databases. DB-per-user is a good pattern also because it means you can let users replicate their entire account locally, without worrying about filtering out extra data. -- Chris Anderson http://jchris.mfdz.com
