“MongoDB is dead. Long live Postgresql”
Seriously, another case of using Mongo incorrectly? I want to believe all the Mongo hate, but I can't because I always find out that the actual problem was one or more of:<p>* didn't read the manual<p>* poor schema<p>* didn't maintain the database (compactions, etc.)<p>In this case, they hit several:<p>" Its volume on disk is growing 3-4 times faster than the real volume of data it store;"<p>They should be doing compactions and are not. Using PostgreSQL does not avoid administration; it simply changes the administration to be done.<p>"it eats up all the memory without the possibility to limit this"<p>That's the idea -- that memory isn't actually used though; it's just memory mapping the file. It will swap out for something else that needs the space unless you are actively using all the data, in which case you really are using all your memory. Which is why you should put it on its own server...<p>"it begins to slow down the application because of frequent disk access"<p>"Finally we sleep quietly, and don’t fear that mongodb will drive out redis to swap once again."<p>You should be running Mongo on a server by itself. At the very least, if you're having disk contention issues, don't run it on the same server as your other database.<p>I'm not sure you always need to read the manual for everything, but for your production database, it's probably worth it.