Hi,
at some recent Meteor podcast was mention about Meteor 3 noSQL and SQL database abstraction, so it would be possible to use reactivity with different noSQL and SQL databases. Where is related discussions and code? URLs ?
2 Likes
They’re really different models. Meteor reactivity is really powered by having minimongo on the client, which works as a client side replica set that the mongo cursor can synchronize with. We’ve tried to create minisql on the client, and that was sort of a dead end. Much easier to simply flatten SQL into a Mongo cursor after your JOIN query, and synchronize across DDP like usual. It’s easiest to just treat Meteor as a content distribution network layer,
I don’t remember if I’ve mentioned this before, but today Meteor’s reactivity is based on MongoDB (using either polling or oplog). I’m working on two new ObserverDrivers: one using change streams (still Mongo-dependent) and another based on EventEmitter, which will remove the MongoDB dependency on the server side. Once that’s in place, we’ll be able to focus on the client side (Minimongo).
So, we don’t support non-NoSQL databases yet, but we’re moving in that direction.
2 Likes