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


The tension between data & use-case driven GraphQL APIs

In this article, Marc-André Giroux comments on the differences between data and use case driven schema design . Even with a tendency to lean toward a use case driven approach, there are some clear downfalls when handling details like pagination and timeouts. As with most things, a combination of strategies may solve these problems. Marc offers a few ideas to merge the two strategies and benefit from each of their strengths.

TypeGraphQL and GraphQL Nexus — A Look at Code-First APIs

Rohit Ravikoti at Novvum provides a clear comparison of two popular code-first GraphQL libraries, TypeGraphQL and GraphQL Nexus. The article does a great job of outlining the advantages and disadvantages of each API and provides coded examples of their differences. This is a great place to start when exploring code-first GraphQL development with Typescript or Node.

Understanding GraphQL Mutations

An in-depth introduction for beginners to understanding GraphQL mutations. The article provides a helpful summary on the different use cases for mutations as well as how to return custom objects.

Behind the scenes of Hootsuite Inbox

A deep and fascinating article on how Hootsuite used GraphQL to build out their inbox tooling. The piece walks through the the challenges the team faced with views and the ways that the collaborative nature of the software required all actions taken to be asynchronous and having eventual consistency. Told through an example of a more generic todo list, this article is a great read through some of the benefits and challenges of GraphQL in development.


GraphQL Without GraphQL: Backend Agnostic Requests with GraphQL Style Querying

A great talk from ForwardJS 2019 that explores GraphQL's data fetching style and how we can apply that regardless of the backend implementation. The video provides a quick introduction to fetching data with GraphQL, then dives into how you can emulate that pattern without a GraphQL backend. This could provide a new and unique way to migrate frontend clients iteratively.