The fact that you'd lose all capability for sharing any common relationships, tagging, and other benefits, plus the extra resource demands, would seem to suggest it doesn't make any sense to use Neo4J in a "database per user" manner. Would you do that with any other type of data store? Almost certainly not, so I wouldn't do it with Neo.
-------- Original Message -------- Subject: [Neo] a lot of small embedded databases or one big? From: TuX RaceR <tuxrace...@gmail.com> Date: Sun, April 11, 2010 7:00 am To: Neo user discussions <user@lists.neo4j.org> Hello Neo4j Users! I'd like to store tree data attached to users of a web application. As each user tree depends only on the user, I have the choice of store the user data on a user file. (This is some kind of easy sharding) Is there some kind of problem in creating many small database files? Thanks TuX _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
