Questions you need to be able to answer — The book Observability Engineering by Charity Majors, Liz Fong-Jones, George Miranda (highly recommended) starts with an explanation of what “Observability” is, and how to know if you software has it. They propose a small litmus test for determining the answer. …

The Problem Rate limiting and securing server resources are central problems when developing any kind of API. We want to prevent clients from being able to affect the experience of other clients, or simply avoid being taken down. …

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…

🌱 This post is still growing and likely will change as best practices evolve 🌳 GraphQL errors are something many of us struggle with. Good practices are emerging but the community has not yet settled on a convention. …

GraphQL has a reputation for its N+1 problem which can often happen when implemented naively. This leads to a lot of us trying to solve the issue of data fetching with GraphQL in the most efficient way possible. …

GraphQL is everywhere these days. From Facebook’s original usage of it to some more funky usages like databases, GraphQL is loved by so many developers that we are starting to use it in areas nobody would’ve thought of initially. Every technology has its use cases for which it is ideal…