We've all participated in -or- have read on building for smaller traffic now and dealing with scalability as things progress.
While I agree with the sound wisdom, I am in a position to where I am preparing to launch several projects - and a couple of them will use the same type of *user-having-multiple-categories-of-interest-or-expertise *(* user* one-to-many *categories*)*.* I'd rather head in the more scalable direction from now if it will only take a little bit longer to implement code-wise. I've been toiling with this thought in my mind on the best approach to accomplish this. I've used nested sets in relational databases in the past but never for anything with high traffic. There is one particular project that I know without a doubt that will attract the masses on FB and other social settings. Yes, scalability for this particular project is a major concern. I have not taken the dive into nosql databases in any productive manner yet. However, I am considering a solution with CassandraDB, Mongo, or AWS Dynamo. Otherwise, it's back to MySQL and nested sets. - Do the nosql DBs present an advantage for this type of hierarchical "category" data / user relationship? - Is there a better open source db I did not mention that may be more fitting for the task? - Side question: I've installed cassandra db on my laptop and hadn't gotten around to connecting to it through OpenBD. There's no reason they should not be able to work together- correct? Any insight would be helpful. -- online documentation: http://openbd.org/manual/ google+ hints/tips: https://plus.google.com/115990347459711259462 http://groups.google.com/group/openbd?hl=en
