I am looking out for some NodeJS ORMs. I have found Loopback and Sequelize. I have tried out both of them, and found them extremely useful for the basic CRUD operations, and to some extend in custom operations also. But, in some of the cases (which are usually the main operations of the app), I usually have to find out a work around with them, and the code looks extremely crappy. So, what would you suggest, use ORMs or to write your own neat code.
Yes, ORMs don't cover all your needs and there might be something which you need, but not available in ORM. So, you better analyse before you choose one. Write down all possible scenarios/usage and see if the ORM matches with it. If it matches exactly, then go ahead. Else, just drop the idea and start from scratch. If you have enough time to implement your needed operation in that particular ORM tools, you better do it. But if not, then a big no. Stock is the way to go, rather then get stuck at some crucial time and looking for solution. BTW I use node-orm2 and it pretty much covers all my needs.
Denny Trebbin
Lead Fullstack Developer. Experimenting with bleeding-edge tech. Irregularly DJ. Hobby drone pilot. Amateur photographer.
It is not easy to answer which ORM should you used. It depends on the data model I feel.
I avoid ORMs which forcibly try to get ownership of the data model and data structure. They are only easy to use for greenfield projects, IMO. But who is still choosing databases for greenfield projects where ORMs are required to tame the query beast?
Not long time ago I used waterline.js. I've not really used but think these ORM good choices too JugglingDB and Osmos.
The ORM I love and use the most right now is Thinky (For the super cool RethinkDB). It adds only as much sugar as needed. The rest is up on my knowledge. Great!