GraphQL Subscriptions Are Stateful; We Made Them Stateless - Matteo Collina, Platformatic

GraphQL Subscriptions over WebSockets is an extremely popular way to notify the caller that something happened on the back end. While a high level of Quality of Service is possible in other protocols such as STOMP or MQTT, there is no actual guarantee of delivery with GraphQL Subscriptions: any acknowledgment mechanism should be built in userland.

WebSockets can be interrupted at any time with both graceful and ungraceful disconnections, and the lack of acknowledgment in the subscription protocol affects reliability, making GraphQL Subscription over WebSocket connections susceptible to disconnections, as any protocol failures will result in messages being lost. In other words, Subscriptions are stateful. In this talk, we will investigate a mitigation technique to make them resumable so that the connection can be destroyed and recreated without any message loss.

-------
About GraphQL Foundation
The GraphQL Foundation is a neutral foundation founded by global technology and application development companies. The GraphQL Foundation encourages contributions, stewardship, and a shared investment from a broad group in vendor-neutral events, documentation, tools, and support for GraphQL. Read more at https://graphql.org/community/foundation/

-------
Get More GraphQL
📥 Subscribe for more talks & presentations: @GraphQLFoundationTalks
▶️ Watch the Working Group Meetings: @GraphQLFoundation
✅ Join our Discord: https://discord.graphql.org/
🛠 Contribute on GitHub: https://github.com/graphql
🛼 Follow us on X: https://x.com/graphql
👩‍💼 Follow us on LinkedIn: https://www.linkedin.com/company/graphql-foundation

Видео GraphQL Subscriptions Are Stateful; We Made Them Stateless - Matteo Collina, Platformatic канала GraphQL TV