This post is a response to "Why use GraphQL" by Kyle Schrade. The author states that REST APIs come with a set of downsides and how GraphQL solves all of them. The pattern described is named "backend for frontend" (BFF) It's not limited to full stack frameworks like Next.JS.
Table of contents
Why not use GraphQL?Downside of RESTNo more versioned APIsSmaller payloadsStrictly-typed interfacesBetter client performanceLess time spent documenting and navigating APIsLegacy app supportBetter error handlingConclusionMy version of "Why GraphQL"1 Comment
Sort: