3 ms·
But you're still going to make lots of requests which result in inefficient data access on the server unless you batch them up. So you just end up moving batchi
by jahewson 10y ago
But you're still going to make lots of requests which result in inefficient data access on the server unless you batch them up. So you just end up moving batching from the client where it is easy, to the server where it is hard.
- ruslan_talpa 10y agoIt's hard but solvable. If the data comes mainly from one database (although you can do some cools stuff with FDW in Postgres) then each graphql query can be translated to a single SQL query and it works quite efficiently, only one trip to the db (https://subzero.cloud/ https://subzero.cloud/)