Comment Comment by maktouch We solved this by using persistent queries that maps it like/graphql/{queryname}/{hash}?{params}Multiple advantages:1) client doesn't need to send the whole query unless it doesn't exist. All of this is handled automatically.2) http caching of queries are now possible since it's a get instead of post3) we can check slow queries using similar tools as rest. When we see a query being slow, we check each resolvers. We usually keep the queries simple parent maktouch 7 years ago
/graphql/{queryname}/{hash}?{params}
Multiple advantages:
1) client doesn't need to send the whole query unless it doesn't exist. All of this is handled automatically.
2) http caching of queries are now possible since it's a get instead of post
3) we can check slow queries using similar tools as rest. When we see a query being slow, we check each resolvers. We usually keep the queries simple