Changing a field from "one" to "many" sounds trivial until three different consumers depend on it: an admin studio, a GraphQL API used by web and mobile apps, and a public API used by customers' own integrations.

This talk walks through a real migration on an event technology platform, where a single-value relationship became a multi-value, ordered one. We will cover how we designed the new schema alongside the old one, how we kept existing queries working, how we backfilled data safely, and how we decided when a deprecated field could finally go.

This ad-hoc talk is just Benjie (and any other TSC present) riffing about some of the work that's going on in the GraphQL Working Groups currently. Topics covered include:

Vi på Sikt skriver skjemaet vårt først for deretter å koble dette opp mot våre datakilder. Dette er ganske enkelt og smertefritt, men hva gjør du når det dukker opp verbose mønster som GraphQL SDL ikke lar oss generalisere?

Kom og hør hvordan vi har løst dette ved hjelp av det jeg liker å kalle SDL-makroer eller schema transforms.

GraphQL celebrated it's 10 year birthday last year, today it's PostGraphile's turn! Hear from maintainer Benjie about the origins of the project, the lessons learned along the way, and how the project has evolved to meet the needs of its users despite being MIT-licensed OSS.

We built a real-time system for Postgres→React sync using a `LISTEN/NOTIFY` Postgres trigger, GraphQL `@live` queries, a React hook and a custom ORM-inspired GraphQL query builder. Starting from ESP32 microcontroller devices sending MQTT messages and a Node/Postgres backend, we moved from polling to a stand-alone PoC with Yoga, Prisma triggers, and a custom `useLiveQuery` hook. After proving that the PoC was working we integrated with all our existing full-stack apps. So now we have low-latency UI updates, reusable cross-app logic, and easier extension for new sensor values. Great UX and excellent DX.