3 ms·
The default implementation of GraphQL has a lot of overhead in query parsing and validation alone. You can try this yourself with complex queries and simulating
by quonn 5y ago
The default implementation of GraphQL has a lot of overhead in query parsing and validation alone. You can try this yourself with complex queries and simulating some load.
But it‘s an issue that can be solved.
- FpUser 5y ago">You can try this yourself with complex queries and simulating some load." I do not need to try it. I know what it takes to parse/validate this kind of queries and then manage to get and assemble the results from numerous sources. >"But it‘s an issue that can be solved." No. This issue will not be solved as in general it is a problem of mapping one storage / functionality format to end client format. It can be easily solved for particular situations by writing custom servers (this is for example one of the things I do) but doing it generically introduces overhead / costs that are very unhealthy for a normal businesses. And it is of course bad as it wastes energy.