Authorizing and authenticating users is an important part of building web applications. We need to know who the users are and what they are allowed to see. With a GraphQL app, how do we make sure that a user is allowed to see content? We need to authenticate them to make sure that we identify them. We also need to authorize them to prove that they have the right to access the application.
At the heart of any GraphQL project is a schema, a document that describes all of the types, queries, mutations, and subscriptions that are available on the API. In addition to these basic types, the GraphQL schema definition language provides us with a way to create an interface.
"We out here". I say this at least 5 times every day. I never knew the origin until I looked it up and found out that it means the "arduous labor of consistent practice in skateboarding tricks...skating hard...putting in work". Turns out, I've been using that phrase right, because lately, "we out here" has meant that we are on the road teaching GraphQL workshops.
In Spring 2017, we released our first O'Reilly book, Learning React. On the day that I heard they were sending the final version of the book to the printer, I made one simple request on Twitter:
