> You still have to aggregate somewhere. Tbh, I'm not entirely sold on this - although I see this (server-side aggregation a cross data sources) as the main id

> You still have to aggregate somewhere. Tbh, I'm not entirely sold on this - although I see this (server-side aggregation a cross data sources) as the main idea behind graphql. So seems like it belongs in your graphql proxy (which can proxy graphql, rest, soap endpoints - maybe even databases). But for the "somewhere" part - consider that your servers might be on a 10gbps interconnect (and on 1 to 10gbps interconnect to external servers) - while your client might be on a 10 Mbps link - over bigger distances (higher latency). Aggregating on client could be much slower because of the round-trip being much slower. In addition, you might be able to do some server-side caching of queries that are popular across clients.