I think one problem of gql relates to caching. Using rest, it's dead easy to enable caching on load balancer or CDN level with background updates. But with gr

I think one problem of gql relates to caching. Using rest, it's dead easy to enable caching on load balancer or CDN level with background updates. But with graphql- it's not so trivial. Youll have to do workarounds by caching POST requests (which imo is bad practice) or use GET requests, which might not work because the URL gets too long. Or use named queries, but then - what did you gain compared to rest? Another problem is that you expose internals and may more easily make yourself vulnerable to overload attacks. My two ören