Rdb – a Node.js ORM with transactions, persistence ignorance and promises
1–10 of 47 posts
Re: Rdb – a Node.js ORM with transactions, persistence ignorance and promises
#2Seems interesting ! I would definitely like more ORM for node.js technologies.
The concurrent are Sequelize (http://sequelizejs.com/) and Bookshelf (http://bookshelfjs.org/), both very mature libraries (look at the Sequelize test suite, it's quite impressing !). Iroal, any comment on the rdb choices against these two big guys ? How can we expect rdb to evolve ?
Re: Rdb – a Node.js ORM with transactions, persistence ignorance and promises
#3Not sure I see the advantage over waterline (https://www.npmjs.com/package/waterline) ?
Re: Rdb – a Node.js ORM with transactions, persistence ignorance and promises
#4Seems interesting ! I would definitely like more ORM for node.js technologies. The concurrent are Sequelize ( http://sequelizejs.com/ ) and Bookshelf ( http://bookshelfjs.org/ ), both very mature libraries (look at the Sequelize test suite, it's quite impressing !). Iroal, any comment on the rdb choices against these two big guys ? How can we expect rdb to evolve ?
And if you just want a flexible ORM without models, knex (http://knexjs.org/), which bookshelf uses.
I found knex + Postgres to be a great combination.
Re: Rdb – a Node.js ORM with transactions, persistence ignorance and promises
#5Seems interesting ! I would definitely like more ORM for node.js technologies. The concurrent are Sequelize ( http://sequelizejs.com/ ) and Bookshelf ( http://bookshelfjs.org/ ), both very mature libraries (look at the Sequelize test suite, it's quite impressing !). Iroal, any comment on the rdb choices against these two big guys ? How can we expect rdb to evolve ?
And if you just want a flexible ORM without models, knex ( http://knexjs.org/ ), which bookshelf uses. I found knex + Postgres to be a great combination.
Likely also better performance with just using Knex.
Any ORM likely adds overhead, Sequelize definitely does, although we keep working on reducing that overhead - But inevitably features === overhead.
Re: Rdb – a Node.js ORM with transactions, persistence ignorance and promises
#6Seems interesting ! I would definitely like more ORM for node.js technologies. The concurrent are Sequelize ( http://sequelizejs.com/ ) and Bookshelf ( http://bookshelfjs.org/ ), both very mature libraries (look at the Sequelize test suite, it's quite impressing !). Iroal, any comment on the rdb choices against these two big guys ? How can we expect rdb to evolve ?
Neither Sequelize nor Bookshelf has persistence ignorance as far as i know.
Re: Rdb – a Node.js ORM with transactions, persistence ignorance and promises
#7Seems interesting ! I would definitely like more ORM for node.js technologies. The concurrent are Sequelize ( http://sequelizejs.com/ ) and Bookshelf ( http://bookshelfjs.org/ ), both very mature libraries (look at the Sequelize test suite, it's quite impressing !). Iroal, any comment on the rdb choices against these two big guys ? How can we expect rdb to evolve ?
Neither Sequelize nor Bookshelf has persistence ignorance as far as i know.
Ok, after a lookup, "persistence ignorance" is the ability to have implicit save of the models when things change.
Bookshelf has events, which make very easy to wire some kind of persistence ignorance (we implement it in our base Model class).
Re: Rdb – a Node.js ORM with transactions, persistence ignorance and promises
#8Is anyone working on auto-generated migrations in node.js ala. Django / South?
Re: Rdb – a Node.js ORM with transactions, persistence ignorance and promises
#9ORMs are not really required in a Node/Mongo/JSON setup anymore:
- JSON's nature is already very 'object oriented' and I use in code JSON data like it saved—no translation beetween clunky SQL and objects is necessary (if I have a DB which saves JSON natively like Mongo)
- Mongo allows to directly save JSON and stuff like migrations is stuff from the past since tables/collections don't have to be created
- Mongo's Native Driver is low level and at the same time fully sufficient, the syntax is not beautiful and tons of libs sit on top to make it beautiful but I still don't see the need for a real ORM
So, Mongo's Native Driver is your best friend and validations are often a matter of a few lines. Or did I miss anything which is life saving I get from ORMs in a Node/Mongo setup?
Re: Rdb – a Node.js ORM with transactions, persistence ignorance and promises
#10ORMs are not really required in a Node/Mongo/JSON setup anymore: - JSON's nature is already very 'object oriented' and I use in code JSON data like it saved—no translation beetween clunky SQL and objects is necessary (if I have a DB which saves JSON natively like Mongo) - Mongo allows to directly save JSON and stuff like migrations is stuff from the past since tables/collections don't have to be created - Mongo's Nat…
Not everyone is only using Mongo with Node