React, Angular, Blaze 2 < MDG in-house SQL support

[brajt]

Mongo is solving a different problem than a relational database like Postgres; one can’t merely shift a problem fit to be solved by one model into the other.

And contrary to that…

SQL on the same level as Mongo (no joins) is not hard to learn and learning SQL apart from whatever language was connecting to it is fairly standard. We don’t expect people to shy away from learning basic shell commands. SQL is similar to this.

…the world generates plenty of developers who try to solve every problem in SQL or hack relations into NoSQL databases and claim their problems are a better fit for SQL even if they’re not. So they come to Meteor and start shouting “dude, where’s my SQL” just because they feel more familiar with it.

SQL on the same level as Mongo (no joins)

NoSQL is not just SQL without joins. Sadly that’s what plenty of developers forget about.

MDG in-house SQL support

But they’re working on it already:

An early look at SQL in Meteor

One of the design decisions we made to build Meteor was initially only supporting MongoDB as the backing database. This decision has affected all parts of the stack, for example the use of Minimongo on the client. So while it was obvious that Meteor would eventually need support for other databases, as mentioned in the Meteor roadmap blog post, it was very unclear what that support would look like. We had a lot of internal design discussions and considered many approaches, but at the end of the …

If I wanted the Meteor-SQL project to get realized as fast as it can, I’d do everything to provide the feedback for the guys.