News for hackers. Stuff that matters.
Re:Migrating Netflix to GraphQL Safely by x86x87 on Sunday June 18, 2023 @02:41PM (#36383035)
I call bullshit. Where are you adding it? Api wide? Resolver? Data model? Custom?
Re:Migrating Netflix to GraphQL Safely by bbbbzzz1 on Sunday June 18, 2023 @03:37PM (#36383611)
Re:Migrating Netflix to GraphQL Safely by theturtletalks on Sunday June 18, 2023 @04:15PM (#36384003)
My SaaS backend is a GraphQL Server that has single-handedly saved me tons of hours for integrations and coding. The first iteration of the app was using rest and that was a pain. Hitting multiple endpoints to get all the details of an order is not something I miss. On top of that, I get a beautiful playground that acts as a query builder and documentation.

Have you actually used GraphQL in production or for a wide-scale project? A lot of these criticisms for GraphQL comes from people who have played with it for an hour and determined it's not good. Give it a real chance and you'll see why big companies are using it and understand why the ecosystem is growing so fast.

Re:Migrating Netflix to GraphQL Safely by x86x87 on Sunday June 18, 2023 @09:46PM (#36386410)
Yes. Used it for a a couple of large projects at BigCo. Was actually brought in to "polish" a few things. One of the original team members thought it was cool. It was a disaster. Uncovered issue after issue. Convinced management to run a bug bounty program through hackerone and I'm going to let you guess what happened.

If you're so brave and confident find a good pen tester and let them have a go at your api. It's a humbling experience.