mysql v mongodb - best solution for a complex user focussed site? -


i've spent few days researching pros , cons of mysql against nosql solutions (specifically mongodb) project.

the project needs able scale handle tens of thousands of simultaneous users - millions of users in total. site heavily user focussed , interact database if not more site facebook - relational, functionality dependant on relation user , relationship other users. it's data heavy - lots of files, images, audio, messaging, personal news feed etc.

i on mongodb lot, way works, , how scales - can't head around how work site such describe. interactions specific user have stored in single document?

i comfortable using mysql , relational aspect of it. worried without lot of work there scalability issues project - although perhaps memcached , sharding won't issue?

i'd know experience 2 databases on large projects, out of mysql , mongodb right tool particular job?

if data highly relational, use relational database. if it's not, don't. nosql great, don't me wrong, it's not suited tasks. may suited task, way find out build tests specific usecase. add bunch of dummy data (millions if not hundreds of millions of rows). , load test it.

as far scaling, that's more of component of how build application backend choose. have solid schema? have strong cache layer write-through caching? access backend efficiently possible (queries , such)? can shard based upon application?

those kind of questions appropriate here. not "which scale me better". , not "which right tool". both can job fine. best you...


Comments

Popular posts from this blog

apache - Add omitted ? to URLs -

redirect - bbPress Forum - rewrite to wwww.mysite prohibits login -

php - How can I stop spam on my custom forum/blog? -