3 ms·
You're likely to get a lot of selection bias in the answers - people using it likely made a decision that it's worth the hassle for their use case. To add a cou
by radu_floricica 5y ago
You're likely to get a lot of selection bias in the answers - people using it likely made a decision that it's worth the hassle for their use case. To add a counter point: GraphQL was a non starter for our company, because we work with _very_ heterogenous clients who need to implement our API and the extra learning curve would be a killer.
If you have to implement a simple REST API you just look at it and in a few hours the job is done. If it would be GraphQL, lots of people would have to learn a new paradigm just to implement a few calls.
- eurasiantiger 5y agoYou can call a GraphQL API using any HTTP client.
- radu_floricica 5y agoI don't know any GraphQL, and when it came time to implement a GraphQL client, I spent half an hour trying to figure out what it's about, and then simply chose another supplier. It may be "self-documenting", but not for those that didn't go through the learning curve. The learning curve may be short, or worth it, or fun if you're that kind of person. But don't tell me that all you need is a http client because that's simply not true, not "out there". And I'm certainly not about to subject hundreds of my clients' clients to having to learn something new just to implement a simple API.
- eurasiantiger 5y agoBut it is true. You can call it even with cURL and get a JSON string back. https://www.apollographql.com/blog/graphql/examples/4-simple-ways-to-call-a-graphql-api/ https://www.apollographql.com/blog/graphql/examples/4-simple... Of course, you need a GraphQL API first. Apollo is good if you want to resolve all your entities manually, but there are novel integrated database approaches like Dgraph that generate everything based on the schema.
- radu_floricica 5y agoI hope you're joking. What is this "resolving all your entities manually" you speak of? Apollo? Dgraph? Is it Klingon? What you're telling me that it's doable... once you go through the learning curve. And if you'll allow me a testy comment (not personal), it's exactly this lack of empathy toward end users that doesn't make me wanna try it. What would help would be an already generated REST API I can use as an alternative.
- brundolf 5y agoTechnically all you need is a TCP port I think the other person's point is that a GraphQL API is not a trivial leap from normal http; it's a significant abstraction layer of its own that requires its own learning process