9 ms·
I used bookshelves a couple years ago and while it was very good on paper, I quickly ran into a lot of quirks and bugs for advanced usage. There was an obvious
by ht85 10y ago
I used bookshelves a couple years ago and while it was very good on paper, I quickly ran into a lot of quirks and bugs for advanced usage.
There was an obvious lack of resources to develop it, and after contributing to it a bit I switched. Reliability is the #1 feature in an ORM in my opinion, and I didn't get that confidence from using bookshelves.
I later moved to sequelize, and it worked flawlessly from the get go, give it a try. You can compare the Github activity, you'll see it's thriving, and everything is much cleaner.
The performance is also way ahead, as last time I used it bookshelves relied on Backbone-esque models underneath, making it way slower for big nested queries.
- olalonde 10y agoThanks. I actually started out with Sequelize before switching to Bookshelf.js but you convinced me to give it another go.
- gaastonsr 10y agoNoo, give it a go Bookshelf.js you will be more happy. Yes, maintenance lacks behind sometimes but the core is strong. And if you do anything particularly hard you always can tap into knex and get all its powerful API and if that is not enough you run raw queries until the feature is officially supported.