What's wrong with MongoDB?

K

kliss2011-09-09 15:09:10

MongoDB

kliss, 2011-09-09 15:09:10

The question arose here: why not use MongoDB in production on loaded systems?

This refers to a cluster setup, with replica sets and so on.

Reply

Answer the question

In order to leave comments, you need to log in

5 answer(s)

V

VBart, 2011-09-09
@VBart

Why not? Worth it, it was designed for this. =)
And if the data storage model does not suit you, then alas.

A

Anatoly, 2011-09-09
@taliban

It has one drawback (and an advantage at the same time, at least it used to be the main drawback) it stores a lot of things in memory, and if the memory runs out, it will silently simply not write anything there (this mainly applies to keys), on the other hand if there is a lot of memory, then it works fast =)

V

Vlad Zhivotnev, 2011-09-09
@inkvizitor68sl

Hm. Costs. And even very much. If production is understood as a set of dedicated servers, and not one piece of iron in someone else's DC.

S

sajgak, 2011-09-09
@sajgak

The disadvantage is not so much that it uses memory (which is logical), but that it cannot be given limits on its use. If it ends - rarely selected collections will be forced out, everything is clear here, but if you want to run something else on a server loaded with a large mongo database - you will hardly succeed

V

Vladimir Chernyshev, 2011-09-09
@VolCh

For mongo, you need to allocate separate servers. If something else is spinning on them, then this something may at one fine moment not have enough memory that mongo will take. Services that only take memory at startup and no longer ask for it may well live on the same server, you just need to make sure that a lot is started last.