What do you expect from such an integration?
- Full stack support like live queries and subscriptions connected to your Mongo database? Like adding a Collection will also add mutations for it. Like Meteor generates methods for you. But most people advice to create your own methods, instead of trusting allow/deny.
- Integration with Tracker or Blaze? There is already
- Automatically load data into MiniMongo? You could do this with a custom Apollo cache implementation, but if you’re using GraphQL you won’t need MiniMongo.
It’s already very easy to get started by using the
apollo or the
swydo:ddp-apollo package. But it’s just GraphQL in the end.
I’m asking this because I’m interested in creating such a tighter integration, but I’m wondering what the expectations are. If the only thing is: it should work like the current Meteor, but with a schema, than use the current Meteor with simple schema.
Why do you want to use Apollo? What does it solve that current Meteor doesn’t? And what does the current Meteor solve that isn’t available in the current integrations?
@yellowspaceboots, could you also elaborate on what you expect from a tighter integration?
Have a look at ddp-apollo and let me know if this comes closer to the integration you’re expecting: