This is the problem I had with graphql. Indeed it simplifies the interface between the backend and the frontend of your application (that is when the api can be

This is the problem I had with graphql. Indeed it simplifies the interface between the backend and the frontend of your application (that is when the api can be cleanly mapped to a graph) but it doesn't really solve the problem of minimizing roundtrips, it just moves it between the backend and the database. Because the database I was querying was not on the same network I was losing seconds (!) doing roundtrips on the network gathering all the data necessary for a single complex graphql query. You may say: well use something like postgraphile but what if you did not designed the database and so it doesn't map cleanly to your graphql object tree? I had to waste a week implementing a postgres query generator so I can remove the latency. Not fun, especially when you have deadlines.