Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I want to create a node.js and MySQL based application. Google and Stack Overflow give many options for Javascript ORMs:
sequelize.js
persistence.js
waterline
knex.js
node-orm2
bookshelf.js
objection.js
However, I could not find an perfect ORM that supports subqueries, joins, transitions, stored procedures, is compatible with MySQL cluster, and has good documentation and community support.
Are there other options? What considerations should I take into account in making a decision?
You should try Sequelize. It is a quite different, but still really easy to use. The best I like on it, is their auto synchonizer, which it is quite like Mongoose.
Use light-orm and mysql.
Light-orm is wrapper around any relational db and mysql is best mysql driver for node.
https://npmjs.org/package/light-orm
https://npmjs.org/package/mysql
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I will start developing my e-commerce website soon however, I don't have experience in backend. So I'm considering to use firebase. But my real concern is, , is firebase good option on long term? Is it easy to migrate to mongodb and node js or is it better to write my own backend from the beginning?
You should consider using firebase if the features are useful to you:
authentication
noSQL database
storage
in-app messaging
It is a good option long-term if don't hit the upper limits of the free plan for a long time. This is almost always the case for new unknown projects.
Because of the noSQL nature, switching to mongoDB is straight-forward. The real question is if you are already experienced with setting up and using node.js with mongoDB. You are better served with what you already know.
Use Firebase if you have no significant experience with the alternatives.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
some times ago I found a few articles that keep saying that mongoose is prevention for NoSQL attacks but know I found a different article saying that mongoose won't prevent all NoSQL attacks. Well, so I am curious if mongoose is enough prevention from NoSQL attack for node app. Thank for answer.
Mongoose is not intended to prevent NoSQL attacks. It is a MongoDB ODM that makes it easy for you, including organizing your database with schemas or query helper.
Inherently, it will help you avoid some security mistakes you might make without it, but that is not enough in itself.
First of all, you need to securize your MongoDB database and your system.
Note also that it is quite impossible to prevent "all" attacks in general.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I am just about to make a small instant messaging server.
I am thinking of using MongoDB, NodeJS, and Redis. Do you think it is a good choice?
What do you think about the model schema?
It's really a good choice. If I were you, I'd use socket.io, node.js, and mongoDB.
you can also use mongoose which is a model-based and It's much better.
MongoDB(Mongoose) is a good choice, because when you do a instant messaging application, it's a good choice (you will need ) to store data as documents.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I've been considering using node/express/sequelize for a project but I've read in a few places where people strongly advise against using sequelize as an ORM. Can someone advise me on the major reasons why people say not to use sequelize?
For clarity, I'm using postgres as a database for relational data, not no-sql
It happens to be that MySQL is not part of the opinionated MEAN Stack. There was a revolution against the strict schema types of SQL, and started a NoSQL revolution. MongoDB earned its position in the MEAN stack, and the rest is history. As far as I'm concerned, it's just an opinion. If you need strictly structured data and your backend uses MySQL, you'll be fine, don't listen to all the hype man. Remember, these are tools we are using.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
this article suggests that using MongoDB for a SAAS application that you should use one DB for each client - can this be right? http://docs.mongohq.com/use-cases/marketing-platforms.html (see bottom of page)
If so are there any occasions when it would still pay to put all clients into one DB?
I asked a similar question
Is it better to use multiple databases when you are managing independent sets of things in MongoDB?
The conclusion seems to be its not really very efficient to have multiple databases. But its still a valid way of doing things.
A more important consideration is if you want to do queries across customers for whatever reason, then your job gets a lot more difficult if they are in separate databases.