Start With REST

If each screen maps onto a resource or two, REST is the simpler choice. It caches at the edge, and every tool understands it. GraphQL earns its place when one screen needs data from several resources, each in a slightly different shape, and the round trips start to show.

GraphQL solves two real problems REST is bad at: over-fetching (mobile downloads 12 fields, uses 3) and under-fetching (one screen needs 5 round trips). The trade is operational complexity — N+1 query risk, harder caching, harder rate limiting. In 2026 the ecosystem has matured around Apollo Federation v2.x for subgraph composition, persisted queries for bandwidth + security, and HotChocolate 16 on .NET (with built-in DataLoader, projection, and federation support).

The right question in 2026 is no longer "REST or GraphQL?" but "where does each fit?" — GraphQL for product/aggregation graphs (BFFs, mobile, partner APIs); REST for resource CRUD, webhooks, and anything cacheable at the edge.

If your screens need many round trips
  • Your single GraphQL query triggers 400 SQL statements
  • Clients send 50KB queries on every render
  • You can't rate-limit because every request hits one URL
  • Your federated graph composition fails on every deploy

DataLoader for N+1, persisted queries for bandwidth + security, and field-level cost analysis for limits.