News for hackers. Stuff that matters.
Re:Migrating Netflix to GraphQL Safely by Humphrey on Sunday June 18, 2023 @10:11PM (#36386572)
This!

But I'll add one more: "Standardisation". Every RESTful API uses different URL paths, naming schemes, HTTP verbs, data structures, headers. Whereas those are defined by the GraphQL spec.

When consuming or creating a GraphQL API, those (usually meaningless) decisions are defined by the spec, so I only need to learn how the data is structured. Since it's a spec, my queries can be strongly typed in both frontend and backend.

Re:Migrating Netflix to GraphQL Safely by throw1234651234 on Monday June 19, 2023 @01:29PM (#36393961)
I don't understand what you are saying here. RESTful APIs are supposed to follow a specific format, e.g. GET: candidate/{id}, GET: candidate, POST: candidate, body: CandidateDto, etc. How is GraphQL different? Keep in mind that you can "see what's available" on a Swagger page easily with a REST API.