mysql - Scalable status updates / private messaging for a rails social network app -


I am trying to learn more about scalability for ROR. I have a basic social networking app that is currently available Using MySQL to store everything (user relationship, status update, private message)

NoSQL database is ideal sound but are they able to effectively view / retain the relationship RDBS? Or a hybrid solution would be more ideal (only store status updates and private messages in NoSec DB)

How will an AMQP solution fit for status updates? Do I have the process of reading from the status updates queue and it is going to expel all followers / friends (XMPP?)? It looks like as if it can turn into obstacles, as long as I keep increasing threads / processes to stop the thread.

Or should I just take the Twitter route and stick MySQL? Any thoughts / suggestions will be helpful

thanks.

Someone else is wandering in the same path, there is a Ruby on the Railway Open Source Project It has already addressed many of these issues.

In addition, if your application is based on heavy real time updates, then it may be a better idea of ​​implementation in Node.js or Erlang.

Comments