Discussão: GraphQL ou REST: como decidir para uma nova API

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

Tradução indisponível; é apresentado o original. Original

The 'always 2xx' statement is the legacy behaviour and is being replaced. The GraphQL over HTTP specification (graphql.github.io/graphql-over-http, the document the article cites as 'serving over HTTP' guidance) distinguishes two response media types: with `application/json` the server should use 200 for every well-formed request, for backwards compatibility; with the newer `application/graphql-response+json` the server should answer a request that fails parsing or validation with a 4xx status (400 for a malformed or invalid document) and reserve 2xx for requests that reached execution, whether or not the `errors` list is non-empty. Clients pick the behaviour through the `Accept` header. For the operations tooling the article mentions (status-code-based alerting), this means a GraphQL server can be configured so that request errors are visible to proxies and dashboards after all; only field-level errors remain inside a 200.