It&#x27;s great that GraphQL&#x27;s solved some of your issues, and you&#x27;ve encouraged me to look into it a bit more. One thing you should worry about, though - if at any point there&#x27;s any user-specific data in an HTTP response that doesn&#x27;t have the user&#x27;s ID in the URL (or something pointed to by the &#x27;vary&#x27; header), it kills the idempotence of the request, whether you&#x27;re using what Rails gives you or GraphQL or XML-RPC or whatever, which is pretty much the whole point of REST. It&#x27;s not just REST-nazism, this completely destroys the usefulness of any cache past that point if it doesn&#x27;t understand the internals of your API (as you seem to note that you&#x27;ve realized at the end of the article). It might make sense to just not expose the GraphQL to the client, so you can think about the idempotence of your requests from the backend, and allow yourself to keep making use of caching proxies and client-side cache.