Subscriptions in flask-graphql

[willdeuschle]

Is there any plan to implement this / are you accepting pull requests?

[syrusakbary]

Hi @willdeuschle, graphql-core and graphene are waiting on the Subscriptions RFC in GraphQL (graphql/graphql-spec#267) to be defined and standardized from the community.

Once that is done, we will start the work :)

[kavink]

@syrusakbary @willdeuschle Looks like graphql-core/graphene has subscriptions support ? Is there an example to refer of an flask app using subscriptions?

[paunovic]

Bump. Is there a working example on how to implement subscriptions in Flask-GraphQL? I've tried some things with Gevents but nothing worked.

[rshk]

I'm using subscriptions via graphql-ws. See example: https://github.com/rshk/yawc/

Messages are forwarded to subscriptions via a Redis PUB/SUB (this allows scaling to >1 app/websocket server).

HOWEVER, I'm still having some trouble figuring out how to properly deal with those RxPy Observable objects. As it is right now it works BUT it will create a new Redis connection / subscription for every new GraphQL subscription, and it will never close them, even when the websocket is closed on the client side.

I'm assuming there's some way the Observer can signal to the Observable when to stop, but I haven't find how it's supposed to work yet. This assuming things are done properly in graphql-ws, i.e. it's not missing some call that's supposed to signal to the observer when to stop.

What I would like to do btw is to actually have one redis subscription per process, and just dispatch the messages internally to all the subscriptions that are currently listening. This to reduce the amount of unnecessary traffic (and as a bonus make it work on the free heroku-redis plan).

Any suggestions are welcome, maybe the graphql-ws authors have some hints about how to make this work?

[rshk]

Looks like this does the trick: rshk/yawc@95d6e50

(It will basically make all subscriptions listen from the same Observable, so it definitely stops countless Redis connections from being created / never disposed of).

[dtamez]

@syrusakbary Since the spec has been updated (graphql/graphql-spec#267) has work begun on adding support for subscriptions in flask-graphql?

[babaMar]

@syrusakbary Since the spec has been updated (graphql/graphql-spec#267) has work begun on adding support for subscriptions in flask-graphql?

doesn't seem so

[adiberk]

Any updates on this? How have people gone about adding subscription support with graphene3 and flask?