News for hackers. Stuff that matters.

A comment on Ask HN: Were you happy moving your API from REST to GraphQL?. Parent comment

Re:Ask HN: Were you happy moving your API from REST to GraphQL? by CGamesPlay on Thursday July 19, 2018 @12:07PM (#17567628)
Why do you think it makes the most sense if “the backend and frontend teams don't like to talk to each other”, given that your biggest complaint seems to be “I don't want to spend time figuring out your database schema“? Aren’t you the frontend guy in this scenario, and not wanting/able to talk to the backend guys (the people who designed the database schema)?
[ Parent | on HN ]
Re:Ask HN: Were you happy moving your API from REST to GraphQL? by StavrosK on Thursday July 19, 2018 @12:37PM (#17567976)
He (the hypothetical he) doesn't want to talk to them to get them to add the endpoint he needs, so he'd prefer to just get the schema directly and query for whatever.
[ Parent | on HN ]
Re:Ask HN: Were you happy moving your API from REST to GraphQL? by tormeh on Thursday July 19, 2018 @02:27PM (#17569072)
Note that this means the back end team has to keep the schema backwards compatible forever. Having everyone have direct access to the schema (speaking from SQL experience) is bad. This is the start of a slow moving disaster train that you can't stop.
[ Parent | on HN ]
Re:Ask HN: Were you happy moving your API from REST to GraphQL? by alexchamberlain on Thursday July 19, 2018 @02:35PM (#17569135)
I disagree; the GraphQL schema should be your point of stability, whereby anything in front or behind can change. That being said, ofc, you'll need to deprecate something at some point and that is fine, it might just take a couple of weeks. See @deprecated decorator examples
[ Parent | on HN ]
Re:Ask HN: Were you happy moving your API from REST to GraphQL? by tomnipotent on Thursday July 19, 2018 @09:11PM (#17571728)
> the GraphQL schema should be your point of stability, whereby anything in front or behind can change

This is the bit of abstraction I see most developers fail to understand when evaluating GraphQL.

[ Parent | on HN ]
Re:Ask HN: Were you happy moving your API from REST to GraphQL? by RussianCow on Thursday July 19, 2018 @02:31PM (#17569104)
Not forever, just as long as you support out-of-date clients (either because of cached JS on the web, or mobile apps that haven't been updated recently). Plus, you generally don't want to introduce backwards-incompatible changes to your schema anyway at a certain scale, unless you can afford to have planned downtime, so GraphQL doesn't add anything new here.
[ Parent | on HN ]
Re:Ask HN: Were you happy moving your API from REST to GraphQL? by BerislavLopac on Thursday July 19, 2018 @02:56PM (#17569291)
I'm not quite sure what does the database schemas have to do with the front-end queries...
[ Parent | on HN ]
Re:Ask HN: Were you happy moving your API from REST to GraphQL? by elliotec on Thursday July 19, 2018 @04:10PM (#17569819)
In this case OP is talking about the GraphQL schemas, not the DB.
[ Parent | on HN ]
Re:Ask HN: Were you happy moving your API from REST to GraphQL? by BerislavLopac on Thursday July 19, 2018 @04:32PM (#17569998)
I'm not sure which OP do you mean? The parent mentions "SQL experience", the grandparent is ambiguous, and the GGP explicitly mentions "database schema".

If by OP you mean the original article, I completely agree with you; my comment was directed to its ancestors.

[ Parent | on HN ]
Re:Ask HN: Were you happy moving your API from REST to GraphQL? by slow_donkey on Thursday July 19, 2018 @01:59PM (#17568823)
The internal team would have a vested interest in introspecting the API but an end user (developer) would not.

But I actually found their graphql docs to be sensible? Not sure where the introspection comes into play

[ Parent | on HN ]