Persisted Queries? Let’s start with a very quick primer on GraphQL persisted queries. A typical interaction between a GraphQL client and server looks a bit like this. While this works perfectly well, there are certain downsides with query-based APIs: The request payload can grow large and is sent every single request, even…

This twitter thread blew up on twitter yesterday and I thought I’d go over some of the author’s points in a longer format so we can clear up some misconceptions. Let’s go over them one by one! [Tweet 1] GraphQL makes your public API equal to a generic database and…

This is a response to two articles I stumbled upon the past few weeks: https://devops.com/graphql-as-a-meta-layer/ (which links to the second article below) https://wundergraph.com/blog/graphql_is_not_meant_to_be_exposed_over_the_internet Having worked on two large public GraphQL APIs in the past, this concerned me. …

Last week, the team at Notion released the beta of their new public API: https://developers.notion.com/. As a Notion user myself (but mainly as an API nerd), I took a look at what the new API looks like. Thought I’d share my findings here. API Style Let’s start by the API style. Some…

As GraphQL is gaining in popularity, misconceptions about how it works and what it provides are also growing. I demystify a lot of these misconceptions in detail in Production Ready GraphQL, but here’s a little top 3 list of misconceptions I see and hear around GraphQL these days. Self-Documenting REST: Requires…