-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sean Clark Hess wrote: > Our system will have comments related to live data - imagine people > commenting on tweets right after they are written. > > I'm having trouble deciding how to model it. It makes a lot of sense to make > one document containing all the comments for each data segment, but we could > theoretically have hundreds of users commenting on the same segment at > once.
It is surprising how often this question comes up. Fortunately there is a good answer :-) http://www.cmlenz.net/archives/2007/10/couchdb-joins > Is Couch DB a bad fit for an update-heavy system? It shouldn't be. In any event make sure you benchmark your system using your representative data and activity patterns no matter what approach is used as that data, concurrent connections, disk speeds, RAM etc can all have an effect. http://jchrisa.net/drl/_design/sofa/_show/post/Benchmarking-CouchDB http://books.couchdb.org/relax/reference/high-performance Make sure your benchmarking uses concurrent connections. CouchDB tends to have lower maximum performance when only using a single connection, but as you add more connections keeps on going while many other databases degrade very quickly. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAks5rJQACgkQmOOfHg372QTRAACfW2YpBs0kt6cDqpO5ZGUCwFId kesAn3/xPcRISJqr7t85HLvrt4rTt/FC =j2qb -----END PGP SIGNATURE-----
