(This thread was originally a question, but after some research, the title reflects the outcome)
TLDR (more details below): Use Meteor collections and pubsub for Meteor apps for the superior developer experience and data consistency, and learn how to control their power with throttling and/or methods. Use Apollo GraphQL only for fetching from external sources, and do not rely on it for realtime data.
Is there a real advantage to using GraphQL in a Meteor app?
Development wise, and code wise, complexity seems to be about the same between stock Meteor, and the
--apollo template (if anything, we’re merely swapping mongo-style query language for GraphQL query language, and one might be slightly harder than the other).
meteor create --apollo example feels like an extra layer over Mongo. To me, it seems like it’s just easier to use the standard Mongo setup and move along.
Is there a real benefit of using GraphQL, especially the setup found in the
meteor create --apollo template?
I don’t see it as going to greatly improve my code base, so the only think I can imagine is there’s a performance reason for going to GraphQL. Is this the case?