GraphQL

Modeling/Architecture

GraphQL

데먕 2020. 3. 8. 14:41

1. Overview

GraphQL is an open-source data query and manipulation language for APIs, and a runtime for fulfilling queries with existing data. It allows clients to define the structure of the data required, and the same structure of the data is returned from the server, therefore preventing excessively large amounts of data from being returned, but this has implications for how effective web caching of query results can be. The flexibility and richness of the query language also add complexity that may not be worthwhile for simple APIs. It consists of a type system, query language and execution semantics, static validation, and type introspection.

GraphQL supports reading, writing (mutating), and subscribing to changes to data (realtime updates - most commonly implemented using WebHooks).

GraphQL servers are available for multiple languages, including Haskell, JavaScript, Perl, Python, Ruby, Java, C#, Scala, Go, Elixir, Erlang, PHP, R, and Clojure.

On 9 February 2018, the GraphQL Schema Definition Language (SDL) became part of the specification.

2. Description

2.1 Motivation

GraphQL helps to address some of the more common headaches developers faced when building a REST API - backend application.

Typical architecture of a web application using REST API

2.1.1 Multiple round trips

You have a singleton REST resource that is too tightly coupled to your client UI. A new requirement comes from your product designer with changes. Newer clients would be requesting data that they essentially don't need anymore. Not that bat when you just start out, but in the long run, it'll be something nagging at you.