So, today we’re going to write a small GraphQL server. I’m not going to try to persuade you to drop everything and adopt GraphQL — but if you’re curious about what this stuff looks like today and how it works, read on.
The word “directive” might sound quite technical and maybe a bit scary, but we’re going to take this time to explore GraphQL directives and show that they’re not really all that bad.
Browsing the GraphQL specification, you might stumble into the section on variables and wonder, “Why on earth GraphQL does have variables?”
The spec quietly mentions the rationale, and if you read too fast you might miss it:
GraphQL’s type system is the distinguishing feature in comparison to other protocols like REST, Falcor, and JSON Schema. Interfaces and Unions are two of the more nuanced aspects of the type system, but prove valuable in any non-trivial product. Let’s take a closer…
Maybe you haven’t heard of GraphQL. It’s a query language for front-end engineers to retrieve data from…
Folks ask about how GraphQL works with authentication and authorization. Ultimately, the answer is that GraphQL…
