Ruby on Rails Thursday, September 12, 2013


I think the   User->HasOne->Profile association will be OK. From there you can go searching for more efficient database calls.



On Thursday, 12 September 2013 03:16:45 UTC-5, Yash Ladia wrote:
I am working on a social networking project. I need to store about 10-15 user profile information like movies,music,books,relationship-status and so on. I am confused about which database should i use to store user profile info. There are NOSQL solutions like MONGODB as well as Neo4j(graph). Or should i store it in relational database like mysql. Needless to say, but the solution should be scalable and efficient. Any guidance on this would be of great help. 

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/f2f775b4-b568-4f2a-a3fd-0ff90d2d7bab%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment