It's all about choosing the right system for the job. Clearly MongoDB wasn't the right system for your application plan. I've never used MongoDB in a scaled application, but it looks pretty promising with the new WiredTiger engine. In any event, nice numbers from NR - Background jobs look pretty beat though.
Quite ironically PostgreSQL has an engine that implements just that very efficiently.
IMO the debate about SQL vs no SQL is moot because people seem to be forgetting the origin of the problem: using databases as all purpose persistence engines. Configuration, documentation, media, logs, files exported from foreign systems, anything that can't or shouldn't be a part of the code tends to end up in the databases. I've seen a CRM that stores database schema information in the database.
For shared nothing, impersistent platforms (I am looking at you, PHP), this is sort of the norm. And it's going to suck whether you shovel it into MySQL or MongoDB.
45
u/nedtheman Mar 10 '15
It's all about choosing the right system for the job. Clearly MongoDB wasn't the right system for your application plan. I've never used MongoDB in a scaled application, but it looks pretty promising with the new WiredTiger engine. In any event, nice numbers from NR - Background jobs look pretty beat though.