4 ms·
I have to absolutely disagree with the point you're making about mongodb never being something an experienced developers should use. An experience developer un
by zjaffee 8y ago
I have to absolutely disagree with the point you're making about mongodb never being something an experienced developers should use.
An experience developer understands when the goal is to deliver something as fast as possible vs building something more resilient.
If you're building an internal tool, particularly one that won't be storing data that would later be used for analytics, there's absolutely no reason to not go with mongodb over a relational database considering you can get hosted versions of both for the same price. For a less than a week long project, you could be saving at least 20% of the time spent not having to worry about a datamodel.
- matthewmacleod 8y agoYou could be saving at least 20% of the time spent not having to worry about a datamodel. You are not "not worrying about a datamodel" – you are just ignoring the data model that exists. And that overhead, if it exists at all, is far less than "20%".
- tracker1 8y agos/datamodel/data-mapping/