Tell me more ×
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.
up vote -1 down vote favorite

We are in the initial phases of developing one social networking project and off course have a tough time deciding between Node.js/mongoDb or PHP/Mysql for our backend.

I have read a tons about the advantages/disadvantages of both of them. But i am still unsure of what to use. I am a bit inclined towards node.js combination.

here are my requirements...

The web application would be a highly dynamic with real time responses with lot of writing/reading databases (small chunk of data every time). Its like any other social network like twitter/facebook/quora where user can post comments, likes, follow and typical features of such kind of sites.

Also, as such we don't have high calculation part in backend. What we have is one time page rendering by fetching the content of database and rendering to user and then doing real time activities.

I have learned that Node.js is event driven so seems to be a better fit for that. Also we don't have as such high processing driven modules in backend. Can you please guide me if this would be a good combination for such types of websites. Please excuse me for my english or if i posted it at wrong place.

Thank you

share|improve this question
add comment

closed as off-topic by hexacyanide, FractalizeR, Sammaye, Chris Kempen, Kami Oct 14 at 10:31

This question appears to be off-topic. The users who voted to close gave these specific reasons:

  • "Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it." – hexacyanide, FractalizeR, Sammaye, Chris Kempen, Kami
If this question can be reworded to fit the rules in the help center, please edit the question.

1 Answer

up vote 2 down vote

From my point ov view

**highly dynamic with real time responses**

and

**one time page rendering**

point you in the direction of NodeJS for the webserver

Regarding Mongo vs MySQL it is all abount what you need in terms of speed vs integrity, but, for lots and lots of small chunks of data I'd use Mongo.

share|improve this answer
 
That is a very subjective view of things and isn't backed up with any factual information, aka this isn't really an answer –  Sammaye Oct 14 at 10:13
 
He asked for guidance not solution. I believe that expressing the top reasons for myself to choose one option over another fits the request. –  Udan Oct 15 at 9:11
 
Hmm your reasoning is very base and both of them apply to PHP as well and your answer lacks any real substance, however SO isn't about this kind of stuff if you read the FAQ, you posted your own opinion in the wrong place if I am frank. –  Sammaye Oct 15 at 9:31
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.