# Migrating to GraphQL: A Practical Assessment

arXiv: https://arxiv.org/abs/1906.07535 · HTML: https://mlsanity.com/paper/1906.07535/

## Key facts

- Cited by 3 papers in the map (data through 14 Oct 2026).
- First posted on arXiv 18 Jun 2019.

## Built on by (most cited first, 3 of 3)

- [Synergizing LLMs and Knowledge Graphs: A Novel Approach to Software Repository-Related Question Answering](https://mlsanity.com/paper/2412.03815/) (2024)
- [FinOps Agent -- A Use-Case for IT Infrastructure and Cost Optimization](https://mlsanity.com/paper/2510.25914/) (2025)
- [Learning GraphQL Query Costs (Extended Version)](https://mlsanity.com/paper/2108.11139/) (2021)

## Abstract (arXiv)

GraphQL is a novel query language proposed by Facebook to implement Web-based APIs. In this paper, we present a practical study on migrating API clients to this new technology. First, we conduct a grey literature review to gain an in-depth understanding on the benefits and key characteristics normally associated to GraphQL by practitioners. After that, we assess such benefits in practice, by migrating seven systems to use GraphQL, instead of standard REST-based APIs. As our key result, we show that GraphQL can reduce the size of the JSON documents returned by REST APIs in 94% (in number of fields) and in 99% (in number of bytes), both median results.