3 ms·
> Maybe there are also some situations where GraphQL fails, I would definitely be interested to hear about that. I know one, but it will take you a while to re
by kodablah 9y ago
> Maybe there are also some situations where GraphQL fails, I would definitely be interested to hear about that.
I know one, but it will take you a while to realize it. Allowing a lot of flexibility in query types makes it harder to optimize later when you can't predict the code paths your clients will take. In the API world, I have learned the hard way that flexibility is a bad thing especially compared to specific ways to obtain data and very optimizable, well-known "hot" paths to data.
- foota 9y agoYou can always use analytics on the calls made to find hot code paths.
- kodablah 9y agoThis misses the point. I'm not talking about finding hot paths, I'm talking about limiting the total predictable path count so you can optimize better. Or, as I often saw, when you have so many paths to different data pieces, you don't test every permutation of every combination of paths, and a caller finds one that hurts for some reason (e.g. bad optimization choice by your RDBMS).
- foota 9y agoYes, but with analytics in place you'll find that when it happens and be able to fix it?