Oh no, another bullet-points under-argumented article with misleading comparison charts. How is GraphQL not cacheable, performant and scalable? Doesn’t work with any data? Not enterprise-ready? Tell that to Facebook, Twitter, Airbnb, GitHub, Ticketmaster, The New York Times, KLM, ProductHunt, Open Table, Pinterest, Shopify, Express, Major League Soccer, Expo…
Server and clients coupled at the client programming time
Don’t you need to couple REST queries as well? Because if you use the wrong fields, sure it won’t work. I don’t see the point.
application state is not driven by the server
You mean the frontend devs know better how the frontend works and what are its needs? That’s the point!
Bikeshedding (content negotiation, network errors, caching), etc. etc.
All done for you already in the most popular clients.
You are on your own with scaling and performance
Yeah, use containers and REDIS for Real-time subscriptions. Are you saying REST is automatically scaled and performant?
JSON representation only
the major one is pretending it owns the show
What do you mean? If you talk about Facebook, Apollo or Prisma, those are leading and pushing the development and improvement of the GraphQL spec (like for example subscriptions) and ecosystem (like tracing protocol).