Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. 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

I am actually can not understand the real advatage or killer feature of MongoDB storage.

As I understand currently MongoDB implements exclusive per-database write lock that is even worse from the concurrency point of view than per-table write locks of MySQL's MyISAM storage engine.

Also MongoDB uses memory mapped files which are mapped to virtual memory (not physical RAM) and flush data to disk every second (without journaling). With write ahead log (journal) the data is also not durable because group commits are performed in certain time intervals. So we receive not durable and not in-memory storage at the same time. (There was a time when Redis also used swapping but they wisely removed this feature since 2.5 version)

So considering the above, what is the point of using MongoDB in production (especially highload) applications?

share|improve this question

closed as primarily opinion-based by bluefeet, dezso, Mark Storey-Smith, Max Vernon, RolandoMySQLDBA Sep 16 '13 at 15:40

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.