Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

MongoDB is this great database I hear about. I'd like to evaluate its performance in typical scenarios relatively to traditional MySQL or SQL Server backends.

Assuming I would like to store data about employees in many company divisions:

In MySQL we would store a table containing divisions, and another containing employees and then link them.

In MongoDB, if we used a design where we have a document for each division containing employees within it, how would this scale with many employees? Is this an efficient structure for a database? Does MongoDB offer benefits performance-wise (I love that we can store bits of data without a traditional column)?

share|improve this question

closed as not a real question by Sven, Martijn Heemels, gWaldo, Shane Madden, Ward Feb 27 '12 at 6:47

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Mongodb is free, so just install it and test it in your scenario. – Sven Feb 26 '12 at 13:47
This is well covered in their documentation. They are very specific about answering pretty much these questions. You spent more effort writing this than it would have reading their intro pages. – gWaldo Feb 26 '12 at 14:42
up vote 1 down vote accepted

take a look at some real world deployments - this can give you some idea.

random links:

share|improve this answer

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