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

The agentic age of software brings new challenges for our APIs. Semantic Introspection makes GraphQL discoverable, scalable, and precise for LLMs.

Explore how Shopify rebuilt GraphQL execution from scratch. Cardinal's breadth-first engine delivers 4s latency savings and what it means for Ruby developers.

We fact-checked 18 claims comparing GraphQL and REST against peer-reviewed research, official docs, and security reports. Only 3 held up. Here's what the evidence actually says.

GOV.UK are exploring how the APIs that deliver content for GOV.UK could evolve to better support an experience spanning multiple digital channels. Find out what we’re doing and how GraphQL being explored!

Apollo Skills cut AI agent token usage and completion time down significantly — same result, far less cost. Here's what the experiment revealed.

From the AWS blog: This post shows you how to implement AWS Lambda authorizers with Direct Lambda Resolvers in .NET.

Most GraphQL Gateway and general GraphQL discussions focus on customer-facing applications—aggregating microservices behind a single endpoint for web and mobile clients, enabling frontend teams to query exactly the data they need without multiple round trips. Trivago's use case and perspective were different.

Event Sourcing is emerging as a preferred approach to building complex software systems. It enables rapid development, smooth evolution over time, and opens the door to AI-based acceleration.

GraphQL adoption within enterprise environments follows a predictable pattern. A single team implements it successfully, word spreads and suddenly dozens of services want to expose data through your graph / Ramesh Karsala

Hello there, this is a nice content that could be interesting for folks running GraphQL in JVM applications.

April Fools' Special: A look at the most controversial (and entirely fictional) bug fix of the year.

Hemnet is Sweden’s largest property platform, serving millions of users who browse, save, and search through real estate listings every day. This case study shares their migration story from Apollo Router (Rust) to Hive Gateway (JS).

Boilerplate became cheap, but GraphQL still wins when a durable schema contract matters across teams and clients.

Your GraphQL API already serves your frontend developers well. But increasingly, it needs to serve another kind of client: AI agents that can discover, understand, and interact with your data automatically, retrieving information, performing actions on behalf of users, and chaining multi-step workflows without human intervention.

Apollo's MCP Server turns your GraphQL schema into a tool catalog that AI agents discover and call through natural language. Blog post covers production patterns including serverless deployment on AWS Lambda, Vercel, and Cloudflare.

Shopify discovered their slowest GraphQL queries weren't waiting on databases. They were sluggish in the resolver loop. DFS runs every field resolver per object, and it compounds with nesting. Their answer: Cardinal, a breadth-first executor. 15x faster, 6x less GC pressure, 4s off P50 on large lists.

A thorough exploration of schema evolution, semantic drift, and why GraphQL schema registries are "parse, don't validate" applied at the version boundary.

GitHub won't admit it's a social media platform and notify you when someone ❤️'s your issue. Terence Eden dove into GitHub's API to pull reactions across issues, PRs, and comments. His verdict: the Necronomicon was probably written in GraphQL.

Apollo Skills cover Apollo Client & Server, Connectors, schema design, and operations. Open source at github.com/apollographql/skills

Leela Kumili, Lead Software Engineer at Starbucks, writes for InfoQ about Agoda's API Agent: a single MCP server that connects to any internal REST or GraphQL API with no code, no deployments. It consolidates multi-API overhead, answers AI-assisted queries, and post-processes results with in-memory SQL for safe, scalable data access.

Even with introspection disabled, GraphQL APIs leak schema information through error messages. GraphQL Armor blocks field suggestions by default; for everything else, customize your error formatter to strip schema details.

RLS disabled, a Supabase API Key exposed in client-side JavaScript. Full write access to the DB. GraphQL Introspection and Supabase PostgREST error messages to learn what's inside. Gal Nagli describes how he hacked the social media website for AI agents.

Learn 10 proven principles for designing GraphQL schemas that scale. Covers capability-based design, error handling, nullability, pagination, federation, and avoiding common pitfalls from companies like eBay and SoundCloud.

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