current community

your communities

more stack exchange communities

company blog
Stack Exchange Inbox Reputation and Badges
tour help
Game Development Stack Exchange is a question and answer site for professional and independent game developers. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
up vote 1 down vote favorite

I am building a one click game website/mobile app, and I am debating between using MySQL and MongoDB for the backend.

The way I have been exploring it is with a NodeJS/Express/Angular/Passport/MongoDB stack - I have also implemented Socket.io.

I have gotten to the point where I am sending data from the flash game to the server (NodeJS).

The only data that needs to be sent is basic user information, the players score at the end of each game, and some x,y positions for each players game (for anti-cheating). It seems like MySQL would work fine, but as I am already using MongoDB - are there any major drawbacks to continuing to work with MongoDB on this project?

share|improve this question

closed as off-topic by bummzack, Jari Komppa, Byte56♦ Jun 5 '14 at 13:42

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

  • "Questions about "how to get started," "what to learn next," or "which technology to use" are discussion-oriented questions which involve answers that are either based on opinion, or which are all equally valid. Those kinds of questions are outside the scope of this site. Visit our help center for more information." – bummzack, Jari Komppa, Byte56
If this question can be reworded to fit the rules in the help center, please edit the question.
2  
Hi and welcome to the site. Questions about which technology to use are considered off-topic here. Have a look at the help center and enjoy your stay here. – bummzack Jun 5 '14 at 6:30
1  
If you're using one technology already, keep using it. If you don't see a reason to change, then don't change. – Byte56♦ Jun 5 '14 at 13:42