GraphQL Weekly Logo 2
A weekly newsletter of the best news, articles, and
projects about GraphQL, Apollo and more.
mutation {
  subscribeNewsletter(
    # enter your first name
    name:
    # enter your email
    email:
  ) {
    message
  }
}

Issue 122

Open Source
EasyGraphQL
A set of helpful open source tools for users of GraphQL. Offering a variety of mostly node libraries, the tools cover GraphQL aspects such as schema testing, load testing, creating a mock of your schema (especially useful to test things out quickly), and others. The tools focus on being easy to get started with and are incredibly useful. An awesome project to explore and give back to.
Migrating SpaceX API to GraphQL 🚀
It's now easier than ever to find out the details of all of SpaceX's activity via a GraphQL API. That was not the case before. This post by Carlos Rufo outlines the issues that he had consuming the original REST API and culminates with a code sandbox to try his migrated GraphQL API. There you can play around with the SpaceX GraphQL API and discover only exactly what you want to know about rockets, launches, missions, and other celestial concerns.
Conference
Announcing GraphQL Asia
The first Asian GraphQL conference is coming this spring! Being held April 12th and 13th in Bangalore, the conference has a great speaker line up with a particular focus on the Asian GraphQL community. Organized by Hasura and BrikL , the conference's CFP is open until January 15th.
Talks
Realtime and microservices with GraphQL
In his talk at Commit Conf, Luis Emilio Velasco offers an in-depth, hands-on walkthrough of using GraphQL with a microservice architecture. Building an app with Ruby, Elixir, Javascript, and React, he covers not just challenges and considerations of such a scaled out architecture, but also closes the talk with a focus on subscriptions and GraphQL's realtime capabilities.
GraphQL: “If there’s no documentation, people aren’t going to be able to use it…”
This article covers James Scott's API the Docs's talk, "Is GraphQL really self-documenting?" He makes a convincing case for the value of documentation and descriptive naming, even getting input from Lee Byron on the matter: "If there’s no documentation, it doesn’t matter how good the API is". While documentation may not always be top of mind, this article does a great job of illustrating why it ought to be. A very interesting read.
Want more of this?