fanout / fanout-graphql-tools Goto Github PK

To not add micro as dependency to the whole lib, this involves making an examples subpackage

• The default value for getGripChannel should include the WebSocket-Over-Http connection id

"I'm surprised apollo-demo is over 1000 lines even when tests are excluded. Can you explain to me what is going on in each file for my own learning?"

@jkarneges reported via email:
There is a bug that would manifest like so:

• create a graphql-ws subscription (through pushpin/GRIP) using N>=2 clients. Identical subscriptions (e.g. two tabs in graphiql playground)
• send a mutation that should result in a message on the subscriptions
• You expect each client to receive 1 message from the mutation, but actually they will receive N.

This is because, while they were all independent clients/subscriptions, they all end up reusing the same Grip-Channel. So we only need to publish one message via EPCP to that Grip-Channel, not N messages, one per subscription.

The number of audience who have Serverless Subscriptions issue are certain to use apollo-server-lambda. It would be better if you build an example using it or atleast some guide

I think we can do better than this, including checking new subscriptions against the graphql schema and reporting errors, now that we are making use of graphql execute function.

Putting here as a reminder, but this isn't critical.

While getGripChannel is required in, there is no specific guide to how to use in it GraphqlWsOverWebSocketOverHttpExpressMiddleware

I stumbled upon this project. It looks very interesting and I am wanting to try this out some time soon. I don't think any other project has succeeded in implementing any hosted WS into Lambda.

But my question is: is this project still being maintained and is there a roadmap? I.e. safe to use in production?