|
|
|
|
|
|
by prohobo
1107 days ago
|
|
|
I like it conceptually, but I never actually need it... So yeah. Implemented a gql API a few times and it felt like it was more efficient than a typical REST API with all the caching and flexibility, as well as feeling more functional because of the handlers. That said, it's not that much better and many apps simply don't need it. Often it's okay to just have a "gimme everything whenever I want it" endpoint that sends 100KB of data. I'd say graphql is useful when you're worried about requests killing your server. |
|
|