3 ms·
From my experience building and deploying production systems with mongodb the primary benefit is not needing a migration or ORM framework. - Deployments get mu
by patsplat 10y ago
From my experience building and deploying production systems with mongodb the primary benefit is not needing a migration or ORM framework.
- Deployments get much simpler when migrations for additive changes are unnecessary. Hundreds of deployments a week!
- JSON queries easy to pass around and decorate in application code. Hydration from a dictionary is straightforward. Combined, an ORM isn't really necessary.
- mrweasel 10y ago>primary benefit is not needing a migration or ORM framework You don't need an ORM, but they are handy. I'm pretty sure it wouldn't be an issue to load rows from a RDBMS, using a language like Python, as a dictionary, and just decorate the snot out of that dictionary, to make it look like an object. Anyway, regarding migrations, I sort of agree. Migrations can be terrifying and slow things, but at least you're allow to make certain assumptions about your data afterwards. Assumptions like "this field will always be there". With MongoDB, and any other NoSQL database I've used, you need to handle your "migrations" in the application code. So now you have block of code that checks if a given attribute exists in your JSON document. It's not necessarily a problem, but it is something you need to consider. Personally I much prefer RDBMS, because I actually like SQL and the ability to make ad hoc queries easily. If JavaScript is advertised as the query language for a database I'm not terribly interested, unless the pay off is extremely high.