Having too many versions of an API makes it very hard to keep track of. In GraphQL, there's only one version of the graph and changes can be tracked in a schema registry, a paid feature of Apollo. If you want to introduce a breaking change in this scenario without breaking a client, it's impossible. It would be impossible.
Table of contents
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"My personal Conclusion1 Comment
Sort: