
Benjamin Rabier
Grafbase, Software Engineer
Living close to Paris, I've been at Grafbase for over two years building the GraphQL federation gateway among other things.
In this workshop, we will look at different patterns to integrate various data sources in a federated graph using the Apollo Federation V2 spec, the Composite Schemas spec, WebAssembly with the recently released Component Model, and the Grafbase Gateway. GraphQL Federation is a fantastic pattern to combine APIs — called subgraphs — into a single schema while sharing types and declaratively depending from data from other subgraphs. In fact, it is too good to keep it to GraphQL subgraphs only — what if you could bring other kinds of APIs and data sources into your federated graph without having to write a dedicated GraphQL server in front of them? In the course of the hands-on workshop, we will: Integrate a REST API, a Postgres database and a Kafka instance using open source extensions, Use the gRPC extension and the MCP server to understand, integrate and query gRPC services over GraphQL, Build a new custom extension together The result will be a functioning GraphQL federated graph without GraphQL subgraphs, demonstrating that federation as a mechanism is useful beyond just GraphQL subgraphs.
Grafbase, Software Engineer
Living close to Paris, I've been at Grafbase for over two years building the GraphQL federation gateway among other things.
Grafbase, Engineer
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!