Skip to content
dvnt.io

Resources · glossary

REST vs GraphQL

Two ways of exposing data between systems. REST provides ready-made endpoints with a fixed set of fields; GraphQL lets the caller specify exactly what it needs in a single query.

Also called
  • REST API
  • GraphQL API
  • REST vs GraphQL
  • GraphQL query
  1. 01

    What it changes in practice

    The number of requests and the amount of data sent. With REST, data from three places takes three requests and you also get what you didn't need; with GraphQL, one query returns exactly the fields you asked for.

  2. 02

    When REST is enough

    Almost always for simple integrations: a form into a CRM, an order into the warehouse, a few fields each way. It is easier to understand, easier to inspect and supported out of the box by every tool.

  3. 03

    When GraphQL pays off

    When there are many consumers and each needs something different: a mobile app, a website and a reseller, all from the same source. Then one flexible entry point is cheaper than maintaining a dozen variants of endpoints.

  4. 04

    What the technology doesn't settle

    The quality of the other side. The provider's documentation and test environment affect the cost of an integration more than the choice between REST and GraphQL. Without either of them, a quote becomes guesswork.

In practice

Related terms

  • APIAn agreed way for one system to ask another for data or tell it to do something. APIs are how a shop knows its stock levels and how a website sends a contact to the CRM.
  • System integrationConnecting two systems so they exchange data without retyping it by hand: a shop with a warehouse, a form with a CRM, payments with accounting. The cost usually lies on the side of the system you are connecting to.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.