Why REST and GraphQL matters more than it looks

Most teams know this matters. Fewer have decided who owns it. REST and GraphQL is easy to treat as a detail, and that is exactly why it is worth a few minutes of attention.

The question is rarely whether something can be built, but what it costs to keep running afterwards. The version that survives contact with a real deadline is the simple one.

Why it matters

REST is simpler to cache and easier to reason about. Getting it slightly wrong is survivable. Ignoring it entirely is not. The version that survives contact with a real deadline is the simple one.

GraphQL shines when clients need wildly different shapes of data. The teams that handle this well are rarely the ones with the biggest budgets. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

Warning signs

The right answer depends on your clients, not on fashion. The reasoning matters more than the rule, because the rule has exceptions. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

The short version

Code gets read far more often than it gets written, and usually by someone with less context than the author had. Three things worth confirming about REST and GraphQL before you move on:

• Someone can say what the current setup is without going to look
• The right answer depends on your clients, not on fashion — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Most of the value here comes from doing the first two things, not all of them.