5 ms·

I have a very antagonistic relationship with NoSQL databases because the vast majority of people get nothing out of using one, and yet every resource a newcomer

I have a very antagonistic relationship with NoSQL databases because the vast majority of people get nothing out of using one, and yet every resource a newcomer to programming (on the Node.js ecosystem at least) recommends using MongoDB with Mongoose (an ORM for a NoSQL database? Why?), leading them down a path they really have no business walking because they could have instead learned the widely used, time-tested traditional SQL databases.

dlvktrsh 6y ago
I've been the exact person you're talking about, do u think I should switch to postgres instead? I'm trying to build an Instagram bot that collects all sorts of user metadata and their interactions with other users maybe evern someday make a Twitter version of the saem bot and try to mine some more data
- petersellers 6y ago
  For small projects like this either one would probably be fine. Hell, you can try implementing with both just to see what you like and don't like from each.
- Kaze404 6y ago
  I don't think you'll benefit from switching either way, but in my opinion you'll benefit from learning Postgres when you have the time / start a new project.
- mercer 6y ago
  I suppose switching depends in part on how much work that would be. That said, I tend to pick Postgres as a default because using JSONB columns I can get the benefits of 'NoSQL' and switch over to 'SQL' while staying within the same database.
ZephyrBlu 6y ago
> and yet every resource a newcomer to programming (on the Node.js ecosystem at least) recommends using MongoDB with Mongoose (an ORM for a NoSQL database? Why?) It's because it's easy. Who cares about thinking? Just throw your data into Mongo and it'll work (For your toy project where nothing matters). It's sad to see that there's such a massive lack of the type of attitude described in this article: https://www.norvig.com/21-days.html https://www.norvig.com/21-days.html.
- yawnxyz 6y ago
  this is where MongoDB excels... at toy projects. It's great for designers like me to get my feet wet
- Kaze404 6y ago
  That's a great article, thank you.

dlvktrsh 6y ago

I've been the exact person you're talking about, do u think I should switch to postgres instead? I'm trying to build an Instagram bot that collects all sorts of user metadata and their interactions with other users maybe evern someday make a Twitter version of the saem bot and try to mine some more data

petersellers 6y ago
For small projects like this either one would probably be fine. Hell, you can try implementing with both just to see what you like and don't like from each.
Kaze404 6y ago
I don't think you'll benefit from switching either way, but in my opinion you'll benefit from learning Postgres when you have the time / start a new project.
mercer 6y ago
I suppose switching depends in part on how much work that would be. That said, I tend to pick Postgres as a default because using JSONB columns I can get the benefits of 'NoSQL' and switch over to 'SQL' while staying within the same database.

ZephyrBlu 6y ago

> and yet every resource a newcomer to programming (on the Node.js ecosystem at least) recommends using MongoDB with Mongoose (an ORM for a NoSQL database? Why?) It's because it's easy. Who cares about thinking? Just throw your data into Mongo and it'll work (For your toy project where nothing matters). It's sad to see that there's such a massive lack of the type of attitude described in this article: https://www.norvig.com/21-days.html https://www.norvig.com/21-days.html.

yawnxyz 6y ago
this is where MongoDB excels... at toy projects. It's great for designers like me to get my feet wet
Kaze404 6y ago
That's a great article, thank you.