5 ms·

Mongo is quick and dirty. If you're writing NodeJS, chances are you don't care about `what's best`.

virmundi 9y ago
You can do that with Arango. Equally quick. Equally dirty. Doesn't require a prod version with 3 nodes just to make sure, hand to God, no data is lost.
- krisdol 9y ago
  I've literally never heard of Arango before reading these comments. That might have something to do with people not using it.
  - don71 9y ago
    Or maybe it's related to fact that it's pretty young.
  - virmundi 9y ago
    It probably has to do with being German. The US produces alot of tech that the rest of the world knows, due to PR. Germany. Well, they move quietly. Then BAM! ArangoDB in Poland!
bsg75 9y ago
So are you implying Node developers are fine with half-assed solutions? They might disagree.
- brokenpromise 9y ago
  They might disagree, but that doesn't mean they're right.
rawnlq 9y ago
For fast prototyping, it's pretty hard to beat a NodeJS stack. A lot of modern web dev are one-man-shows. When you're just one developer doing frontend and backend, you don't really have time to care about database migrations or designing schemas. You really just want to duct tape enough pieces together to get your app out the door. Caring about schema design, database migration, or even code correctness doesn't really help with this. Mongo in comparison has no learning curve, crazy number of pre-integrated libraries, and works well enough at low scale. This might sound like cancer to corporate devs but the tradeoff does make sense for individuals/demos/startups. A illustrative case study: https://medium.com/unboxd/how-i-built-an-app-with-500-000-users-in-5-days-on-a-100-server-77deeb238e83 https://medium.com/unboxd/how-i-built-an-app-with-500-000-us...
- nikcub 9y ago
  I've always suspected that MongoDB is largely driven by nodejs - i'd be curious what portion of Mongo connections are nodejs There is no real good nodejs RDBMS ORM in the class of what other environments provide. I recently had a company rip out nodejs => sequelize => pgsql and replace it with nodejs => protobufs => sqlalchemy => pgsql
- sanderjd 9y ago
  Even for fast prototyping, I feel like I end up spending more time dealing with data validity issues as the "schema" in my code falls out of sync with what's actually in the database than I would have by laying out a simple schema for my database to enforce. I think this is a YMMV situation.

You can do that with Arango. Equally quick. Equally dirty. Doesn't require a prod version with 3 nodes just to make sure, hand to God, no data is lost.

krisdol 9y ago
I've literally never heard of Arango before reading these comments. That might have something to do with people not using it.
- don71 9y ago
  Or maybe it's related to fact that it's pretty young.
- virmundi 9y ago
  It probably has to do with being German. The US produces alot of tech that the rest of the world knows, due to PR. Germany. Well, they move quietly. Then BAM! ArangoDB in Poland!

bsg75 9y ago

So are you implying Node developers are fine with half-assed solutions? They might disagree.

brokenpromise 9y ago
They might disagree, but that doesn't mean they're right.

rawnlq 9y ago

For fast prototyping, it's pretty hard to beat a NodeJS stack. A lot of modern web dev are one-man-shows. When you're just one developer doing frontend and backend, you don't really have time to care about database migrations or designing schemas. You really just want to duct tape enough pieces together to get your app out the door. Caring about schema design, database migration, or even code correctness doesn't really help with this. Mongo in comparison has no learning curve, crazy number of pre-integrated libraries, and works well enough at low scale. This might sound like cancer to corporate devs but the tradeoff does make sense for individuals/demos/startups. A illustrative case study: https://medium.com/unboxd/how-i-built-an-app-with-500-000-users-in-5-days-on-a-100-server-77deeb238e83 https://medium.com/unboxd/how-i-built-an-app-with-500-000-us...

nikcub 9y ago
I've always suspected that MongoDB is largely driven by nodejs - i'd be curious what portion of Mongo connections are nodejs There is no real good nodejs RDBMS ORM in the class of what other environments provide. I recently had a company rip out nodejs => sequelize => pgsql and replace it with nodejs => protobufs => sqlalchemy => pgsql
sanderjd 9y ago
Even for fast prototyping, I feel like I end up spending more time dealing with data validity issues as the "schema" in my code falls out of sync with what's actually in the database than I would have by laying out a simple schema for my database to enforce. I think this is a YMMV situation.