&gt; I believe graphql can be added on top of your backend, even more - it can layer on top of multiple microservices backends to provide single api endpoint<p>It is exactly what I&#x27;m saying. It&#x27;s yet another layer on the server, it doesn&#x27;t solve caching issues, and it will certainly not make your average app faster, especially when http2 support is here.<p>GraphQL is an ORM for rest apis. I thought rest apis were supposed to be universal, why need another layer on top of it? How many ORMs do developers need ? how much more complex does it have to get? The goal of REST is first and foremost readability and simplicity. The purpose of fat clients are to push complexity on the client. With graphQL simplicity is gone since everything is POST thus no http caching, and the server now gets another layer of complexity instead of being client agnostic.<p>Again, it might make sense at Facebook scale, but many articles promoting GraphQL are not talking about the fact that, it might not make sense for the majority of applications out there, even worse, it actually might make apps slower because of that extra layer.