Migrating Netflix to GraphQL Safely

Re:Migrating Netflix to GraphQL Safely by jdauriemma on Sunday June 18, 2023 @02:13PM (#36382739)

The state of the art of GraphQL tooling around securing and versioning has evolved significantly. You may want to take another look at what’s out there.

[ Parent | on HN ]

Re:Migrating Netflix to GraphQL Safely by rblatz on Sunday June 18, 2023 @02:19PM (#36382815)

I was just researching graphql versioning and the recommendation is not to version because the graph is supposed to be an evolving entity.

[ Parent | on HN ]

Re:Migrating Netflix to GraphQL Safely by x86x87 on Sunday June 18, 2023 @02:28PM (#36382900)

"evolving" right. As someone who had to work with this "evolving" pos I can tell you it degenerates in a mess without a lot of discipline which ends up negating the supposed benefits of gql

[ Parent | on HN ]

Re:Migrating Netflix to GraphQL Safely by Dudester230602 on Sunday June 18, 2023 @04:26PM (#36384112)

Put this into the "my code is self-documenting" bin.

[ Parent | on HN ]

Re:Migrating Netflix to GraphQL Safely by x86x87 on Sunday June 18, 2023 @04:42PM (#36384246)

my self-documenting code is evolving!

[ Parent | on HN ]

Re:Migrating Netflix to GraphQL Safely by itsmeste on Sunday June 18, 2023 @06:03PM (#36384990)

mutation createUser-v2

Seen that in some productive APIs, always fun.

[ Parent | on HN ]

Re:Migrating Netflix to GraphQL Safely by tnzk on Sunday June 18, 2023 @02:21PM (#36382844)

Could you please provide some pointers?

[ Parent | on HN ]