I wouldn't say I'm skeptical of it. I think it's a phenomenal spec with many great implementations like Apollo. I don't think it's the solution for all API needs, but it's a great solution for many use cases. It does come with some costs when giving up on what HTTP provides.
Would you expand on these costs (perhaps in an additional post)? It would be really interesting to see another perspective on this.
I'm currently on the fence about GraphQL (with the drawback I see is a major adaptation work required on the server-side to map the relations - description, definition, implementation) - and would like to know more on what are the pitfalls, before jumping in.
Thanks for the post!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I wouldn't say I'm skeptical of it. I think it's a phenomenal spec with many great implementations like Apollo. I don't think it's the solution for all API needs, but it's a great solution for many use cases. It does come with some costs when giving up on what HTTP provides.
Would you expand on these costs (perhaps in an additional post)? It would be really interesting to see another perspective on this.
I'm currently on the fence about GraphQL (with the drawback I see is a major adaptation work required on the server-side to map the relations - description, definition, implementation) - and would like to know more on what are the pitfalls, before jumping in.
Thanks for the post!