Re:How GraphQL Replaces Redux
by joshribakoff on Wednesday March 14, 2018 @02:48AM
(#16582828)
Being able to stay agile & change the app, without breaking old versions of the app, and without having to have an explosion of ad-hoc end-points for every change you've ever made. With graphQL its perfectly reasonable to never rename or delete fields, and never break backwards compatibility. With REST that would not work & would result in over-fetching, or tons of ad-hoc end points for every query you've ever written.
[ Parent
| on HN ]
There are no comments on this comment yet.