Open ujwal-setlur opened 6 years ago
@ujwal-setlur why isn't it recommended for production ? what is recommended ?
In theory we could abstract it as a driver and allow different hookings into it, but help me get more context around this subject.
@theodorDiaconu, from the graphql-subscription docs at https://github.com/apollographql/graphql-subscriptions/blob/master/README.md:
Note that the default PubSub implementation is intended for demo purposes. It only works if you have a single instance of your server and doesn't scale beyond a couple of connections. For production usage you'll want to use one of the PubSub implementations backed by an external store. (e.g. Redis)
@ujwal-setlur it's no problem actually, because I'm essentially bridging it with observeChanges, so imagine that it becomes an observeChanges
asyncIterator.
Excellent! Just wanted to make sure. Thanks!
@theodorDiaconu, have you ever considered using rawCollection().watch
instead of depending on Meteor specific internals? I'm curious about the pros/cons, as it does sound interesting to decouple a bit from the Meteor Mongo driver.
@smeijer I did consider but there were many hoops to jump especially as this was a PoC that this is possible and not very complex to do with Meteor.
I noticed that this package uses the default PuBSub which I believe is not recommended for production. Is there a facility to specify a different PubSub, or is this handled somewhere else in the cult-of-coders/apollo package?