GraphQL is a data query and manipulation language that provides a single endpoint for fetching data from multiple sources. It allows clients to define their own data requirements and exposes data through a single schema. Some key benefits include fewer roundtrips to the server and allowing UI components to describe their own data dependencies. Apollo Client is commonly used with GraphQL and works well with Redux. It provides features like caching, refetching, and loading states. Development tools include Apollo devtools, GraphiQL, and ESLint plugins. Best practices include creating interfaces for pagination, handling authorization, error handling, and partial responses.

1. GraphQL
Arnar Þór Sveinsson @arnarths

2. • Data defined as a cyclic graph instead of
endpoints.
• Mutations exposed as part of schema
• All data exposed through a single endpoint
Beyond REST

3. Benefits
• Fewer roundtrips to the server
• UI components can describe
their own data dependencies
• Typesafe client/server contract

4. Features

5. • Apollo client
• Works well with Redux
• Available for React, Angular, iOS, Android and standalone client
• Relay
• Developed by Facebook
• Lokka
• Raw client
Clients

6. • One entry point - /graphql
• Single schema with all of our data
• ClientAPI defines the schema and fetches the
data VIA thrift from other services
• Apollo client with Redux
How is WOW using GraphQL

7. • Client side caching
• Refetch prop
• Loading prop
• Force fetch attribute
• Components define their own data
• Becomes part of the Redux store we already have
defined
Apollo Client

8. • Apollo devtools
• React devtools (when using Relay)
• ESLint
• GraphiQL
• Auto complete my request plugin (wants)
Development tools

9. • Pagination - create
an interface for
pagination
• How to deal with
authorization?
• Error handling?
• Partial responses?
Best practices