3 ms·
For comprehensive APIs,GraphQL is often more performant. 1 request that takes 500ms is far better to 5 requests that take 200ms
by throwoutttt 6y ago
For comprehensive APIs,GraphQL is often more performant. 1 request that takes 500ms is far better to 5 requests that take 200ms
- systemvoltage 6y agoYou can create a single endpoint that's non-RESTFul to make a single call.
- adamscybot 6y agoYes and by doing so you lost the advantages of a predictable and well organised API. GraphQL has first class support for this scenario.
- systemvoltage 6y agoI disagree. You're shifting your "organization" to the frontend which becomes an utter cesspool of chaos. If anything changes in the backend, you will need to change the frontend as well. The whole point of an API is to decouple. GraphQL does the exact opposite.
- cunac 6y agodepends, if all requests are parallel they should hit different instances and that would distribute load more efficiently instead of pinning to single instance. You would actually get response in 200ms not to mention that your ability to properly size each node is increased. It also enables you to have a grey area where response can be partial and not just fail/pass. As usual YMMW depending on use case.