5 ms·
you don't think it's a benefit that you could get the benefits of a "hydration service that ran as a proxy in front of the requests" out of the box? there's lo
by bernawil 2y ago
you don't think it's a benefit that you could get the benefits of a "hydration service that ran as a proxy in front of the requests" out of the box?
there's lots of other benefits for GQL: multiple queries per request, mutation/query separation, typed errors, subscriptions support.
- karmakaze 2y agoI currently use GraphQL and have no problems with it specifically, I was merely sharing an experience using REST. Perhaps it adds a bit of latency/overhead due to the implementation/language that's used but with larger requests rounds downward.