It's also interesting to consider how making an API that reads data use the `POST` method is likely to make it more difficult to cache yet switching to the `GET` method likely means that a query needs to fit within a URL (unless you send a request body 'a la ElasticSearch').
Interesting to consider the trade-offs between the number of HTTP requests and the likelihood that a request is or isn't cached (by the browser).
-
-
Show this thread
-
Similar thoughts and alternative solutions here and here: https://apisyouwonthate.com/blog/graphql-vs-rest-caching … https://medium.com/@jono/cache-graphql-post-requests-with-service-worker-100a822a388a …pic.twitter.com/6vNukH3C2m
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.