A weekly newsletter of the best news, articles and projects about GraphQL

Introducing a powerful, unique capability in the GraphQL ecosystem — native support for grouped and summarized queries using aggregations directly from your GraphQL API in Microsoft Fabric.

Over the past decade, we’ve seen an explosion in API-first development. REST laid the groundwork: predictable URLs, standard verbs, stateless calls. It was simple, understandable, and worked well…until it didn’t. Today’s applications demand something more. More composability. More flexibility. More precision. REST can’t keep up. That’s why GraphQL is taking over. This isn’t about hype or syntax preference. It’s about the realities of building and scaling modern software.

GraphQL offers unique capabilities for agents to access APIs through Model Context Protocol (MCP). With its strict specification, it's easy to discover and execute arbitrary requests to an API. The clear distinction between queries and mutations also makes it less risky for users to let the agent try queries without worrying about potential side-effects. Existing GraphQL MCP servers suffer from the same fundamental problem: the more capabilities you want to provide to the agent, the bigger its context needs to be. Providing the schema makes it proportional to your API size and specifying possible operations explicitly obviously scale with their number in some form. At Grafbase, we came up with a different approach to enable agents to explore an API without prohibitive context sizes.

We're excited to announce support for PostgreSQL in Grafbase Extensions, bringing even more power, flexibility, and scalability to federated GraphQL APIs. With this launch, you can now declaratively integrate Postgres databases directly into your federated GraphQL API. That means no subgraph infrastructure, no manual stitching, and no extra services required. It's all managed natively within the Grafbase platform.

Booking.com was handling 8 billion API requests per day but their system was falling apart. One architectural change reduced latency from 200ms to 10ms and increased product delivery speed by 40%.