The database you choose will depends on your project needs. If I need strict relations in my data I do not use MongoDB. In such cases, SQLite usually serves my purpose for POCs and in prod I like PostgresSQL. I love using Sequelize ORM docs.sequelizejs.com/ which supports MySQL/PostgreSQL/SQLite. For apps that involves file storage I use MongoDB.
Just a coder and a dad. I love my family and I love to code!!!! started coding at 11, so I have 25 years under my belt. Still love learning about it every day. Black lives matter!
A web developer. A guitar / bass / shamisen player. A hobby audio engineer. A world citizen who has broad tastes and passions in various languages (programming / non-programming), music and food.
It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
I'm partial to Postgres in general but the most important considerations are really your data model and other requirements, not what you're running. If your data model is hierarchical with few relationships (unusual, but it happens) MongoDB is built for that. If your project is small-scale enough that you're okay with the database living on the same filesystem and having only one active connection at a time, SQLite will do perfectly well, although if you've already got Postgres running there's no reason not to use that either.
A web developer. A guitar / bass / shamisen player. A hobby audio engineer. A world citizen who has broad tastes and passions in various languages (programming / non-programming), music and food.
MongoDB is what I'm using for almost anything if I have the power to choose. Because as a frontend developer I really don't want to spend too much time on creating subtle data model schemes for lightweight projects. But we use a lot postgres in the real production.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The database you choose will depends on your project needs. If I need strict relations in my data I do not use MongoDB. In such cases, SQLite usually serves my purpose for POCs and in prod I like PostgresSQL. I love using Sequelize ORM docs.sequelizejs.com/ which supports MySQL/PostgreSQL/SQLite. For apps that involves file storage I use MongoDB.
+1 for sequelize
+1 for Sequelize!
I'm partial to Postgres in general but the most important considerations are really your data model and other requirements, not what you're running. If your data model is hierarchical with few relationships (unusual, but it happens) MongoDB is built for that. If your project is small-scale enough that you're okay with the database living on the same filesystem and having only one active connection at a time, SQLite will do perfectly well, although if you've already got Postgres running there's no reason not to use that either.
This is such an incredibly broad question.
The choice of database should not be decided because it's someones "preferred" technology.
What's the best database for the project you're working on - that's the question you should be asking.
That's the question you should be asking of every technology you use. Is Node even the right language for the job you're trying to do?
MongoDB is what I'm using for almost anything if I have the power to choose. Because as a frontend developer I really don't want to spend too much time on creating subtle data model schemes for lightweight projects. But we use a lot postgres in the real production.