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

Expert architects reveal 10 critical AI architecture rules: avoid model lock-in, establish governance first - plus why GraphQL is the ideal AI orchestration layer.

Curious how PlayStation supercharged their digital store? Dive into their GraphQL journey: unified APIs, slick performance, and a wishlist that wows. Peek behind the curtain of PS5’s slick experience!

APIs are evolving at warp speed in 2025! AI’s reshaping everything—design, security, even why APIs exist.

Apollo just dropped their MCP Server and suddenly AI agents can talk to your APIs without breaking everything. GraphQL meets ChatGPT, governance actually works, and developers might sleep better tonight.

Apollo's MCP Server just made AI agents and enterprise APIs best friends. GraphQL orchestration meets ChatGPT, governance doesn't break, and your legacy REST APIs can finally join the AI party without a complete rewrite.

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.\nToday’s applications demand something more. More composability. More flexibility. More precision. REST can’t keep up. That’s why GraphQL is taking over.\nThis 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. \n\nExisting 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. \n\nAt 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.\nWith 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%.

Challenges in simulating (mocking) GraphQL APIs, and an explanation of how we implemented our solution.

Why write custom AI integrations when you can transform GraphQL operations into Claude-ready tools automatically?

Apollo's CEO explains why direct API-to-AI connections break at scale—and how GraphQL solves the orchestration problem.

Shoppers expect fast, seamless experiences—whether on a desktop web app, mobile phone, or smart fridge.\nGraphQL aligns perfectly with these needs.

Build a GraphQL server in 2025 using a modern, type-safe stack.

Toast's journey from monolithic web apps to GraphQL Federation, embracing microservices and BFFs for scalable, efficient development.

Learn how to customize your GraphQL Federation authentication and authorization strategies with Grafbase Extensions.\n\nUse existing extensions like JWT, Authenticated or Requires Scopes or build your own!

Explore how to implement a practical GraphQL gateway with complete CRUD operations for a multi-service architecture

The NATS extension enables you to publish and subscribe to NATS subjects directly from your GraphQL API, and lets you use the key-value store to store and retrieve data.

This article reflects Benjie's opinions on the past and the future of Nullability in GraphQL; but note that these are merely opinions.

GraphQL Federation has historically been constrained by the complexities of managing subgraphs, custom integrations, and infrastructure overhead. While existing solutions provide ways to unify GraphQL APIs, they still require significant operational effort. Until now.\n\nWe’re excited to introduce Grafbase Extensions, a powerful new way to customize and enhance your GraphQL APIs without the hassle of building and maintaining additional infrastructure. With WebAssembly-powered extensions, you can federate any API, database, or service into your GraphQL schema, whether it’s REST, gRPC, or Kafka. With Extensions, you can bring in any authentication (e.g. OpenID connect) or custom authorization logic directly into the gateway.

Explore the evolution of GraphQL, from overcoming monolithic graphs to enhancing developer experience and boosting performance.

While organizations have long sought to integrate REST APIs with GraphQL, the process of separately integrating each API has remained a widespread and persistent pain point.

Is GraphQL right for your project? Amazon's Vignesh Kamath reveals when this query language shines, when it fails, and how tech giants like Netflix and PayPal use it effectively in production.