GraphQL Day@ FOST Melbourne

Feddi gateway is the first open source implementation of the community driven GraphQL spec. This talk will introduce feddi gateway.

Coding agents are reshaping how we build software. Implementing features, refactoring systems, and shipping changes at a pace unthinkable 6 months ago. But to be successful with agents you need the right feedback loop. One that guides your agent to success, not into the spiral of death. Read more…

REST APIs were designed for human-built clients that know exactly what URL to call. AI agents are different — they reason, plan, and decide what data they need at runtime. That mismatch is quietly becoming one of the biggest friction points in enterprise AI adoption. Read more…

Building a graph requires real up-front investment - designing schemas, deploying new infrastructure, and onboarding teams onto unfamiliar platforms costs precious time and energy. So why bother? Read more…

GraphQL makes APIs remarkably flexible: clients can ask for exactly the data they need, compose resources through a single endpoint, and evolve schemas without constantly introducing new URLs. But that flexibility changes the security and governance problem. Read more…

You can hand your GraphQL work to an AI agent today, but it tends to make the same mistakes developers have made for years: schemas that are nullable everywhere, anonymous queries, and code that ignores partial errors. Most of the time the model isn't the problem. It just doesn't know your API or your team's conventions, so it guesses. Read more…

Most of us know GraphQL as the "Experience Graph", shaped around screens and clients. But GraphQL can be used elsewhere in your architecture: as a Data Graph, a strongly-typed abstraction directly over your data layer, giving every consumer - services and AI agents alike - a single place to access all your data. Read more…