3 ms·
I don't disagree in principle, but often you need the API anyway, and it makes little sense to duplicate the effort just for the sake of purity. If you are in
by qsort 5y ago
I don't disagree in principle, but often you need the API anyway, and it makes little sense to duplicate the effort just for the sake of purity.
If you are in that situation, GraphQL is actually worse, because you end up with less control over the SQL you end up running.
I can see that idea working very well for content-driven, interactive but mostly static websites, something like HN.
- recursivedoubts 5y agoYour JSON API, once you pull your web app usage and all the special end points for it out, should be pretty regular and not a ton of code. So the actual amount of duplication cam be low, and your API engineer will be bored and happy. :)