it all depends. with graphql your backend can become really stupid and just handle saving and retrieving data, making it super easy to deploy, scale, archive, etc.<p>on the other hand having super dump backend makes it expensive to query data, since we have light speed limit for roundtrip between request and response at best.<p>what graphql does - it shifts point which does all these multiple requests closer to the storage layer and return you processed results based on query you asked.<p>if you application already returns rich data structures - graphql is probably do not belong here (right now). if you develop true microservices architecture - graphql sitting on top of it certainly might make sense.<p>as usual - it depends :)