Subscriptions are not like queries and mutations. They require specific thinking and care in any implementation strategy. Federation adds a layer of infrastructure that can complicate subscriptions in two ways: - scaling, because the federation gateway may have to resolve many subscription streams at the same time, - translation, because each subgraph has the protocols it supports, and they may not overlap with the protocol used by the clients. This lightning talk dives into the challenges of translation we encountered in concrete scenarios: - How websocket init payloads map, or not, to http headers - How to translate SSE requests to websocket requests - Alternatives like multipart streams - Websocket subprotocols
Engineer, Grafbase
Tom's professional life has gravitated towards GraphQL and Rust, schemas and databases. After authoring the first Rust GraphQL client library, recent years have taken him from the database schema management space at Prisma to GraphQL federation at Grafbase. In his free time, he enjoys long walks, pistachios and trying to teach his dog the international phonetic alphabet.
Join three transformative days of expert insights and innovation to shape the next decade of APIs!