3 ms·
Maybe that's a good reason to avoid GraphQL then?
by aaaaaaaaaaab 5y ago
Maybe that's a good reason to avoid GraphQL then?
- TheGuyWhoCodes 5y agoThat's not the reason, there are many but this a nice feature where a client can send one request and it will resolve internally (so less client side requests), you can request only the fields you need and it's easier when hitting multiple micro services. Now you get into the issues of tracing, request failures and retries, payload size (only json? really..) etc. But I do agree that a super optimized sql for a a specific purpose has it's performance benefit
- psadri 5y agoIn theory the graphql server could be smart enough to assemble a single SQL select to satisfy the query. Does anyone know of an implementation that does this?