You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there!
You seem to have a solid handle on writing MongoDB extensions, so I have a question for you:
Over in Meteor land, we've been using a library called minimongo, which lets us have an isomorphic Mongo API on the server, client, database, and db shell. Well, the Meteor Development Group has started a new project called Apollo, which is GraphQL focused, and where all their future development is heading. So far, they've got GraphQL working on both the server and client, and various folks are writing GraphQL device drivers for their respective databases.
The point of introducing GraphQL was to abstract away from Mongo, so the Meteor stack could use lots of different databases.... SQL, Oracle, Redis, BigTable, Cassandra, etc.
So, okay... Meteor is evolving and not going to be quite so Mongo focused in the future. Not the end of the world, but we'd like to maintain both Mongo compatibility and the existing isomorphic API. The folks over at Compose.io have figured out how to query a Mongo database using GraphQL. So that gives us server, client, and database.
But not quite. We're missing GraphQL queries in the mongo shell (and various utilities like Robomongo, but that's another discussion entirely). So the question is: how difficult would it be to write a graphql extension for the mongo shell?
Any thoughts on this or where to begin?
The text was updated successfully, but these errors were encountered:
Hi there!
You seem to have a solid handle on writing MongoDB extensions, so I have a question for you:
Over in Meteor land, we've been using a library called
minimongo
, which lets us have an isomorphic Mongo API on the server, client, database, and db shell. Well, the Meteor Development Group has started a new project called Apollo, which is GraphQL focused, and where all their future development is heading. So far, they've got GraphQL working on both the server and client, and various folks are writing GraphQL device drivers for their respective databases.The point of introducing GraphQL was to abstract away from Mongo, so the Meteor stack could use lots of different databases.... SQL, Oracle, Redis, BigTable, Cassandra, etc.
So, okay... Meteor is evolving and not going to be quite so Mongo focused in the future. Not the end of the world, but we'd like to maintain both Mongo compatibility and the existing isomorphic API. The folks over at Compose.io have figured out how to query a Mongo database using GraphQL. So that gives us server, client, and database.
https://www.compose.com/articles/using-graphql-with-mongodb/
But not quite. We're missing GraphQL queries in the mongo shell (and various utilities like Robomongo, but that's another discussion entirely). So the question is: how difficult would it be to write a graphql extension for the mongo shell?
Any thoughts on this or where to begin?
The text was updated successfully, but these errors were encountered: