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.
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…
This post is a snippet from Production Ready GraphQL. It is part of an update I’m working on for the schema design chapter in version 1.3. I decided to release it publicly as well because this side of abstract types is not talked about very much, and the subtle differences…
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.
gqless is a fundamentally new approach to a GraphQL client. It makes using your API…
The book contains a fulloverview of what is needed to build great GraphQL APIs:
Performance & Monitoring
Migrating from legacy APIs
A lot more: Everything I’ve learnt on building GraphQL APIs is in there!
With the book you may also get the Complete Packagewhich contains:
Three extra guides (A schema design checklist you can keep close when building features, a full cheatsheet on making schema changes and evolving an API, and a few reviews of publicly accessible APIs to learn from existing APIs)
4 interviews with amazing GraphQL community members including folks from Shopify, GitHub & More
How do you version GraphQL APIs? The most common answer you’ll get these days is “you don’t”. If you’re like me when I first read that, you might be a little anxious about maintaining a version-less API or a bit skeptical of the approach. …