|
|
|
|
|
|
by xmatos
3267 days ago
|
|
|
Hype and lack of critical thinking abolutely had their role, but mostly because it's so much easier than a relational db. Relational db's are hard. You have schemas and query planners and the truth is, you have to take care of every single query. Every query counts. The same query can take 30 seconds, or 30 milliseconds to run, depending on it using an index or not. You think it's ok for it to take 2 or 3 seconds, until it hits production and halts the server. Mongo doesn't have any of that. Just load and dump json back and forth, which is perfect for fast prototyping. Who cares about data integrity or technical debt? |
|
|
Mongo has query planners, the same thinking you do in SQL applies to Mongo, the edge cases are different. For example, you can't have composite indices on multiple arrays. The same principles we consider when tuning our RDB apply to Mongo, normalisation comes at different forms/levels. The same applies to denormalisation. Just because there are/were "no joins" didn't mean that everything goes into a single collection.
I run some Mongo deployments, and I take as much care in understanding performance, as I do with our SQL deployments. Databases are hard to those who are unwilling to open up the manual and read. It's not only SQL.