How would one use Meteor.js without MongoDB though? Are you saying not to use Meteor.js too? I was thinking about maybe toying with the idea of making a fully reactive RethinkDB package for Meteor.js.
In fact it's the reason I'm not using Meteor, which is a shame because it looks really good. The optimistic UI feature is something I really want, and have had to implement my own custom solution for. I've nothing against Mongo per se, I just need a relational database.
Since most apps are likely better suited to using a relational database, I'm curious as to Meteor's original decision to go with Mongo. Would love to know their rationale behind that choice if anyone can enlighten me / point me towards any articles?
Meteor.js is a fantastic development system (if you can live with needing sticky sessions and you need its features).
The package is really just a simple wrapper around an npm library.
Because meteor is node-based any db that node has libraries for can be "used" .... at the expense of giving up on most meteor features.
Take it up with the Meteor.com people.
[0] - http://info.meteor.com/blog/whats-coming-in-meteor-12-and-be... [1] - https://news.ycombinator.com/item?id=9811583
However, I believe there's a few existing options for using postgres - https://github.com/numtel/meteor-pg