Aman, I think to start with, you probably want to set up indexing on only the interesting aspects of your CMS and documents, not everything. Normally, that leads to a much slimmer storage, and better speed in mutating operations.
Given 50K users, the question is how much index-relevant content there will be, and what the peak load of that system is. Do you have any estimations for that? Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Tue, Jun 14, 2011 at 7:24 PM, Aman <[email protected]> wrote: > I've been working on a project (a CMS) that would require a lot of indexing > as it would manage user generated content (mostly strings). Could I get some > suggestions on what is the extent of indexing that can be useful in a > typical CMS which could have a fair use by about 50000 people? And how does > this indexing matter if I have to scale it any further? > > Also, as I said above, the index would mostly deal with strings. Would it be > any better if I put up another layer in front of my neo4j db that maps those > strings to ints so that I could index those easily in neo4j? > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
